Mercurial > projects > mde
comparison codeDoc/todo.txt @ 90:b525ff28774b
Widgets generated dynamically from a list can now be standard widgets selected from data files.
Started on allowing alignment to be shared between instances of a layout widget in a dynamic list (to allow column alignment of list's rows).
| author | Diggory Hardy <diggory.hardy@gmail.com> |
|---|---|
| date | Wed, 01 Oct 2008 23:37:51 +0100 |
| parents | 25cb7420dc91 |
| children | 4d5d53e4f881 |
comparison
equal
deleted
inserted
replaced
| 89:97e6dce08037 | 90:b525ff28774b |
|---|---|
| 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 GUI: | 5 GUI: |
| 6 -> Widgets: | 6 -> Widgets: |
| 7 -> rethink how widgets are created and receive creation data, so that they don't have to be created by the Window | 7 -> rethink how widgets are created and receive creation data, so that they don't have to be created by the Window |
| 8 -> scripted widgets | 8 -> scripted widgets |
| 9 -> decent rendering/theme system | 9 -> decent rendering/theme system |
| 10 -> lists from content lists | 10 -> lists from content lists |
| 11 -> Content: | |
| 12 -> lists | |
| 13 | 11 |
| 14 | 12 |
| 15 + shows current preference: | 13 Scratchpad area for ideas: |
| 14 | |
| 16 | 15 |
| 17 Redesign: | 16 Redesign: |
| 18 -> requirements | |
| 19 -> widgets can receive int and string data types | |
| 20 -> possibilities | 17 -> possibilities |
| 21 -> per-widget merging (i.e. separate tag(s) for each widget's data)? | 18 -> How widgets get their sub-widgets: |
| 22 -> if a widget with sub-widgets is defined in a base file, but redesigned in a derived file, any unused widgets with data resulting are not created | 19 -> (current) Ask manager to create widget from manager's data with ID from widget's data. |
| 23 -> if design changes in a base file, while the old design was modified in a derived file, will the result be sane? | 20 -> seems to work well; allows widgets some control over creation of children |
| 24 -> if a locally modified gui is updated upstream (so the base files change), should: | 21 -> now extended to support instancing & passing content; seems to fulfill requirements |
| 25 -> the local modifications persist? | 22 -> (alternate) Pass widget a list of pointers to all sub-widgets |
| 26 -> the local modifications be lost? | 23 -> manager creates all static (from data files) widets |
| 27 -> the widgets be merged? | 24 -> other widgets can create dynamic widgets as or to pass to sub-widgets |
| 28 -> potentially gives the best of both worlds | 25 -> widget data needs a portion which is explicitly IDs for subwidgets, or data needs reforming into a tree |
| 29 -> should original widgets used as sub-widgets of modified widgets: | |
| 30 -> use original data (from base file), so they can be updated? | |
| 31 -> have data copied, also impacting unmodified portions of window using same widget? | |
| 32 -> have data copied under a new ID? | |
| 33 -> the user be asked? | |
| 34 -> requires copy of old data... | |
| 35 +> widget data per-gui instead of per-window? | |
| 36 -> identical sub-widget could be used in multiple windows more easily, when data file is hand edited | |
| 37 -> in-gui editor will probably copy data under a new ID anyway | |
| 38 +> Maybe change to: | |
| 39 -> One section per version, containing widget data | |
| 40 -> can inherit from other sections | |
| 41 -> Which section (version of gui design) to use saved in header | |
| 42 -> Either/or: | |
| 43 -> Windows defined in header by primary widget | |
| 44 +> Windows become ordinary sub-widgets or some parent widget, gui becomes a parent widget | |
| 45 +> widget data no longer has "construction" and "mutable" variations | |
| 46 +> widgets know their IDs and update their data whenever necessary, via the gui, into a new data set, which is saved upon exit |