Difference between revisions of "Writer/ToDo/Writer Refactoring/Automatic Styles"
From Apache OpenOffice Wiki
Line 22: | Line 22: | ||
Use of property pool for other attributes (e.g. tables, graphic objects...) | Use of property pool for other attributes (e.g. tables, graphic objects...) | ||
</pre> | </pre> | ||
+ | |||
+ | == TODO FME == | ||
+ | * make Attribute stack aware of automatic styles | ||
+ | * handle special attributes correctly | ||
+ | * check undo functionality | ||
[[Category:Writer]] | [[Category:Writer]] |
Revision as of 10:44, 1 June 2006
Reason/Goals
Performance of Load/Save will be improved if we got an efficient handling of automatic styles.
The Plan
We will create a property pool which contains all used combinations of hard attributes.
The Steps
Character properties Load: Construction of property sets during loading of documents Edit: Construction/destruction of property sets during editing the document (manually or by API). Format: Use of the property sets for formatting. Status: Use of property sets for status reporting(?). Save: Save automatic styles during XML-export. Ruby properties Use of a property pool for ruby attributes Paragraph properties Use of a property pool for paragraph attributes Other properties Use of property pool for other attributes (e.g. tables, graphic objects...)
TODO FME
- make Attribute stack aware of automatic styles
- handle special attributes correctly
- check undo functionality