LUMIERA.clone/tests/gui
Ichthyostega 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
..
test complete wiring of nexus and core services 2015-12-19 04:05:21 +01:00
abstract-tangible-test.cpp consider the bus side of the generic UI base in more detail 2015-12-18 01:02:19 +01:00
bus-term-test.cpp test driven planning 2015-11-26 22:23:43 +01:00
README
session-structure-mapping-test.cpp extended planning to define the operation of UI-Bus and model update 2015-01-17 16:08:56 +01:00
tangible-update-test.cpp extended planning to define the operation of UI-Bus and model update 2015-01-17 16:08:56 +01:00
test-gui-test.cpp

GUI backbone tests

The tests in this subtree are a bit special: they cover the generic and
backbone internals of the Lumiera GTK GUI. They are linked against the
complete GUI-module (gui plugin), and thus may use all related ABIs.

Yet these tests are *deliberately* compiled without any GTK, GTKmm or SigC
includes. This effectively rules out the use, even indirectly, of any GTK
widgets and APIs -- forcing the covered GUI backbone entities to stay
clean and generic at API level.

This is a decision done on purpose. The concrete GUI framework technology
shall be treated as an implementation detail. There is no point in writing
tests which click buttons in the GUI -- better delegate any significant
logic or functionality to GUI agnostic components. GUI is meant to be
a presentation layer and must not develop intelligence on its own.