Changes between Version 23 and Version 24 of WRAPPING_TEXT_RENDERING_R0
- Timestamp:
- 05/29/09 21:02:32 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TabularUnified WRAPPING_TEXT_RENDERING_R0
v23 v24 78 78 * (advantage) The number of transitions in the algorithm vastly decrease, generally resulting in a better layout performance. Here is an example for a one line text with 2 segments: 79 79 80 ''Old Solution'' [[BR]]81 OPEN_TEXT [[BR]]82 OPEN_PART [[BR]]83 OPEN_LINE [[BR]]84 OPEN_SEGMENT [[BR]]85 ATOM [[BR]]86 CLOSE_SEGMENT [[BR]]87 OPEN_SEGMENT [[BR]]88 ATOM [[BR]]89 CLOSE_SEGMENT [[BR]]90 CLOSE_LINE [[BR]]91 CLOSE_PART [[BR]]92 CLOSE_TEXT [[BR]]80 ''Old Solution'' 81 OPEN_TEXT 82 OPEN_PART 83 OPEN_LINE 84 OPEN_SEGMENT 85 ATOM 86 CLOSE_SEGMENT 87 OPEN_SEGMENT 88 ATOM 89 CLOSE_SEGMENT 90 CLOSE_LINE 91 CLOSE_PART 92 CLOSE_TEXT 93 93 94 ''New Solution'' [[BR]]95 OPEN_TEXT [[BR]]96 OPEN_PART [[BR]]97 OPEN_LINE [[BR]]98 SEGMENT [[BR]]99 SEGMENT [[BR]]100 CLOSE_LINE [[BR]]101 CLOSE_PART [[BR]]102 CLOSE_TEXT [[BR]]94 ''New Solution'' 95 OPEN_TEXT 96 OPEN_PART 97 OPEN_LINE 98 SEGMENT 99 SEGMENT 100 CLOSE_LINE 101 CLOSE_PART 102 CLOSE_TEXT 103 103 104 104 * (drawback) EdgeKind.SEGMENT has to be more complex to handle the following cases, some of which make more sense to a segment as a whole (in the old solution the responsibilities were spread between OPEN_SEGMENT, CLOSE_SEGMENT and ATOM EdgeKinds):
