Difference between revisions of "Global Library Redesign"
(→Libraries to consider) |
|||
| Line 1: | Line 1: | ||
==Libraries to consider== | ==Libraries to consider== | ||
| + | |||
| + | The most interesting libraries in terms of reorganization and redesign are those that collect a huge number of classes that serve very different purposes. Most prominently these are svx, svtools, comphelper, tools, unotools, goodies and to some extent sfx2. | ||
| + | |||
| + | The basic idea is to group the contained classes more content oriented, not hierarchy oriented. "Hierarchically" oriented means that we grouped classes together not by content but by dependencies. Instead of putting all toolbox controllers into a common library we put those controllers using svx classes into svx and others into sfx2. This might have minimized build dependencies in the current environment but it prevented a general optimization. In a general redesign putting them into one library makes more sense. | ||
| + | |||
| + | Some of the classes in these general purpose class libraries may be moved to others that itself are not part of the general reorganization. Example: svtools contains some controls but it would perhaps make more sense to move them to vcl where all the other controls are located. | ||
==Content of svtools== | ==Content of svtools== | ||
==Content of svx== | ==Content of svx== | ||
Revision as of 09:33, 14 September 2007
Libraries to consider
The most interesting libraries in terms of reorganization and redesign are those that collect a huge number of classes that serve very different purposes. Most prominently these are svx, svtools, comphelper, tools, unotools, goodies and to some extent sfx2.
The basic idea is to group the contained classes more content oriented, not hierarchy oriented. "Hierarchically" oriented means that we grouped classes together not by content but by dependencies. Instead of putting all toolbox controllers into a common library we put those controllers using svx classes into svx and others into sfx2. This might have minimized build dependencies in the current environment but it prevented a general optimization. In a general redesign putting them into one library makes more sense.
Some of the classes in these general purpose class libraries may be moved to others that itself are not part of the general reorganization. Example: svtools contains some controls but it would perhaps make more sense to move them to vcl where all the other controls are located.
