Calligra/Words/Layout restructuring: Difference between revisions
(Created page with 'Development plan for next generation text layout process ---------------------------------------- 1) make kotextanchor use actual odf properties 2) move KWFrame properties over t...') |
No edit summary |
||
| Line 2: | Line 2: | ||
---------------------------------------- | ---------------------------------------- | ||
1) make kotextanchor use actual odf properties | 1) make kotextanchor use actual odf properties | ||
2) move KWFrame properties over to KoShape | 2) move KWFrame properties over to KoShape | ||
- KWFrame remains as sort of hook so framesets will know when a shape is deleted | - KWFrame remains as sort of hook so framesets will know when a shape is deleted | ||
3) move TextSupportShape into the realm of the KoText | 3) move TextSupportShape into the realm of the KoText | ||
- KWord will just ask KoText for a blank one instead of doing a new | - KWord will just ask KoText for a blank one instead of doing a new | ||
- otherwise no movement of functionallity | - otherwise no movement of functionallity | ||
4) move run around over to TextShape | 4) move run around over to TextShape | ||
5) move anchors over to TextShape | 5) move anchors over to TextShape | ||
6) change so TextShape asks for resizedOrNewSupportShape and kword responds | 6) change so TextShape asks for resizedOrNewSupportShape and kword responds | ||
7) reorder layout to be recursive, finally supporting columns and sub tables | 7) reorder layout to be recursive, finally supporting columns and sub tables | ||
Latest revision as of 22:47, 3 January 2011
Development plan for next generation text layout process
1) make kotextanchor use actual odf properties
2) move KWFrame properties over to KoShape
- KWFrame remains as sort of hook so framesets will know when a shape is deleted
3) move TextSupportShape into the realm of the KoText
- KWord will just ask KoText for a blank one instead of doing a new - otherwise no movement of functionallity
4) move run around over to TextShape
5) move anchors over to TextShape
6) change so TextShape asks for resizedOrNewSupportShape and kword responds
7) reorder layout to be recursive, finally supporting columns and sub tables
Investigations that can be undertaken immediately
- figure out how best to distribute evenly in columns
Investigations for step 3 onwards
- factor out the shape related stuff (TextSupportShape,...) from the lib (kotext) into the textShape
- idea is: KoText lib: handles text, style, loading/saving
TextShape: handles and lay out lines of text in a container
Words/application: handles and lay out shapes