kcj wrote: I really appreciate the work that has gone into Gscreen (and its derivatives like Gmoccapy), but my feeling is that it is more of a set of building blocks that a developer can use to build a new screen, rather than a complete interface that can be quickly and easily customized and configured by the typical LinuxCNC user.
Actually Gmoccapy was a skin for Gscreen in the beginning.
Gscreen is not a screen as per say, it's an infrostructure. Screens are skins that Gscreen displays.
It is possible to build a basic functional screen with just GLADEVCP widgets. see the docs for an example.
You can add python code to it to do custom things and all of the built in examples do use python code.
By adding more custom widgets to gladevcp, one could build a much more sophisticated screen with just widgets.
gladeVCP was not built with using it without GLADE in mind, so it's not optimized for that but that is just code to be added.
It just seems so wasteful of effort and talent to build another screen mechanism - many people have spent a lots of time on gladevcp and gscreen to do mostly what you want! Just build your custom widgets and help with the gtk3 conversion would be miles ahead.
Chris M
