lumiera_

History

Ichthyostega fd0a011ea4 DiffMessage: bold attempt towards a way to produce diffs (#1066 ) actually I do not know much regarding the actual situation when, within the Builder run, we're able to detect a change and generate a diff description. However, as a first step, I'll pick IterSrouce as a base interface and use a "generation context", which is to be passed by shared-ptr		2017-08-11 00:59:10 +02:00
..
ctrl	CmdAccess: expand on the DSL draft	2017-04-14 03:22:08 +02:00
interact	CmdAccess: rename the front-end to CmdContext to clarify the purpose	2017-04-17 20:00:07 +02:00
test	CmdAccess: replace existing usages of InvocationTrail	2017-04-17 16:57:09 +02:00
abstract-tangible-test.cpp	DiffMessage: bold attempt towards a way to produce diffs (#1066 )	2017-08-11 00:59:10 +02:00
bus-term-test.cpp	CmdAccess: replace existing usages of InvocationTrail	2017-04-17 16:57:09 +02: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	Doxygen: magically insert a reference to the test class	2017-02-22 03:17:18 +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.