> Thanks - will do. In the meanwhile, how then do I add Komodo to my
> separate Mozilla installation, so it appears within it in the bottom left of
> the lower panel as an "seperate app" along with Communicator/Composer,
> etc (instead of being something which has to be run separately within
> its own Mozilla installation). Is it just a case of merging something into
> one installed-chrome.txt from the other, and copying the necessary
> chrome files?
I have no experience with Komodo, but I assume that the developers
designed it to be a separate app with its own install of Mozilla (which,
given how quickly Mozilla is changing at the moment, is a very sensible
move.) I would suspect, however, that the code changes required to make it
use the "installed Mozilla" may not be enormous.
> I know (two "instances" being two main app windows within the same process),
> thats why I used the quotes. I just mean a top level application window,
> which looks like to separate application copies to the user (its the latter
> which is important here).
So you want MDI? :-)
> > Do you think this is a coincidence? Mozilla has for a long time been an
> > application platform (albeit an unfinished one.) Almost all of what you
> > suggest has been thought of and is planned.
>
> No, I'm not that slow. What you say is exactly what I thought, suggested
> and said. But I haven't yet found any clues (eg. doc/code snippets) about
> support or plans for 5) and I've asked the newsgroups about 9) to
> the reply "its not something which is planned or regularly asked for". These
> are the main points of my suggestion, really. If you know of any URIs
> covering plans/existing support in this area then I'd be grateful if you
> could
> post them.
5) is a function of how the application developer develops their
application. You can write it to integrate with the user's
currently-installed browser, or just install it as a separate application
altogether. It's not something we have control over.
9) is a request for using a different UI paradigm (something akin to MDI.)
There's no reason why this UI style can't be built on top of the Mozilla
framework, but I think the chances of the current Mozilla applications
switching over to it at this late stage are probably quite slim. If you
wanted to build a Mozilla platform that had applications that used this UI
paradigm, that could certainly be done - and you could then install other
apps into it.
The point here is not that Mozilla needs changing or improving to do 9),
it's just that no-one has done it yet and (IMVVHO) it's unlikely to be
taken on board the main distribution - merely because a complete UI
paradigm rearrange would be very disruptive, and you'd need a big
usability improvement to justify it.
Does that make sense?
Gerv
