WIP some notes what could be addressed next

This commit is contained in:
Fischlurch 2016-02-09 02:17:59 +01:00
parent 44785859ea
commit fea6628b3c
2 changed files with 11 additions and 1 deletions

View file

@ -59,7 +59,7 @@
** like a common styling. These are addressed the conventional way, through a common \ref WindowManager.
** The following discussion focuses on the aspects of integration with the core.
**
** For one reason ore another, any element in the UI can appear and go away.
** For one reason or another, any element in the UI can appear and go away.
** This lifecycle behaviour corresponds to attachment and deregistration at the UI-Bus
**
** In regular, operative state, an interface element may initiate _actions_, which translate

View file

@ -367,6 +367,14 @@ namespace test {
markState ()
{
UNIMPLEMENTED ("mark interface state");
// verify both directions of state marking
// expand and collapse the mock
// and verify that the corresponding state marks appear at the bus
// then replay those state marks
// at least the doMark should be invoked
// TODO maybe we'll even provide a default implementation for expand/collapse
// which then means that, by replaying the mentioned state marks, the
// doExpand() or doCollapse should be re-invoked
TODO ("be sure also to cover signal diagnostics here");
}
@ -376,6 +384,8 @@ namespace test {
notify ()
{
UNIMPLEMENTED ("receive various kinds of notifications");
// send msg, error and flash messages via Bus to the element
// verify the doMsg, doErr or doFlash get invoked
}