Schooner in reference to your comment: "I am confused by your use of 'remote'. Gmoccapy is not a remote GUI, but you were using it. Are you just referring to accessing the controller machine remotely from another computer?
Or are you intending to use an actual remote interface via a loader and machinetalk, like Alex's Machineface or Cetus?" Yes. I have been working on a gui for a while to replace gmoccapy on linuxcnc and to be able to run it remotely. But it turns out that I would have use what I consider to be obsolete methods to accomplish that. My goal has thus changed and drifted away from linuxcnc and towards Machinekit and run the gui I'm working on remotely like Cetus. It may end up running on a touch screen laptop. I'm familiar with and have used Labview for programming remote control application for a good number of years and thus my gui is coded in Labview. Unfortunately there is not much information on how to code protobuf related items in Labview so I will need to work that out. Labview has a Zeromq library so that is not problem. As an aid in getting to understand protobuf coding a bit better I could use Cetus and perhaps do a little network snooping to look at the bi-directional data exchanges to help understand the communication process. About gmocappy on being a remote gui. I used gmocappy only as a starting point to get Machinekit installed and do some preliminary testing and do not intend to keep using it. I use gmocappy on my linxcnc controlled milling machine and thus anticipated that using it for testing would be simplest. That turned out to be a mistake due to differences in available gmocappy versions and axis/joint difference requirements between linuxcnc and Machinekit. Gmocappy buttons: I also believe that picture buttons on anything that controls machinery is a very bad idea based on my own experience with working on past NASA related projects. Plainly marked buttons of a size suitable for a touch screen are fine. But finger tip size is not the same for everyone so touch screen buttons tend to grow larger and take up a large amount of screen area. To save screen area pull down menus excel but in general they do not use buttons and thus are not really suitable for touch screens. Touch screens however can use pop up button panels instead for selected items to save screen area and allow for added functionality. -- 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 [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
