2009/4/27 Björnke von Gierke <b...@mac.com> > I have been thinking into a similar direction lately. The main issue is > about how to decide what is a component and what isn't. For example a script > editor contains stuff for debugging, auto-completion (... sometimes), > colorisation, undo handling, etc. > So should a "script editor" be one component, or a dozen? It's probably > best to just start somewhere, and then readjust constantly what degree of > atomisation actually makes sense.
For the Script Editor - I'd say the debugger is separate, and the other features you mention should be Script Editor plugins or options. > Also, I think this should be a fork of metacard, and not a replacement of > the current mc ide. I guess that makes sense. Structurally it would be nice if certain MC components evolved for closer interop. So where to start? How about starting with a basic component and create a switcheroo palette which would work in either IDE? Which component, maybe one of: 1. Property Palettte 2. Script Editor 3. Tools Palette
_______________________________________________ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard