Inbox

[W4DBL]

Hi Mooneer,
Thanks for the initiative and best of luck.

One thing that would be nice is the ability to merge various accounts (call signs) into a single inbox. With multiple shares accounts and an amateur account, having everything visible in one place, identified by source would be very useful.

Ideally this feature could toggle each source in the merge on or off and keep the original source inboxes.

This would be similar in functionality to the mail in an I phone when “All Inboxes” is selected.

I’m sure others have ideas as well and as I think of other functionality, I’ll chime back in.

Thanks,
Doug Lynch

[SkyeDog]

Hello Doug & Mooneer. Doug, you can already use the same instance of Winlink Express for your Part 97 and all of your SHARES Account callsigns by adding them to the same instance of Winlink Express after clicking on the discreet down arrow in the space between your first Winlink Callsign and “Settings’ in the upper left corner. Yeah - that was news to me when I learned that just a few weeks ago :) Mooneer - same sentiment as Doug, with added best wishes for massive support flowing your way. After logging in to the subject Github yesterday I couldn’t find where to add suggestions, I’ve since seen where you said to open a new thread. Up first wrt to Forms is to send only the End User input data and the Form’s unique Identification with the end user input and repopulate the form with ser’s input at the far end of each circuit i.e. wherever it is received, This was one of the algorithms straight out of "K&R C Language 1972” re: implementation of *nix ‘pipes’. It can be done while retaining all of the currently existing code that has evolved into the current set of Forms Libraries and capabilities changing only how the The Form’s message is prepped during runtime before being transmitted and again in reverse when the msg is received. Source Code for fillable PDF Forms should be available as a place to start. Beyond this I will think long and hard before making other suggestions after I get a sense for how the Project Team is evolving. My former coding skills are several decades too old to be useful however I have been trying to keep up with this kind of open source project architecture I’m always willing to take phone calls & reply to emails from you. Cheers & 73 Dan Sohn wl7coo & then some ...

…

On May 22, 2023, at 7:35 PM, W4DBL ***@***.***> wrote: Hi Mooneer, Thanks for the initiative and best of luck. One thing that would be nice is the ability to merge various accounts (call signs) into a single inbox. With multiple shares accounts and an amateur account, having everything visible in one place, identified by source would be very useful. Ideally this feature could toggle each source in the merge on or off and keep the original source inboxes. This would be similar in functionality to the mail in an I phone when “All Inboxes” is selected. I’m sure others have ideas as well and as I think of other functionality, I’ll chime back in. Thanks, Doug Lynch — Reply to this email directly, view it on GitHub <#3>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFRDMWTSCXJJLY2I37HDWYLXHQO6TANCNFSM6AAAAAAYLGZUL4>. You are receiving this because you are subscribed to this thread.

[tmiw]

Re: forms, there are some (e.g. USGS DYFI) that basically are just the submitted data. For the rest, is this a bandwidth concern or something else? I was under the impression that the XML attachment most of them add wasn't that big but I could be mistaken.

[SkyeDog]

This will make sense only if you consider it in light of the prime use cases for Winlink Express - as a Contingency & Emergency information system for essential Disaster Response activities aka Emergency Service Functions. A few of the Forms (like the NorCal Winlink Net Check In - found in the non standard forms page on Winlink.org) hardly adds any ‘overhead'. OTOH, many of the best Form enhancements over the last several years have increasingly useful ‘help’ - explanations (like the Mercali seismic intensity scale explanation accessible in the DYFI form’s input screen) or instructions for replying to some of the ICS Forms and Form instructions which are user accessible while filling in the Form will have larger amounts of ‘overhead’ which could be greatly reduced or eliminated - *without changing the Forms*. All of the information which is required to recreate any Standard Winlink Form at the recipient’s end(s) of the circuit(s) is already residing in every Receiving Station's Winlink Express’s Forms Library regardless of which client originates the Standard Form based messages. Keep an eye on the transmission overhead and transmission sizes - compared to the size of the User input data when using any of the Standard Forms over time and the potential savings in transmission size & time to transmit. Comparing it to transmitting just the user's input and the savings will probably surprise you. When there are multiple recipients of a transmission, the ‘overhead', however large or small & however it is encoded or compressed, per recipient of the same Form, is multiplied by the number of recipients. The magic smoke of Winlink’s Forms based Contingency and Emergency Communications is the User input data getting where it needs to be as expeditiously as possible. I readily concede that there are more useful open source enhancements to be made prior to this issue surfacing as a 'too little, too late’ concern for most users. Cheers & 73, dan sohn, wl7coo

…

On May 23, 2023, at 12:16 PM, Mooneer Salem ***@***.***> wrote: Re: forms, there are some (e.g. USGS DYFI) that basically are just the submitted data. For the rest, is this a bandwidth concern or something else? I was under the impression that the XML attachment most of them add wasn't that big but I could be mistaken. — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFRDMWR6NFMOJEULSWUK7LDXHUEHFANCNFSM6AAAAAAYLGZUL4>. You are receiving this because you commented.

[tmiw]

I noticed that #7 was created for the Winlink forms stuff, so I copied some of the comments here to that issue to make it easier to follow.

Also, this issue was added to the list in the wiki: https://github.com/ARSFI/winlink-mail-client/wiki