LUMIERA.clone

History

Ichthyostega b5b62f101f WIP: draft a message broadcasting function not really sure about its usefullness, but it seems low hanging fruit for me right now (while I am still aware of all details how the UI-Bus works). This might possibly be helpful to broadcast "reset" messages....		2016-02-14 01:47:21 +01:00
..
interact	state manager storage implemented and covered by unit test	2016-02-13 22:55:59 +01:00
test	test to cover call sequence of message dispatch in UI-Bus	2016-02-14 01:34:58 +01:00
abstract-tangible-test.cpp	cover additional message/error diagnostics in MockElm	2016-02-14 00:23:24 +01:00
bus-term-test.cpp	WIP: draft a message broadcasting function	2016-02-14 01:47:21 +01:00
README	enable special unit-tests to link against the gui	2014-10-18 04:27:07 +02:00
session-structure-mapping-test.cpp	mass clean-up: adapt usage of std::cout pretty much everywhere	2016-01-07 20:12:46 +01:00
tangible-update-test.cpp	mass clean-up: adapt usage of std::cout pretty much everywhere	2016-01-07 20:12:46 +01:00
test-gui-test.cpp	mass clean-up: adapt usage of std::cout pretty much everywhere	2016-01-07 20:12:46 +01:00

README

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.