Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manual: Digipeater/Igate symbol selection, updated links. #41

Closed
wants to merge 1 commit into from

Conversation

dandrzejewski
Copy link
Contributor

@dandrzejewski dandrzejewski changed the title Manual Updates Digipeater/Igate symbol selection, updated links. Dec 18, 2016
@dandrzejewski dandrzejewski changed the title Digipeater/Igate symbol selection, updated links. Manual: Digipeater/Igate symbol selection, updated links. Dec 18, 2016
@PhirePhly
Copy link
Owner

Thanks. I haven't done a good job of scrubbing stale links and contact info from the Aprx source.

How did you generate the digi icons with over-lays? I've been looking for a clean way to do that.

As for the symbol guidance, I was very displeased that Bob took none of my input on what symbols should be recommended for new builds, and I'm not willing to recommend the use of E, L, P, V, or W overlays. The Aprx manual should recommend the symbols covered in my article: https://github.com/PhirePhly/aprs_notes/blob/master/digipeater_symbol_selection.md

@dandrzejewski
Copy link
Contributor Author

OK. I'll update the document.

As for the symbols with overlays... I figured out how aprs.fi does it. I used Chrome developer tools to figure out the URL for the I# symbol, and then extrapolated that for the others. I# ends up being http://d1dhsh1i77j8ju.cloudfront.net/s1/f24/I23I23.png.

Note that ascii hex 0x23 is #. So just extrapolate that out to 123123.png, R23R23.png, etc.

It looks like for the "normal" digipeater symbol, he's just using a sprite from the symbol files he's made (https://github.com/hessu/aprs-symbols).

* PhirePhly#39 - Updated links to point to Kenneth's site.
* PhirePhly#32 - Added digipeater/igate symbol selection section.
@dandrzejewski
Copy link
Contributor Author

dandrzejewski commented Dec 18, 2016

Updated the document and cleaned up the commits a little (I had some other changes committed that I'm not ready for).

@PhirePhly
Copy link
Owner

Looks good. Thanks for the work! I cherry-picked your commit, so you'll want to reset your repo off my current head to keep your history clean. Ideally pull requests come from branches which you dispose of once the owner accepts it.

Clearly I need to hurry up on my plan to port the manual to LaTeX, which is more revision control friendly than odt so more than one of us can work on this at once.

@PhirePhly PhirePhly closed this Dec 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants