Difference between revisions of "Writer/ToDo/Writer Refactoring/Automatic Styles"

From Apache OpenOffice Wiki
< Writer‎ | ToDo
Jump to: navigation, search
m
Line 23: Line 23:
 
</pre>
 
</pre>
  
== TODO FME ==
+
== ToDo FME ==
 
* make Attribute stack aware of automatic styles
 
* make Attribute stack aware of automatic styles
 
* handle special attributes correctly
 
* handle special attributes correctly
 
* check undo functionality
 
* check undo functionality
  
 
+
== 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 durign export
  
 
[[Category:Writer]]
 
[[Category:Writer]]

Revision as of 07:34, 2 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

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 durign export
Personal tools