>This is as far as I got today. Any comments or improvements on the workflow? >FWIW I would consider this rtos work more important for a linuxcnc 2.6 >release than the redis work that just seems to break the build and cause >problems on 12.04/12.10.
Anders (and anyone else who hasn't had the opportunity to use Michael's redis integration branch): Please - don't throw redis under the bus simply because people haven't had the time to use it. I've been using the http://git.mah.priv.at/gitweb/emc2-dev.git/shortlog/refs/heads/interpreter-python-api-numbered-params branch for several weeks and Michaels's redis integration represents an enormous improvement to the code base with respect to GUI writing. The potential for redis to simplify any number of GUI tasks is enormous. I'm currently use it for python access to the #5xxx g code parameters, as well as a replacement for persistent storage of UI settings (e.g. Touchy's preferences flat file). I see it as a large improvement over the status quo, and I've only begun to scratch the surface of what it can be used for (I haven't looked at the pub/sub stuff, which presents a number of possibilities). I don't have a patch to Axis/Touchy/G Screen to submit with these redis use cases, but perhaps Chris M would be inspired to have a look at Michael's work. One very simple thing to do with redis-params is that it makes it quite easy to display all the G5x work offsets (not just the current set) on a GUI screen, something that wasn't possible before. Daniel Rogge ------------------------------------------------------------------------------ Keep yourself connected to Go Parallel: BUILD Helping you discover the best ways to construct your parallel projects. http://goparallel.sourceforge.net _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
