Mercurial > projects > mde
comparison codeDoc/todo.txt @ 74:cee261eba249
Minor tweaks.
| author | Diggory Hardy <diggory.hardy@gmail.com> |
|---|---|
| date | Mon, 07 Jul 2008 15:54:47 +0100 |
| parents | f54ae4fc2b2f |
| children | 25cb7420dc91 |
comparison
equal
deleted
inserted
replaced
| 73:08d3b6bcf891 | 74:cee261eba249 |
|---|---|
| 1 Copyright © 2007-2008 Diggory Hardy | 1 Copyright © 2007-2008 Diggory Hardy |
| 2 License: GNU General Public License version 2 or later (see COPYING) | 2 License: GNU General Public License version 2 or later (see COPYING) |
| 3 | 3 |
| 4 | 4 |
| 5 * means done | 5 * means done: |
| 6 | 6 |
| 7 GUI: | 7 GUI: |
| 8 -> Widgets: | 8 -> Widgets: |
| 9 -> rethink how widgets are created and receive creation data, so that they don't have to be created by the Window | 9 -> rethink how widgets are created and receive creation data, so that they don't have to be created by the Window |
| 10 ->* minimum size but expandable, auto-set | 10 ->* minimum size but expandable, auto-set |
| 12 -> scripted widgets | 12 -> scripted widgets |
| 13 -> decent rendering/theme system | 13 -> decent rendering/theme system |
| 14 -> lists from content lists | 14 -> lists from content lists |
| 15 -> Content: | 15 -> Content: |
| 16 -> lists | 16 -> lists |
| 17 | |
| 18 | |
| 19 + shows current preference: | |
| 20 | |
| 21 Redesign: | |
| 22 -> requirements | |
| 23 -> widgets can receive int and string data types | |
| 24 -> possibilities | |
| 25 -> per-widget merging (i.e. separate tag(s) for each widget's data)? | |
| 26 -> if a widget with sub-widgets is defined in a base file, but redesigned in a derived file, any unused widgets with data resolting are not created | |
| 27 -> if design changes in a base file, while the old design was modified in a derived file, will the result be sane? | |
| 28 -> if a locally modified gui is updated upstream (so the base files change), should: | |
| 29 -> the local modifications persist? | |
| 30 -> the local modifications be lost? | |
| 31 -> the widgets be merged? | |
| 32 -> potentially gives the best of both worlds | |
| 33 -> should original widgets used as sub-widgets of modified widgets: | |
| 34 -> use original data (from base file), so they can be updated? | |
| 35 -> have data copied, also impacting unmodified portions of window using same widget? | |
| 36 -> have data copied under a new ID? | |
| 37 -> the user be asked? | |
| 38 -> requires copy of old data... | |
| 39 +> widget data per-gui instead of per-window? | |
| 40 -> identical sub-widget could be used in multiple windows more easily, when data file is hand edited | |
| 41 -> in-gui editor will probably copy data under a new ID anyway | |
| 42 +> Maybe change to: | |
| 43 -> One section per version, containing widget data | |
| 44 -> can inherit from other sections | |
| 45 -> Which section (version of gui design) to use saved in header | |
| 46 -> Either/or: | |
| 47 -> Windows defined in header by primary widget | |
| 48 +> Windows become ordinary sub-widgets or some parent widget, gui becomes a parent widget | |
| 49 +> widget data no longer has "construction" and "mutable" variations | |
| 50 +> widgets know their IDs and update their data whenever necessary, via the gui, into a new data set, which is saved upon exit |