On Wednesday 28 January 2009, Eric H. Johnson wrote: > <minor rant> > I don't mean to step into a hornet's nest, and may well be my ignorance, as > I have never made any attempt to learn Python or TK/TCL for example, but it > seems to me that there is an awful lot of duplicated functionality across > the various UIs. > > I have been wondering for some time if there would be significant benefit > in implementing a unified UI API or other means of handling the parts > common to all UIs. A preprocessor / filter would just be one of those > common parts. </minor rant>
In the beginning, it was convenient just to copy an entire file, edit a couple of lines and call it a new interface. Over time, new "features" would be added to one or another and possibly a bug fix or two. When changes at another level were required to either fix a problem or add additional functionality, it became problematic because it might break an interface or two. As you rightly point out, the right way would be to implement a core library so that new features would be accessable to all interfaces with a minimum of effort. Indeed, there were attempts to do this at an early stage of emc2 "development" (which you have since duplicated in part), but the work was rejected for the flimsiest of excuses. As a result of ad hoc "development", when expediency of early implementation is found to be wanting, it is much easier to copy and hack rather than dealing with the root cause. This is applicable to all levels, not just the GUI, but there is not the stomach to resolve the underlying problems. I wish you luck, but I fear the worst... ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
