Hi Daniel, > It seems some developer at machinekit did some good work there. > ... > ... are the best features in machinekit that are missing in linuxcnc.
Hm, I don't think, that a remote ui is something important, that linuxcnc is missing. And I don't take the nml-layer for bad so that it must be replaced. For me, nml-layer is a good piece of C-code, which was easy to adapt for java. The bad thing is the python addon, which can't be worse. So beside the remote accessibility I don't see any feature (in userworld) that machinekit has, which linuxcnc does not have. And replacing the middleware without benefit for the enduser is lot of time wasted (at least for me). For me, a machine is a local system. Some users would like to have an UI running on their mobile phone, but I can't take that for serious. May be acceptable as info board, but not for machining purpuse. And an infochannel is quite easy to workout as addon. That remote stuff could be "outsourced" to developers, that really want that stuff and like to spend their time to achive it. I believe, that the main purpose of linuxcnc is and should be the control of machines. In the sense of realtime responses, it is reasonable, to have all processes local to the machine controller (i.e. the pc that runs linuxcnc). What I really favor is a close coupling between backend and frontend. But that coupling must respect the realtime requirements of the backend. Frontend is always ok to be somewhat slow - as the human eyes are slow. So it does make no sense at all, have a UI which has an refreshrate higher than 24Hz. Nobody can see the difference. So coupling should relax the different timings. cheers Reinhard _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
