LUMIERA.clone

History

Ichthyostega de71baccc3 use a inline command handler to actually invoke. Unit test PASS Wow! This innocuous little commit integrates several subsystems for the first time And all worked right away!		2016-01-12 02:59:16 +01:00
..
test	mass clean-up: adapt usage of std::cout pretty much everywhere	2016-01-07 20:12:46 +01:00
abstract-tangible-test.cpp	use a inline command handler to actually invoke. Unit test PASS	2016-01-12 02:59:16 +01:00
bus-term-test.cpp	mass clean-up: adapt usage of std::cout pretty much everywhere	2016-01-07 20:12:46 +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.