One of the effects would be that core developers weren't forced to spend much time to make decision which _one_ solution would be the good one for all users, as they often do. Instead they could implement _every_ way that made sense or even was a known way.
that is a significant reason, I sense that there are quite a few different directions that OpenOffice is being pulled in, and it'll be much easier if with such a big thing specialised versions could be created Also individual users have a particular way of setting things up, then they want to be able to carry that configuration around.
In addition an other point of view: Imagine there was a framework, which allowed building that configuration sets (let's call them "capes" to complete the suite? :o))) in an easy way. This made it possible to widely extend the resources of active OOo development by separating core development from GUI development. The latter could be done by the new founded ux project.
consider, in the Office 2007 thread, which is now centered around the proposed integration with thunderbird. Mathias recently mentioned the idea of moving OpenOffice interface to xul, which has the benefit of a established way of developing interface modifications (xul overlays) However I gather that would be a lot of work. Also it's a slightly different idea I think to configuration sets - themes, which could be controlled by configuration but, it's not to be confused. So a 'cape' might consist of a configuration set and a theme, which is automatically applied. -- Chris Monahan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
