Changes between Version 2 and Version 3 of BASE_MODEL_TEXTS_R0


Ignore:
Timestamp:
01/08/09 16:36:38 (16 years ago)
Author:
htomov
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • BASE_MODEL_TEXTS_R0

    v2 v3  
    99== Overview == 
    1010In BASE_MODEL_TEXTS task the model and the functionality for the text elements should be defined. The model should allow the creation of chained views, styling of text, rotation, transparency and different modes of wrapping . It should allow persisting of texts along with all the applied attributes.  
    11 The task consists of two logical parts -a model for the text itself and a model for the view components.  
    12 The model for the text consist of styled text and contains information about the font, size, color, opacity, modifiers (bold, italic, underline, strikethrough), attached actions - attributes of the text itself. The chained view components will share a common text model and each will display only part of it.   
     11The task consists of two logical parts  
     12 * a model for the text itself  
     13 * a model for the view components.  
    1314 
    14 The model of the individual text component should contain additional information for the rendering of the text in the particular view – transparency,  rotation, wrapping. The view component model should also contain information what part of the text model it should display, in the case of chained views. A mechanism should exist that will trigger recalculation of the ranges of the texts displayed in different chained views if some change is made in one of them, causing its range to change. Among this kind of changes are insert/remove/replace text, change the size of the view component, changes in the size of some part if the text inside the component, change the wrapping mode of the component and others. 
     151. Text model 
     16 * The model for the text consist of styled text and contains information about the attributes of the text itself  
     17  - font  
     18  - size  
     19  - color  
     20  - opacity  
     21  - modifiers (bold, italic, underline, strikethrough)  
     22  - attached actions  
     23  - other attributes that may appear 
     24 * The chained view components will share a common text model and each will display only part of it.   
     252. Individual text component model 
     26 * The model of the individual text component should contain additional information for the rendering of the text in the particular view  
     27  – transparency 
     28  - rotation 
     29  - wrapping mode  
     30  - other attributes that may appear 
     31 * The view component model should contain information what part of the text model it should display, in the case of chained views.  
     32 * A mechanism should exist that will trigger recalculation of the ranges of the texts displayed in different chained views if some change is made in one of them, causing its range to change. Among this kind of changes include 
     33  - insert/remove/replace text 
     34  - change the size of the view component  
     35  - changes in the size of some part of the text inside the component 
     36  - change the wrapping mode of the component  
     37  - maybe other 
    1538 
    1639A mechanism for persisting both models should be designed and it should be consistent with the overall persistent strategy in Sophie ([wiki:BASE_PERSISTENCE_INTERMEDIATE_STORAGE_R0],  [wiki:BASE_PERSISTENCE_COMMONS_R0]) 
    1740 
     41In both models a undo/redo mechanism should be designed in a way that will allow it so seamlessly integrate with the properties oriented undo/redo mechanism used in sopie ([wiki:PRO_CHANGE_UNDO_MANAGER_R0]).  
     42 
     43Considering the complexity of this task it is probable that parts of it will have to be moved to separate tasks and, in addition, unplanned related tasks can emerge. Such tasks have to be identified and described, during the work. Such tasks may be, for example, the persistence mechanism, the undo/redo mechanism, the  attachment of actions (hyperlink style) to the text, and others. 
     44 
    1845 
    1946== Task requirements == 
    20    For the R_0 focus on  following requirements: 
     47For the R_0 focus on  following requirements: 
    2148 * The model should support chaining of views. 
    2249 * The model should support styling of the text. 
    … …  
    3057 * Create EditorKit ( probably extend the StyledEditKit or RtfEditKit) to support the coordination of multiple chained views, split selection, and persistence 
    3158 * Create DocumentModel (probably extend StyledDocument) to contain appropriate element structure that will support the required functionality. Eventually create a MasterDocument containing all the text and ChainedDocument to represent only part of it displayed in a single component view, using the MasterDocument as a backend.  
     59 * Register appropriate UndoableEditListener and implement integration with with the undo/redo mechanism used in Sopie ([wiki:PRO_CHANGE_UNDO_MANAGER_R0]) 
    3260 * Define the attributes that will describe the text and will be acceptable in the AttributesSets of the elements in the document. 
    3361 
    … …  
    3563[wiki:BASE_PERSISTENCE_INTERMEDIATE_STORAGE_R0][[BR]] 
    3664[wiki:BASE_PERSISTENCE_COMMONS_R0][[BR]] 
    37 [wiki:WRAPPING_TEXT_RENDERING_R0] 
     65[wiki:WRAPPING_TEXT_RENDERING_R0][[BR]] 
     66[wiki:PRO_CHANGE_UNDO_MANAGER_R0] 
    3867 
    3968== How to demo ==