a91d6a3bae
implement and cover the zombie network
2015-12-26 22:56:43 +01:00
d7191959cf
fix a zombie segementation fault
...
hey, it's still X-mas...
2015-12-26 21:53:46 +01:00
8cd31443b1
invent a suicidal zombie terminal
...
yeah, it's X-mas time,
letz build a diagnostic network of deceased widgets...
2015-12-26 20:41:24 +01:00
f23b482d7d
adjust test code to get MockElm log joining to PASS
...
the "log joining" functionality was already implemented
and covered with the generic event log facility, but this test
here was drafted even before that, meaning that the semantics
of matchingn on the log, especially on events, as been
implemented slightly different than planned
2015-12-26 04:55:00 +01:00
b9ef66b221
provide and cover a mock implementation of receiving notification messages
2015-12-26 04:40:38 +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
4d1fcd6dcb
implement logging/identification of mock UI elements
2015-12-25 00:41:14 +01:00
37802fd699
complete wiring of nexus and core services
...
since, by definition, the Nexus is "the" up-link,
all we need is clever overriding of the relevant
handling functions, so the nexus will care for the routing,
while the CoreService cares for command and presentation
state handling
2015-12-19 04:05:21 +01:00
0f793e0a79
untangle the setup of test nexus
2015-12-18 19:50:57 +01:00
d673d1ed1c
better naming of the test facility
...
I think it is a shame to waste the nice name "nexus"
just for a test facility; rather I've named our central
routing hub in the UI-Bus gui::ctrl::Nexus
So it makes sense to name the fake for unit testing
the test-nexus (we're not at nexus 5 yet)
2015-12-18 19:50:57 +01:00
f19ebd63d0
pondering about how to connect the central bus hub
...
...especially since we need a faked UI backbone for unit testing
2015-12-18 19:50:02 +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
59c2d2b482
WIP: start implementing the generic UI base
2015-12-16 23:24:11 +01:00
bf92333339
implement log joining in shared heap storage
2015-12-09 01:18:15 +01:00
272d62d5a3
log handling const correctness
...
adding log entries requires full access,
whereas matching log entries is const,
since it doesn't alter the log
2015-12-06 04:37:41 +01:00
ef1b640ffb
adapt API to the workings of log joining (as defined/planned)
...
indeed I flipped the meaning, with respect to the previous plan.
It seems more natural to "join this into another log"
2015-12-06 04:30:39 +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
9af20b7cf6
WIP: BusTerm needs to be a concrete class
...
...providing the standard implementation of UI-Bus connectivity.
It seems reasonable to place all of the UI-Bus implementation into
a single translation unit
2015-11-28 20:55:28 +01:00
1eda2a070b
harmonise the form of the header include guards
...
no trailing underscore
2015-11-28 18:36:35 +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
