2009/4/27 Björnke von Gierke <span dir="ltr"><<a href="mailto:bvg@mac.com" target="_blank">bvg@mac.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
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.<br>
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.</blockquote><div><br>For the Script Editor - I'd say the debugger is separate, and the other features you mention should be Script Editor plugins or options.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Also, I think this should be a fork of metacard, and not a replacement of the current mc ide.</blockquote>
<div><br>I guess that makes sense. Structurally it would be nice if certain MC components evolved for closer interop. <br><br>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:<br>
<ol><li>Property Palettte</li><li>Script Editor</li><li>Tools Palette</li></ol></div></div><br>