I am not a developer. But I have 4 Raspberry Pis working as a master and 3 workers with Kubernetes. I am trying to learn some basic python , git hub, gitops (a method not a tool) and so on. So take it from me I get how hard you have worked and appreciate? your efforts. Being a newly wed I assume you have different distractions than yacc.?
Peace
Scott Sheppard??
On Tuesday, December 17, 2019, 11:13:33 AM EST, Andrew P. <andrewemt@...> wrote:
Greetings, all.
Just letting everyone know the new YAAC mailing list and the YAAC software author aren't dead yet (although I am declaring the old mailing list dead now). I'm still cleaning up the code after debugging and fixing a _very_ annoying GUI rendering issue introduced
by a recent patch to the Java runtime, plus usual bugfixes, and some updates to support large-scale events as discussed on the aprssig@... mailing list a couple of weeks ago. But I hope to have build 143 of YAAC out before Christmas. Whether the large-scale
event support plugin will be ready by then is a different question.
Also, for all those who have asked for the ability to copy YAAC configurations from one system to another, I have reluctantly (i.e., dragged kicking and screaming :-) started implementing an experimental means to re-import a YAAC configuration saved by
the File->Configuration->Export to XML File option. The difficulties were in ensuring that callsign-SSID assignments weren't duplicated on multiple active stations by negligence, and accounting for operating system changes (i.e., no /dev/tty devices on Microsoft
Windows or COMn ports on Linux) during the transfer, while still making it generic to support arbitrary additional configuration data from plugins (and enhancing all relevant plugins to support it). It's a big issue.
So, you'll have an upgrade with some big new features soon.
It's been a long road since I first officially released YAAC back in 2012. Thanks, all, for making it worth the effort.