Whilst I am a competent programmer with C and struggle to code in Python, I think enforcing C++ on GUI users would be a disaster. An interpreted language is much easier to work with and to add the overhead of compilation to a quick GUI tweak will leave users out in the cold. I persevere with Python because I know that I can solve problems in Python in 100 lines of code that would take 1000+ lines in C. Heck we write whole ERP systems in Python (Have a look at Odoo ERP previously Open ERP), so to string a few lines together for a GUI is a walk in the park for Python.
Only using C++ would basically stop the customisation of this wonderful software in its tracks and force users to continue to use an archaic GUI called Axis. It might be good from a programmer's perspective but its just too far out of date in terms of where software development and user expectations are today. I personally think that we need to adopt Python3 ASAP and yes I just got dragged kicking and screaming from Python 2.7 to 3.0 but I did it. Once Python 3.0 is upgraded the next major body of work should be to release a new, modern GUI as the Linuxcnc default. Keeping the current third party developers would be a a smart option because some of them have done an amazing job and have kept their work in Git repositories so it is sitting there ready to be pushed into Master branch of LinuxCNC which is bound to save an enormous amount of work for the developer team. So not to do what Andy has suggested would really be a bad move in my view. Rod Webster *1300 896 832* +61 435 765 611 VMN® www.vmn.com.au On Sat, 2 May 2020 at 17:14, Nicklas Karlsson <nicklas.karlsso...@gmail.com> wrote: > Use this gtk interface and it works but must install older version of > glade. > > Still consider C++ a better option than python and I used both but if > someone wrote in python I am of course a grateful user. Main reason for > rather soft real time like GUI is static types so compiler could check > pieces fit together before program is run. > > > > Actually I would just link to the QtPyVCP web site qtpyvcp.com > > > > JT > > > > On 5/1/2020 4:28 PM, Gene Heskett wrote: > > > On Friday 01 May 2020 16:38:01 John Thornton wrote: > > > > > >> Sounds like a good idea to me. > > >> > > >> JT > > > I think so too John, but verifying that all those extras are alive and > > > well is more than I'll ask our limited manpower to do, so just the > > > mention of something google should find s/b more than enough. > > >> On 5/1/2020 7:17 AM, andy pugh wrote: > > >>> I wonder if the docs should mention the GUIs that are made for > > >>> LinuxCNC but are not part of LinuxCNC? > > >>> > > >>> I am thinking of > > >>> http://www.qtpyvcp.com/showcase/mill_vcps.html > > >>> And > > >>> https://github.com/DjangoReinhard/JCNCScreen > > >>> > > >>> And maybe also PathPilot. > > >> _______________________________________________ > > >> Emc-developers mailing list > > >> Emc-developers@lists.sourceforge.net > > >> https://lists.sourceforge.net/lists/listinfo/emc-developers > > > > > > Cheers, Gene Heskett > > > > > > _______________________________________________ > > Emc-developers mailing list > > Emc-developers@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/emc-developers > > > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
