Re: [M-dev]Questions concerning Cranberry

[Owen S. <ow...@ma...>]

On 1/31/02 3:27 PM, "Mike Benonis" <mbe...@ma...> wrote:

> [snip]
> 
> 2.  I'm considering a plugin-based graphical architecture for editing MML
> documents, similar to some of the older editors.   Is this important to you,
> and if so, should I:
>   A)  Finish up, release without it now, and add it to the next version
>   B)  Add it before I release this version
> 
> Take into consideration that this may take a while (read: more than a month)
> to implement.
I'd say you should do a release, even if it's only a .5, then do a full 1.0
after adding the graphical system...

Not quite sure how you're going to pull off plugins that define their own
windows + control behaviors, but I guess it's possible with a lot of work.
IMO it would be much easier to just release the RB source, and make a set of
standard methods that windows can access to get data, perhaps in an
abstracted format to make it easier to read/edit, since the app can already
do both of these, maybe it could have methods to do it that each window can
easily access in an abstracted way. Then, people can just make new windows
for editing different elements, and drag them into the project and recompile
with very little code changes needed (hopefully, if it was done in a modular
enough way). This would be the best in my opinion, and much easier than
designing a full-fledged plugin system.
> 
> 3.  What features do you need to make Cranberry your MML editor instead of
> tools like BBEdit or another text editor?
> 
> My goal is to make Cranberry the ultimate Aleph One program, that does
> everything you want it to, and is the easiest program in the world to use.

How about a fully graphical B&B editor then, complete with 3 view graphical
3d editing ;) (j/k, this would be a huge amount of work, and would go better
with a map editor than an XML/MML editor.)

-- Owen
"Live simply that others may simply live" - Gandhi