<div dir="ltr">please delete my adress from all chirp-users adress</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Nov 25, 2013 at 5:22 PM, Mike Agner <span dir="ltr"><<a href="mailto:ka3jjz@comcast.net" target="_blank">ka3jjz@comcast.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Actually Bob that's really 2 separate issues. I'll let the CHIRP<br>
developers comment on putting context (by radio) help into the<br>
software. That's a long way off in any case - the wiki has to be<br>
greatly enhanced, first, before that could even be considered. It does<br>
make sense to me, however.<br>
<br>
What I was referring to was the way each radio in the wiki would link to<br>
the pool of pages. A simple example would be a radio that updates in<br>
live mode (and we just saw such an example recently on this list). We<br>
would have 1 page (or 1 set of pages) each for uploading, downloading<br>
and editing a radio's template (image file). Now if that radio was a<br>
live mode one, you don't upload data to it, so the uploading page would<br>
not be linked. It would only have links to downloading and editing.<br>
There would have to be a note on that radio's page that it was a live<br>
mode radio, and that you would need to do a CSV export to save the data<br>
you uploaded.<br>
<br>
Another simple example would be if because of some limitation, CHIRP<br>
could not import EVE files for a particular radio. Then in the list of<br>
import formats on that radio's page, the EVE page would not be linked.<br>
<br>
This is what is meant by selecting pages to be linked from a common<br>
pool. If a particular function isn't available for some reason, there<br>
should be no link to it.<br>
<br>
Mike<br>
==============================================================================================================<br>
On Sat, Robert Terzi wrote:<br>
>/Once all that is done, then each model of radio can point to the<br>
page(s) />/that apply to it, and ignore those that don't.<br>
/I'm not sure if you are just talking about the organization of the wiki<br>
pages, or links from the radio specific (driver) code to launch the<br>
correct page on the wiki. However, the later is something I've thought<br>
about a little, but never suggested because I didn't think there would<br>
be enough critical mass in documentation. It could be helpful if from<br>
Chirp there was the possibility to launch a radio specific web page on<br>
the wiki for help: - before starting the download from radio - before<br>
starting the upload to the radio - after a download or upload has failed<br>
for troubleshooting advice The help menu should also have an entry to<br>
launch the radio specific wiki help page. This means there should be a<br>
little planning in how the wiki pages are named. There should be (some)<br>
correlation to the radio driver since it will have to generate the URL.<br>
The radio specific pages on the wiki should be in their own name space.<br>
I don't know what redmine's capabilities are, the "name space" could be<br>
as simple as prepending a prefix like "Radio-" for all of the radio<br>
specific help template pages. The rationale for this that I believe many<br>
people will attempt to use the software before looking for or reading<br>
any documentation. --Rob<br>
<br>
---<br>
This email is free from viruses and malware because avast! Antivirus protection is active.<br>
<a href="http://www.avast.com" target="_blank">http://www.avast.com</a><br>
<br>
_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
</blockquote></div><br></div>