On Feb 4, 2009, at Feb 4, 2009--3:27 PM, alex.joni wrote: > It's not actually removing things from pyvcp. Pyvcp still can do > all the > things it did a week ago. > The question at hand was what to include into stepconf generated > configs. > (Note: stepconf is a utility which helps users to set up simple emc2 > configurations). > So the actual question wasn't about things belonging to pyvcp or > not, but > rather in a stepconf generated config. > A stepconf config currently only supports one interface: AXIS. > So the pyvcp embedded along with AXIS is certainly a more > specialized case > then a general pyvcp use. > > Regards, > Alex >
On the subject of stepconf and pyvcp, it would be really nice if there was a way to define halui cmds that was not over written on subsequent invocations of stepconf. Since halui commands are now edited into the ".ini" file, they are subsequently overwritten the next time that stepconf is invoked. Just an idea but a "custom.ini" include file like "custom.hal" might be a solution. Alan --- Alan Condit 1085 Tierra Ct. Woodburn, OR 97071 Email -- [email protected] Home-Office (503) 982-0906 ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
