Question about Axis.

Hello,
we are considering the design of a new GUI to suit our custom made front panel, which is designed to allow the operation of the control without a mouse. At the same time we would like a more Haas-esque screen layout because it features a lot of useful information for the machinist like axis and spindle loads, etc. yet keeping the preview.

Our options are either Glade-GTK+-C or Python, in this case starting from Axis and either polling the hal pins from our pendant or triggering events and pass them to the python code. Anyways, the questions is why part of the code (most of the gui actually) is done in tcl when it could have been easily done (without sacrifying functionality ) in tkinter. Is there some reason for that that remains unseen to us or was it just a matter of inheriting old code?


Regards,

Anyways, the questions is why part of the code (most of the gui actually) is done in tcl when it could have been easily done (without sacrifying functionality ) in tkinter.

Or why indeed in Tk of any sort.

Axis has simply been the most complete GUI for a long time and that is how the writer programmed

Have a look at touchy, gscreen and gmoccapy for more recent touchscreen friendly python (and glade) based GUIs

regards