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.
Also, I think this should be a fork of metacard, and not a replacement
of the current mc ide.
On 27 Apr 2009, at 14:48, David Bovill wrote:
...so I thought that might be a good place to start = Script Editor
Switcheroo API. That is a way to switch between different Script
Editors, and to be able to define and add your own alterrnatives. ...
--
official ChatRev page:
http://bjoernke.com/runrev/chatrev.php
Chat with other RunRev developers:
go stack URL "http://bjoernke.com/stacks/chatrev/chatrev1.3b3.rev";
_______________________________________________
metacard mailing list
metacard@lists.runrev.com
http://lists.runrev.com/mailman/listinfo/metacard
