On Thu, 09 Aug 2012 08:08:27 -0700, dave wrote: > > As a longtime user(1) I'm going to butt in here. My main worry is > that > this will break most of the GUI's. I use TkEmc and Mini most of the > time. As a user I'm not going to complain as long as things "just > work". > > Interp and motion need to modular enough to one can drop in a new or > different interp; here I'm thinking about 4-5 axis vector programming > and there will be other things that are useful or just passing fads. > > Planning for non-intel cpu's seems essential as does communication > with > the HML via a network as that seems easier than implementing a > specific > new protocol just to drive the HML. > I like the idea of setting up a flat screen/mouse/keyboard and having > it > stay static even though the underlying motion stuff changes. > > Discussion is good and appreciated.
there are a couple of things that need to be addressed here. Just because we are discussing changing things does not mean that the current codebase needs to become broken. In fact it should basically freeze and only add bug fixes. The real development effort should go into the new code base. If we get into the age old push of it works (kinda) so "DON'T TOUCH IT" then we will never make any significant changes. I saw this happen before. EBo -- ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
