Difference between revisions of "SFX2 Refactoring"
From Apache OpenOffice Wiki
(→The problem) |
|||
| Line 5: | Line 5: | ||
In result, the model/controller pair are represented in the following way: | In result, the model/controller pair are represented in the following way: | ||
| − | [[Image:sfx2-old.png]] | + | [[Image:sfx2-old.png|thumb|383px|left|What we currently have]] |
| − | + | [[Image:sfx2-new.png|thumb|What we would like to have]] | |
| − | + | ||
| − | + | ||
| − | [[Image:sfx2-new.png]] | + | |
Revision as of 10:41, 14 September 2007
The problem
Though sfx2 no longer is the framework for everything it still is the backbone of the implementation of Writer, Calc, Draw/Impress and Math. sfx2 basically supports the MVC principle but it does not allow to decouple the parts as desired. The "template pattern" approach produces a very tight coupling of all involved classes and traditionally this was even enhanced by the application developers as they didn't try to limit the sfx2 influence as much as possible.
In result, the model/controller pair are represented in the following way:
