Changes between Version 15 and Version 16 of TEXT_CHAINING_BEHAVIOUR_R1
- Timestamp:
- 09/20/09 16:25:52 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TEXT_CHAINING_BEHAVIOUR_R1
v15 v16 67 67 68 68 = Design = 69 The new resource design has already taken in mind text chaining by having two kinds of text frames - head and tail. Here's a more detailed description of the idea plus additional things that are needed.69 The new resource design has already taken in mind text chaining by having two kinds of text frames - head and tail. Here's a more detailed description of the idea and the classes that will be created/modified. 70 70 71 71 * HeadTextFrameR4 extends FrameR4 implements ResourceFrame … … 75 75 * There is a corresponding hierarchy of helpers that have methods for getting these keys. 76 76 77 When a user inserts a text frame, a HeadTextFrame is inserted with a default chaining mode of None. When a user clicks the chain halo button, a hudappears that allows the user to select a frame to be chained or to turn on auto chaining. A frame that is chained is changed to TailTextFrame and its keys for chain head and order are set. The view is responsible for taking information about chaining from the model and redirecting the areas for text displaying to the text layout.77 When a user inserts a text frame, a HeadTextFrame is inserted with a default chaining mode of None. When a user clicks the chain halo button, a HUD appears that allows the user to select a frame to be chained or to turn on auto chaining. A frame that is chained is changed to TailTextFrame and its keys for chain head and order are set. The view is responsible for taking information about chaining from the model and redirecting the areas for text displaying to the text layout. 78 78 79 The existing text chain halo button and hud will be used as a GUI for the chaining. They will be improved by adding a label for the previous/next frame chained and options for auto-chaining and no chaining.79 The existing text chain halo button and HUD will be used as a GUI for the chaining. They will be improved by adding a label for the previous/next frame chained. Options for auto-chaining and no chaining will be added as part of TEXT_AUTO_CHAIN_BEHAVIOUR_R1. They are just part of the overall design for chaining in this task. 80 80 81 81 TextChainingLogic class will be rewritten to provide the expected behaviour for chaining/unchaining frames. It should also be responsible for taking the appropriate action when a chained frame is deleted (this should be done in an operation with a sort key lower than that of the remove frame operation). The same is true for deleting a page that contains head text frames. … … 83 83 The hierarchy of the views follows the hierarchy of the resources and helpers. Each text view holds a TextViewFlow that is used by the layout to display the text. For the layout to display the text correspondingly it is enough to track the chained frames in the getAreas method. 84 84 85 Here follows a class diagram of text classes related to chaining: 85 Some things from that was not clearly described in the analysis is uchaining. Logic for it will be written in the following manner: 86 Clicking either of the unchain button a frame can have breaks the chain at that place. Text is preserved in the first part of the chain, while the second part remains chained but empty. 87 88 Some things from the overview of the analysis are for next revisions: overflow indicator, outlining, and reordering of chained frames. 86 89 87 90 An initial version of the system test for the chaining can be found here: 88 91 89 92 = Implementation = 90 ^(Describe and link the implementation results here (from the wiki or the repository).)^ 93 Describe and link the implementation results here (from the wiki or the repository). 91 94 92 95 = Testing = 93 ^(Place the testing results here.)^ 96 Place the testing results here. 94 97 95 98 = Comments = 96 ^(Write comments for this or later revisions here.) 99 Write comments for this or later revisions here.
