pyngcgui

andypugh wrote:

tjamscad wrote:

What does this have not have? Benifits over current GUI's?

The new thing here is not the GUI (it's just normal "Touchy") but the integration of ngcgui which is somewhere between a macro language and a conversational programming interface.
linuxcnc.org/docs/html/gui/ngcgui.html

Thanks, Andy. I don think this is something that I would use in a production shop. But, I can see that it would be useful for a smaller 1 or 2 guys size shop.

BigJohnT wrote:

It really doesn't matter how many guys you have in the shop but what kind of things your making. If you doing production work your needs are 180 degrees out from people doing one-off''s and people building custom design equipment. If you have a lathe that does one-off's then your missing the boat by not using the power of ngcgui. I can take a print and walk up to my Hardinge CHNC and in a minute have a part running on the lathe from start to finish. It takes me longer to change the collet than it does to program the part in.

John

Good point John, If you were doing one-of type of work that didnt need a model and a drawing it would come in handy to have a macro-wizzard type of thing to use. I am not trying to say what you have here is bad it just doens't fit my enviorment. Sorry for the disruption.

I sent a message to Dewey about pyngcgui and never heard back .. Is he on here? maybe the mail list would be better ....

i haven't looked at pyngcgui for a while but a current patchset (for git-master) is at:
www.panix.com/~dgarrett/pyngcgui/v043.patch

The patched code includes gladevcp widgets for:
PyNgcGui -- compatible with the existing tcl implementation of ngcgui
Hal_GremlinPlus -- a gremlin viewer with some built-in buttons

Included demonstration configs are:
configs/sim/ngcgui/pyngcgui_gscreen.ini
configs/sim/ngcgui/pyngcgui_gscreen_popupkeyboard.ini

and (non-gladevcp) demos for touchy:
configs/sim/ngcgui/pyngcgui_touchy.ini
configs/sim/ngcgui/pyngcgui_touchy2.ini
configs/sim/ngcgui/pyngcgui_touchy_lathe.ini
configs/sim/ngcgui/pyngcgui_touchy_small.ini

These sim configs work with (existing) ngcgui-compatible gcode files
like the ones located in nc_files/ngcgui_lib

Also included are standalone applications:
gremlin_view (use --help for info)
pyngcgui (use --help for info)


To try in a rip build::
$ cd src # the src directory in a git clone
$ git pull # make sure master is up-to-date
$ git checkout master # start in master branch
$ git branch ptst # make a test branch
$ git checkout ptst # use the new test branch
$ git am v043.patch # apply the patch
$ make && sudo make setuid # build
$ . ../scripts/rip-environment # ensure environment in all shells
$ linuxcnc ../configs/sim/ngcgui/pyngcgui_gscreen.ini
etc.

If you start another terminal to try the standalone applications be
sure to source rip-environemnt there too

pyngcgui update:

The latest patch (v045) for git master includes:

1) gladevcp widget: Python Ngcgui -- pyngcgui (uses ini options NGCGUI_*)
2) gladevcp widget: Hal Gremlin Plus -- hal_gremlin with some buttons
3) standalone pyngcgui (for help: pyngcgui -h)
4) standalone gremlin_view (for help: gremlin_view -h)
5) a popup numeric keyboard suitable for touchscreen usage
6) 4 example ini files based on touchy (includes gremlin)
7) 2 example ini files based on gscreen
8) 1 example ini file based on axis
(compatibilty demo, the tcl based ngcgui integrates better with axis)

The patch is at:
www.panix.com/~dgarrett/pyngcgui/v045.patch

Instructions for applying the patch:
www.panix.com/~dgarrett/pyngcgui/pyngcgui.txt

Dewey are you interested in adding this to linuxcnc repo?
if so, do you think it's ready enough now?

Chris M

I think it is ready but could benefit from tests by users. That would be simplified if it were in master and available with a buildbot package instead of requiring a user to patch the source tree.

The patch is mostly new code and is thus a non-interfering set of changes. There are a few code changes to touchy to let it (optionally) include gremlin and pyngcgui. Cradek will probably want to review.

i'd vote for it to be pushed to master , that way any bugs can be found and ironed out in use ( although iv'e not found any as yet )
and thanks to Dewey for the work on the upgrade to glade .