dddcbe9994
DOC: supply basics of UI-Bus and generic UI-element protocol
...
the initial draft of this concept is in place now, and
the first round of unit tests pass. I've got some understanding
of the purpose of the interactions and involved elements
and I'm confident this design is evolving in a sane way.
Note: extensive documentation is in the TiddlyWiki,
here I've just pasted and reworded some paragraphs from there
and integrated them into the Doxygen docs
2015-12-27 01:58:15 +01:00
9aa1fec369
UI-Element protocol: clarify the role of the doExpand() extension point
...
and let the concrete extension point decide if the corresponding
state change was actually relevant and should be persisted
2015-12-26 00:59:16 +01:00
3a287bf134
implement the generic expand/collapse mechanism
2015-12-25 03:53:26 +01:00
af98d75da4
consider the bus side of the generic UI base in more detail
...
especially define the outline of the bus communication
and connection management
2015-12-18 01:02:19 +01:00
b2542b86f7
stub and rectify interfaces defined thus far.
...
...compilation PASS again
2015-11-28 23:50:56 +01:00
d4c017fa73
WIP: settle on the Tangible interface
2015-11-28 21:43:09 +01:00
2704ad4512
decide upon the actual mechanics of command binding and invocation
2015-11-28 08:15:32 +01:00
7b16c6b130
fundamental concerns regarding command binding
...
prompted by first attempt to define the Tangible interface...
ZOMG! And I thought I might be able just to code-up that stuff
2015-11-28 01:20:40 +01:00
d04e6d74d8
WIP: arrange some elements needed for MockElm implementation
2015-11-27 19:24:00 +01:00
