Re: [Machinekit] Looking for examples of conversational machine interface

[schoone...@btinternet.com]

ngcgui in linuxcnc is quite widely used http://linuxcnc.org/docs/html/gui/ngcgui.html This was Deweys' stab at conversational programming, largely successful, if a bit difficult to set up properly for a novice. It has been developed even further recently, but I haven't followed it. Andy Pugh wrote some metric lathe routines, which were even further polished, with pretty graphics, but this is gtk2 / python / gladevcp and all starts falling apart when you use a recent distro with gtk3. https://www.forum.linuxcnc.org/forum/41-guis/26550-lathe-macros Linuxcnc has some `simple code generators` also, including one of mine. http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Simple_LinuxCNC_G-Code_Generators I use the same ngcgui subroutines I wrote for ngcgui, through a Qt interface which generates the code in a similar fashion without all the python, gtk, tcl clutter. It is currently stand alone, but could be embedded Very useful for bread and butter surfacing, slotting, PCD drilling etc etc On 20 Nov 2017, at 00:29, Chris Albertson <albertson.ch...@gmail.com> wrote: As the title says.  I'm collecting ideas and the best place to start is with good examples of what is currently available today. A conversational interface to a milling machine is one that does not expose G-Code or CAD/CAM to the user.  The user "tells" the machine what he wants, usually by selecting from a short menu.  The machine provides a preview of what he asked for.  Possibly the user sees a mistake and makes a correction and then finally says "Do it." There are some serious limits to what can be done with this kind of interface.  But also the simple kinds of operations that can be done are common and useful.   For example surface milling a large flat area, boring a hole of a given diameter and depth or making a pocket. What I'm looking for is examples of this kind of user interface and opinions, good or bad.  Anyone have links to products and experience (good or bad) using them. My goals to make something VERY SIMPLE to do one-off machine tasks.  This kind of software is NOT real-time so it could run on any hardware, even a cell phone. Please don't say you would never us this because you write g-code.  No, you do that only because it is the least bad option. Sorry to cross post this.  I know some of you will see this twice -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.