[chirp_devel] Thoughts on upload/download terminology

[Matthew Poletiek]

Probably thinking about it too hard myself, but here are some thoughts.

Upload and download infer a temporary, potentially unstable connection or a
remote/temporary target.

Read and write infer something less remote and much more stable and
consistent.

I think upload and download make the most sense for this use case
considering protocols in use and the temporary connection or potentially
unstable one.

Read and write might set expectations too high for some users.

2cents.

On Fri, Jan 20, 2023, 17:34 Dan Smith via chirp_devel <
chirp_devel at intrepid.danplanet.com> wrote:

> Hi all,
>
> Someone just filed a bug about the fact that CHIRP-next uses only "upload"
> and "download" in the Radio menu. This wasn't intentional, but is a
> departure from what it used to be, which is "Upload TO radio" and "Download
> FROM radio". Changing that completely now *might* catch some users
> off-guard, but I think he's probably right that the single-word options are
> too vague.
>
> Any strong opinions on moving from upload/download (to/from radio), to
> "Read from Radio" and "Write to Radio"? Even "Read" and "Write" might be
> okay, given they're under the "Radio" menu.
>
> https://chirp.danplanet.com/issues/10303?next_issue_id=10301
>
> I initially knee-jerked in my usual hates-change way to moving to
> read/write but perhaps that would be better, and does (I think) match other
> software.
>
> --Dan
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20230120/9d2aac93/attachment-0001.html