It is not qrm'ing the list to take issue with a proposed developmental issue that may negatively impact the program. If implemented, it will impact ALL of us, not just you. If that impact is deleterious, we suffer for your so-called enhancement, so we have every right to voice our opinions and recommendations to the developers. ...and you have every right to ignore or dispute our assertions.
...and the developers can decide what best suits their intentions, after due consideration of your requests, and our feedback. (Both of which are appropriate on this list) 73, N0AN Hasan On Thu, Dec 3, 2020 at 3:32 PM Dave Slotter, W3DJS <[email protected]> wrote: > Just curious -- how many of the people responding to my original message > -- *directed at Bill and Joe* -- are actually going to be coding > anything? Not to be an ass here, but this was not an open invitation to > send QRM to the mailing list. > > If you have code to contribute, great, otherwise, please stop the QRM > about irrelevant stuff. > > I am working on a solution for a particular use case. If this doesn't work > for you, that's totally ok. It will work for me and quite a few other > people. > > -- > Dave Slotter, W3DJS <https://www.qrz.com/db/W3DJS> > > > On Thu, Dec 3, 2020 at 4:25 PM Hasan N0AN <[email protected]> > wrote: > >> Please do not ask the developers to turn WSJT-X into Bloatware. Focus on >> the core functions and let 3rd party apps do the rest. They are out there. >> The interface to them already exists. Don't recreate the wheel and >> negatively impact the decoding of weak signals by trying to make WSJT-X >> into a Swiss Army Knife. >> 73, N0AN >> Hasan >> >> >> On Thu, Dec 3, 2020 at 2:11 PM Adam Bartlett <[email protected]> wrote: >> >>> I want to agree with Jim N2ADV here - WSJT-X is a great application for >>> weak signal work. ACLog/Log4OM/RUMLog are great loggers that will tie to >>> QRZ/HamQTH/a database of US Hams from the FCC's dump/etc, and two of the >>> three are free (plus CQRLog and other tools). In information systems we're >>> moving away from monolithic services/software toward microservice >>> architectures - I see WSJT-X as a weak signal microservice that talks to my >>> logging microservice that might also talk to FLDigi or a SSTV tool. >>> >>> 73, >>> Adam Bartlett >>> N5YHF >>> >>> On Thu, Dec 3, 2020 at 1:38 PM James Shaver (N2ADV) < >>> [email protected]> wrote: >>> >>>> So many users have so many different tastes that the UI really should >>>> be dedicated to decoding functions vs what are “quality of life” >>>> functions. If you try to sharpen a hammer to make it a knife, you’ll have >>>> a mediocre knife and a terrible hammer. >>>> >>>> Just my 2 cents... >>>> >>>> 73, >>>> >>>> Jim S. >>>> N2ADV >>>> >>>> On Dec 3, 2020, at 2:27 PM, Neil Zampella <[email protected]> wrote: >>>> >>>> >>>> >>>> There are many for Windows, and I'm fairly sure that Gridtracker does a >>>> lookup also, and its available for Linux. >>>> As far as modifying the wsjtx_log file, why? Again, you're adding >>>> complexity to the program that is not really needed, and would add to the >>>> support issues seen here. >>>> >>>> Neil, KN3ILZ >>>> On 12/3/2020 11:37 AM, Dave Slotter, W3DJS wrote: >>>> >>>> You said, "there are plenty of third-party bridge, programs that do >>>> this as do many logging programs" >>>> >>>> Please support your statement with specific examples. >>>> >>>> I would like to know which of these run under Linux and directly modify >>>> the file "wsjtx_log.adi" file. >>>> >>>> Thank you. Regards >>>> >>>> -- >>>> Dave Slotter, W3DJS <https://www.qrz.com/db/W3DJS> >>>> >>>> >>>> On Thu, Dec 3, 2020 at 11:29 AM Neil Zampella <[email protected]> wrote: >>>> >>>>> FWIW ... there are plenty of third-party bridge, programs that do this >>>>> as do many logging programs. Adding something that requires Internet >>>>> access both ways, rather than the PSK Reporter's feed only, may cause >>>>> other issues, as well as add on to the support issues often seen here. >>>>> >>>>> Neil, KN3ILZ >>>>> >>>>> On 12/3/2020 8:38 AM, John Nelson wrote: >>>>> > Dave, >>>>> > >>>>> > Scheme to populate name field in log: good idea but — you suggest >>>>> “full names” where it seems to me “first name” would be sufficient and >>>>> appropriate. Comment? >>>>> > >>>>> > — John G4KLA >>>>> >>>>> >>>>> _______________________________________________ >>>>> wsjt-devel mailing list >>>>> [email protected] >>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>>>> >>>> _______________________________________________ >>>> wsjt-devel mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>>> >>>> _______________________________________________ >>>> wsjt-devel mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>>> >>> _______________________________________________ >>> wsjt-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>> >> _______________________________________________ >> wsjt-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
