| 88 | [[Image(source:trunk/sophie2-platform/doc/uml-design-diagrams/hotText/HotText - model.png)]] |
| 89 | |
| 90 | For proper styling we should have proper nesting that's why it's a good idea this logic to be presented like a stack with proper sequence call to |
| 91 | pop/push operations. Even more, the number of operations with values is a finite number, and to become more error prone this is how the design looks: |
| 92 | |
| 93 | [[Image(source:trunk/sophie2-platform/doc/uml-design-diagrams/hotText/HotStyleDef-model.png)]] |
| 94 | |
| 95 | Sophie2's formatted text is one that should not work only in rectangle areas, that's why we need a a custom graphical component and a layout mechanism. |
| 96 | |
| 97 | The custom graphical component is a scene element that uses the graphical context to draw the formatted text |
| 98 | |
| 99 | [[Image(source:trunk/sophie2-platform/doc/uml-design-diagrams/hotText/HotTextIntegration.png)]] |
| 100 | |
| 101 | The layout mechanism is most appropriate to be a graph where where each route have a cost and then the path with the minimal cost will be used |
| 102 | |
| 103 | [[Image(source:trunk/sophie2-platform/doc/uml-design-diagrams/hotText/HotTextLayout-model.png)]] |