Environment for GUI Customization?

Beginner in LinuxCNC world.  I have built a PrintNC (X,Y1, Y2, X) machine and would like to dabble in user interface customization.  I successfully used PncConf for a Mesa 7i76E configuration and successfully managed movement.

For exploring and user interface development experimentation I am not sure if I should go Axis (specifically I like that is has a window that displays HAL signal names and their state), GMOCCAPY, pyVCP, QtPyVCP, or QtVCP.  Is there a table that contrast and compares each of the various "common" user interfaces or at least provides a description of them in a single place?

I spent the better part of this weekend trying to configure a QtPyVCP development environment and the "instructions" were not helpful where I was successfully using QT and poking around the code.  It seems Gmoccapy and QtPyVCP are in some state of transition with Python 2 being end of life.  I just tried QtPyVCP and the instructions from my perspective are vague, install fresh Debian 11".  Hmmm... would that be "debian-11.2.0-amd64-netinst.iso" or "debian-edu-11.2.0-amd64-netinst.iso".  The 'edu' version just failed to install.  It has been exhausting and frustrating as I am new to the Linux realm.

So...  what development setup is recommended for LinuxCNC novice and where to start?  I have software engineering background with some hardware experience picked up along the way.  Have used Pascal, Fortran, VB, VC, VC++, C++, C, C#, Python, XML, XAML, over the years.

If you wish to work with QTPYVCP, my recommendation would be to follow the steps here
www.qtpyvcp.com/install/bullseye.html

Using Debian 11 is deliberate to avoid any traces of Python 2.7 but you must build linuxcnc from  source.
Be sure to install Debian from the non-free iso to be sure all available drivers are installed.
cdimage.debian.org/cdimage/unofficial/no...nfree/amd64/iso-dvd/

I have to say QTPYVCP is pretty amazing. I have not developed with it but am working with James who wrote those instructions on a new plasma config from scratch. Hopefully I will be using it to cut real parts today after a few test cuts.

tommylight wrote:

kcjengr.github.io/probe_basic/quick_start.html
Download ISO from here, first link:
linuxcnc.org/downloads/
edit
to late.

Don't do this. Follow the steps I gave. 

Of course I recommend Qtvcp - it is included in linuxcnc and works with older systems.
I think it's fairly well documented in linuxcnc's docs.
There are quite a few sample screens already built with it QtDragon and QtPlasmac are the stars.

Gmoccapy is a screen not a system for building screens.
It can be modified but was not built to make that particularity easy, though it has many options to cover most situations.

AXIS is a screen and not a system - it is even worse in this regard.

Pyvcp is too limited - it's ok for simple panels that are incorporated into AXIS.

Gladevcp and Gscreen can be used for building screens but are in python transition still, but people are working on them.

QtPyVCP is a third party project for building screens, with enthusiastic developers. As of late I have read of problems with python3 conversions (I'm sure not for long) and they tend to require newer libraries. I'd say their star is the screen 'BasicPobe'

Chris

 The whole python2 to python3 migration by Linux and then adoption by Linuxcnc has been difficult to manage and forced me to upgrade to later OS versions several times to keep being able to use master branch.

To me the attraction of Debian 11 is that there are no python 2 libraries left in it and it stays faithful to the Debian environment in use. Its frustrating there are no debs being built by the buildbot for it. I don't understand why that is as other Debian releases were supported very quickly.

I have not built screens at all other than some modifications to gmocappy a long time ago. 

What I like about QTPYVCP is its integrated with the python pip installation process and the developers are responsive. I also like how the team member I've been working with has had excellent support from the lead devs. He also uses pip to install updates of his sim. QTPYVCP has some nice features including SQL support for the tool table. Yes their star is currently ProbeBAsic but i think before long Monokrom will become a star as well. I finally was able to cut some production jobs using it today. github.com/joco-nz/monokrom-vcp

PS: Full python 3 support is available in QTPYVCP and its solid.