| 3 | | |
|---|
| 4 | | |
|---|
| 5 | | Content: |
|---|
| 6 | | Need a way for a single content to contain multiple "sub-contents", and a way for widgets to be bound to a sub-content. |
|---|
| 7 | | -> how |
|---|
| 8 | | -> Use indecies; widget's use an integer value to choose index (or a string)? |
|---|
| 9 | | -> Protection: read-only and read-write contents? |
|---|
| 10 | | -> why |
|---|
| 11 | | -> Dynamic lists of name, value and possibly description fields. |
|---|
| 12 | | -> Done in a basic case, so is it needed? |
|---|
| 13 | | Generic Content creation: |
|---|
| 14 | | -> Created centrally, e.g. from options or translation strings. |
|---|
| 15 | | -> Creator keeps a hash-map of all created content, so that if the same content is asked for again the same content object will be returned, not a new object (besides efficiency, this keeps content synchronized). |
|---|
| 16 | | -> Generic ContentList type for instancing on at run-time. |
|---|
| 17 | | -> Items in ContentList may represent a cluster of items; e.g. an option plus it's name and description. These may be special classes, but should use a generic interface allowing getting sub-contents (e.g. value/name/desc.) via an index. |
|---|
