[chirp_devel] Need of a new wiki page
Hi to all,
We have now the driver class alias feature that allows to show the alias (clones) of some Chinese radios up front in the UI, but this new feature has a drawback: once the user save a img of this radio clone that image stop being from the clone and when opened again will show itself as the original radio, not the clone.
Tom has make a mod to the save operation to include a pattern ( {vendor}_{model}_{date}.img ) in the name to easy this, but some users may have some problems with this or at least it will generate some noise in the site/lists with users complaining about this.
I vote to create a wiki page called "Radio clones" in which we explain why the users see his FooBar-300 is showed as china_radio-123 when opened from a image file, this will allow us to tag the clones on the "Supported Radios" page as clones and redirect to the "Radio clones" wiki page, or even when the noise arose in the site/list we will have a link to send and stop infinite threads...
I can generate a draft for the page for the wiki admins to put in place. (That draft will require some revision as I know my english is not so good yet)
Is this a good idea?
If so, please wiki admins contact me off list to coordinate.
Thanks.
Is this a good idea?
Yes.
I can generate a draft for the page for the wiki admins to put in place. (That draft will require some revision as I know my english is not so good yet)
No need to do this. Just create the page and let people edit it when you're done. That's how wikis are supposed to work :)
--Dan
El 27/06/16 a las 11:31, Dan Smith via chirp_devel escribió:
No need to do this. Just create the page and let people edit it when you're done. That's how wikis are supposed to work:)
--Dan
I know... but I have not enough wiki power to create a new page.... that's why the email...
Check it here http://chirp.danplanet.com/projects/chirp
:-[
The page is alive now at:
http://chirp.danplanet.com/projects/chirp/wiki/Aliasing_for_radio_clones
I would appreciate revisions/comment/improvements of it from the developers team as I'm not a native English speaking OM.
I will wait for at least one revision to link it and comment on the supported radio page.
73.
El 27/06/16 a las 13:23, Dan Smith via chirp_devel escribió:
I know... but I have not enough wiki power to create a new page.... that's why the email...
That's unintentional. Try now.
--Dan _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
I would appreciate revisions/comment/improvements of it from the developers team as I'm not a native English speaking OM.
My edits:
http://chirp.danplanet.com/projects/chirp/wiki/Aliasing_for_radio_clones/dif...
I removed the implication that we'll keep the list of aliases up do date because I know we won't ;) We can also generate that list from the data we have in the code, like I do for model_support.html.
Thanks!
--Dan
Roger, agreed on the changes,
I will make a note on the Supported Radios for the users to know about this.
73 and Thanks.
El 01/07/16 a las 12:51, Dan Smith via chirp_devel escribió:
I would appreciate revisions/comment/improvements of it from the developers team as I'm not a native English speaking OM.
My edits:
http://chirp.danplanet.com/projects/chirp/wiki/Aliasing_for_radio_clones/dif...
I removed the implication that we'll keep the list of aliases up do date because I know we won't ;) We can also generate that list from the data we have in the code, like I do for model_support.html.
Thanks!
--Dan _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
I will make a note on the Supported Radios for the users to know about this.
Thanks, but I think we should change the wording a bit. Looks like you've been doing this:
* Foobar99 (it's a clone)
The phrasing of that in a list is a little strange. Also, I think it would be better to just say (clone) and even better if we can mention the model it's a clone of. What about:
* Foobar99 (clone of Snarfblatt UV-42)
What do you think?
--Dan
On Sat, Jul 2, 2016 at 11:21 AM, Dan Smith via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
I will make a note on the Supported Radios for the users to know about this.
Thanks, but I think we should change the wording a bit. Looks like you've been doing this:
- Foobar99 (it's a clone)
The phrasing of that in a list is a little strange. Also, I think it would be better to just say (clone) and even better if we can mention the model it's a clone of. What about:
- Foobar99 (clone of Snarfblatt UV-42)
What do you think?
--Dan
I would rather use for "clone". Clone sort of implies that one vendor came out with their radio first and then it was copied by another.
But what happens here is we add support for a radio to CHIRP. Then as time goes by we come across another radio that happens to program exactly the same way. Because it got to us 2nd (or 3rd and so on), we call it a clone of the first radio.
- Foobar99 (clone of Snarfblatt UV-42)
When in actuality the Foobar99 was on the market long before the Snartblatt UV-42.
To me it is in the "family of Snartblatt UV-42" or it is a "Smartblatt UV-42 variant".
I vote for "variant" since it is it has already used for a long time to describe the plethora of radios that are similar to the UV-5R.
Jim
I would rather use for "clone". Clone sort of implies that one vendor came out with their radio first and then it was copied by another.
But what happens here is we add support for a radio to CHIRP. Then as time goes by we come across another radio that happens to program exactly the same way. Because it got to us 2nd (or 3rd and so on), we call it a clone of the first radio.
Sure, variant or family sounds fine to me. Excellent point about the relative ordering of the CHIRP driver vs. actual release :)
--Dan
I get late on the discusion but agree with the variant or family logic, good point.
73 Pavel CO7WT
El 02/07/16 a las 15:46, Dan Smith via chirp_devel escribió:
I would rather use for "clone". Clone sort of implies that one vendor came out with their radio first and then it was copied by another.
But what happens here is we add support for a radio to CHIRP. Then as time goes by we come across another radio that happens to program exactly the same way. Because it got to us 2nd (or 3rd and so on), we call it a clone of the first radio.
Sure, variant or family sounds fine to me. Excellent point about the relative ordering of the CHIRP driver vs. actual release :)
--Dan _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
participants (3)
-
Dan Smith -
Jim Unroe -
Pavel Milanes (CO7WT)