Difference between revisions of "Writer/ToDo/Writer Refactoring/Automatic Styles"
From Apache OpenOffice Wiki
Line 30: | Line 30: | ||
* New implementation of Merge function OK | * New implementation of Merge function OK | ||
* handle special attributes correctly OK | * handle special attributes correctly OK | ||
− | * SwTxtAttr flags: What do they mean | + | * SwTxtAttr flags: What do they mean OK |
− | * Toolbar should consider autofmt | + | * Expanding attributes OK |
+ | * Toolbar should consider autofmt OK | ||
* Check redlining | * Check redlining | ||
* html/ww8/rtf filter | * html/ww8/rtf filter |
Revision as of 09:19, 9 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
- Portions in hints array OK
- make Attribute stack aware of automatic styles OK
- check undo functionality OK
- Copy & Paste OK
- New implementation of Merge function OK
- handle special attributes correctly OK
- SwTxtAttr flags: What do they mean OK
- Expanding attributes OK
- Toolbar should consider autofmt OK
- Check redlining
- html/ww8/rtf filter
ToDo AMA
- create style pool functionality in svtools: class StylePool
- create style pool management at SwDoc: interface IStylePoolAccess
- develop uno interface of XAuto..-classes
- use uno interface during import
- use uno interface during export