| 1 | [[BackLinksMenu]] |
| 2 | |
| 3 | [[TicketQuery(summary=BASE_MODEL_TEXTS_R0, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|)]] |
| 4 | |
| 5 | |
| 6 | |
| 7 | = Analysis = |
| 8 | |
| 9 | == Overview == |
| 10 | In BASE_MODEL_TEXT task the model and the controller for the text elements should be defined. |
| 11 | |
| 12 | == Task requirements == |
| 13 | * The model/controller should support chaining of views. |
| 14 | * The model/controller should support styling of the text. |
| 15 | * The model/controller should support selection split over more than one view. (selection of text starting in one view and continuing in another) |
| 16 | |
| 17 | |
| 18 | == Task result == |
| 19 | The result of this task should be design description and prototype implementation code. |
| 20 | |
| 21 | == Implementation idea == |
| 22 | * Extend the StyledEditKit or RtfEditKit. |
| 23 | * Implement a DocumentFilter subclass to achieve the requested behavior. |
| 24 | |
| 25 | == Related == |
| 26 | |
| 27 | |
| 28 | == How to demo == |
| 29 | * Create a frame containing more than one text views over the same model, prefilled with text, with at least two different styles. |
| 30 | * Observe the different styles |
| 31 | * Type some text in the views and observe the splitting of the text on different views. |
| 32 | * Select some text with part of the selection at the end of the first view and part – at the beginning of the second. |
| 33 | * Copy and paste the selected text to ensure the selection is correct |
| 34 | |
| 35 | = Design = |
| 36 | |
| 37 | = Implementation = |
| 38 | ^(Implementation results should be described and linked here (from the wiki or the repository))^ |
| 39 | |
| 40 | = Testing = |
| 41 | |
| 42 | = Comments = |
| 43 | In future releases the model will probably have to support also the following functionality: undo/redo, custom styles, attaching actions to text ( hyperlinks style), pagination, search/replace, spell check, read/write to stream/reader/writer (serialize) |