Christian Lohmaier wrote: >> Are there any plans to move away from our current monolitic binary? > > Well, OOo isn't monolithic - and I don't think there are any new plans > regarding > "splitting it up in separate applications". I guess more effort will be put in > restructuring the parts in a more clever way, so that not all features are > loaded at once, but when they are needed. > Making them truly separate would be a bad idea. Using the same code > in multiple apps is good. But loading seldomly used functions on startup is > bad. > > I think this is really what people have in mind when asking for separate > applications. If you would now split writer, calc, ... into separate > applications, > they wouldn't launch much faster. The big feature set will be loaded > nevertheless. The gain comes only when not all features are loaded at once.
Yes, OOo is not monolithic any you completely got it right: we are on the way to separate the parts better. The applications are already well separated, it's a myth that OOo loads "everything" on startup. It's not even close to that. The "separated apps" approach has only one big advantage, as Kyrill mentioned: a crash will only kill one application. Some smaller advantages like the ability to rund two documents of different type concurrently are not that important IMHO. But the disadvantages are also there: - combined startup time for two or three apps is worse than now (take the startup time from Firefox and TBird wrt. old Mozilla as a proof; I gave some data some months ago in GullFOSS) - memory consumption would go up considerably (as also can be seen comparing FFox/TBird and Mozilla) - the direct interaction between the apps, e.g. OLE embedding would become more complicated, slower and will consume more memory - the integration will get worse as we had to triple all configuration data (as only one application can have r/w access to it), thus also blowing up the disk space. Given the fact that it also would be quite some effort we think that investing this effort in better modularization of the parts is the better choice. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[EMAIL PROTECTED]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
