| | 26 | * The code for every part of the UI should be reviewed. |
| | 27 | * Some parts may appear to be OK. |
| | 28 | * Other parts may need a redesign in order to meet the requirements. |
| | 29 | * UI should become consistent with the new resources, changes and templates (see [wiki:GROUP_RESOURCE_MODEL_REDESIGN_R0], [wiki:HOT_TEXT_REDESIGN_R0], [wiki:GROUP_BOOK_MODEL_REDESIGN_R0]). |
| | 30 | * For UI parts that need attention define a more suitable design. These include: |
| | 31 | * Layout |
| | 32 | * MyDoggy - the whole "org.sophie2.main.layout.mydoggy" module should be rewritten (Flaps, tabs and palettes part). |
| | 33 | * The library(mydoggy) itself may also cause problems, so have in mind rewriting some part of it or may be use another library. Since the library is tightly connected with skins (look and feel part of them). |
| | 34 | * Workspace areas (PageWorkArea, book desktop and document windows etc.) should be refactored. |
| | 35 | * Examine the hierarchy of classes. |
| | 36 | * Make it consistent with the "View" concept and the "BaseVisual" concept. Things there as slightle messed up and the desktop book is currently of no use. |
| | 37 | * Current things should be entirely in the Workspace (if there is something left in the model - remove it). |
| | 38 | * Remove old things that are no longer needed. |
| | 39 | * App, AppView for example. |
| | 40 | * All interaction should go through the LogicR3 using EventR3. (This is refactoring of the old Logics). |
| | 41 | * When refactoring the code, have in mind that we need to have a sinle-document-interface for the workarea (preview mode, presentation mode etc.). So when redesigning we should implement such functionality. |
| | 42 | * Along with the Workspace and Layout consider having two separate windows for Author and Reader (one having all flaps and desktop book and one without these). |
| | 43 | * Halos - things there seem to be alright for the time being. A refactoring has already been made (see [wiki:GROUP_BASE_HALOS_AND_FRAME_POSITION_R1] for more details, where the menus were refactored.) |
| | 44 | * Bound controls: |
| | 45 | * Have bugs: |
| | 46 | * Implementations of bound controls using JTextField have a bug connected with the listeners attached to the text field. |
| | 47 | * BoundCheckBox - a problem connected with Boolean.TRUE/Boolean.FALSE - does not update state properly with the pro lib. |
| | 48 | * Fix the layout of the components in the bound control. |
| | 49 | * Change the hierarchy so that the icon of the state can be dropped (controls should be able to chose whether with such an icon or without it). |
| | 50 | * Create new bound controls: |
| | 51 | * The "bound control" looking panel that most huds use for changing colors is not an actual bounds control. Create such a control: |
| | 52 | * The listener should be attached not to the whole panel, but rather to the color rectangle which may become a "ButtonBoundControl". |
| | 53 | * Introduce a "SliderBoundControl" that has a JSlider bound to some model. |
| | 54 | * Dialogs - they are more or less OK. Just review and improve things (optional). |
| | 55 | * Color Picker - the color picker is already a bound to the model. |
| | 56 | * There is a bug with the gradient dialog - clicking the color button breaks Sophie2. Fix it. Consider redesigning the gradient in a similar way to the color picker. Nevertheless the gradient changing component should be bound to the model as all controls in Sophie2 are. |
| | 57 | * Skins - the new skin Sophie2 should be integrated. Icons are ready. Use tool-tips from the default skin. |
| | 58 | * Icons - inconsistent icons of all skins should be fixed. This means that no icons should be used from the fall-back skin, since icons in skins differ a lot for different skins and sophie looks ugly with different icon styles. |
| | 59 | * Tool-tips - Tool-tips of the default skin a OK. Tool-tips of the alternative skin however should be fixed since not all components have an alternative skin tool-tip defined. |
| | 60 | * Component titles - Same as tool-tips. |
| | 61 | * Make all code connected with UI consistent with the new model and resources (this is something that depends on new resources and model). |
| | 62 | * Create diagrams of new designs if they appear to be complicated. |
