Changes between Version 9 and Version 10 of TEXT_MODEL_REDESIGN


Ignore:
Timestamp:
03/24/10 15:32:21 (15 years ago)
Author:
kyli
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TEXT_MODEL_REDESIGN

    v9 v10  
    5050== TEXT MODEL PART == 
    5151 
    52  The idea of the new text design is to remove the existing stable poses with unstable indexes. 
     52The idea of the new text design is to remove the existing stable poses with unstable indexes. 
    5353  
    5454In order to achieve this functionality the following changes have been made: 
    … …  
    132132== TEXT LAYOUT PART == 
    133133 
    134 === Text Layout === 
    135  
    136  Why should TextLayout be removed from our code: 
     134Why should TextLayout be removed from our code: 
    137135 
    138136 * We only use the nextLayout() method,  get the line metrics and get the text hit info (determine which char hits a concrete Point2D) from it. Drawing with TextLayout is actually problematic, since it causes the baseline zig-zagging problem. Thus we use tons of reflection, which I suppose is not good. 
    … …  
    140138 * TextLayout is constructed by a LineBreakMeasurer, which demands AttributedCharacterIterator to be made out of the HotText. In the current situation, this could cause some performance problems with large texts and many styles. On the other hand, LineBreakMeasurers need to be cached in order to have better performance (so says the JavaDoc), but they are statefull. So, simultaneous usage is quite undetermined (this could happen with the backgound thread which is used by the lazy layout). 
    141139 
    142  What to use instead: 
     140What to use instead: 
    143141 
    144142 * '''Definition''': a TextRun is a sequence of characters with equal styles.  
    … …  
    160158 * Tabbed text: tabs can be calculated when creating the segment layouts. First of all, we must ensure that if the HotText breaks the text runs if a tab is met (e.g. a tab can only be in the end of a run). Next, put a constant in SegmentLayout which defines the max tab width (the logical width). Then we determine the actual tab width with the formula ''tabSize = MAX_TAB_WIDTH - tabXPos % MAX_TAB_WIDTH''. We add the calculated value as an offset between the current glyph vector and the next one. This way, in a rectangular area, the tabbed text will be aligned and will look cool.  
    161159 
    162 === Positioning === 
    163  
    164160 * Since the HotPos will be removed, HotLayout should not use it. So simply replace all the HotPos-related methods with int-related ones. 
    165  
    166  
    167161 
    168162== Tests == 
    169163 
    170164 * We should make all the current text and layout-related tests to work again. 
    171  * New tests: [browser:branches/private/kyli/2344/modules/org.sophie2.base.model.text/src/test/java/org/sophie2/base/model/text/smart/TextPerformanceTest.java Performance test], [browser:branches/private/kyli/2344/modules/org.sophie2.base.model.text/src/test/java/org/sophie2/base/model/text/smart/ImmTextTest.java] 
     165 * New tests: [browser:branches/private/kyli/2344/modules/org.sophie2.base.model.text/src/test/java/org/sophie2/base/model/text/smart/TextPerformanceTest.java Performance test], [browser:branches/private/kyli/2344/modules/org.sophie2.base.model.text/src/test/java/org/sophie2/base/model/text/smart/ImmTextTest.java ImmText test]. 
    172166 
    173167= Implementation =