lumiera_

History

Ichthyostega 0837498cc0 Relative-Hook: proof-of-concept based on ViewHook (see #1207 ) this draft commit reshifts the (meanwhile broken) test code from: `03c358fe86` Now the marker Buttons are injected again, but without any detailed positioning code at call site. This demonstrates the viability of the Structure-Change / ViewHook refactoring. To make this change viable, it was necessary to remove the ViewHooked<> marker template from the rehook() callback. As it turns out, this was added rather for logical reasons, and is in fact not necessary in any of the existing ViewHook implementations (and I don't expect any other implementations to come) BUT the actual positioning coordinates are still wrong (which seems to re related to other conceptual problems in coordinate offset handling)		2020-02-27 21:03:46 +01:00
..
ctrl	Global-Layer-Renaming: fix remaining textual usages and IDs in the code	2018-12-10 00:09:56 +01:00
interact	Global-Layer-Renaming: fix remaining textual usages and IDs in the code	2018-12-10 00:09:56 +01:00
model	Relative-Hook: proof-of-concept based on ViewHook (see #1207 )	2020-02-27 21:03:46 +01:00
test	Library: complete test coverage of VerbPack	2019-06-11 02:40:20 +02:00
abstract-tangible-test.cpp	Global-Layer-Renaming: fix remaining textual usages and IDs in the code	2018-12-10 00:09:56 +01:00
bus-term-test.cpp	Global-Layer-Renaming: fix remaining textual usages and IDs in the code	2018-12-10 00:09:56 +01:00
gen-node-location-query.hpp	Global-Layer-Renaming: adjust namespace qualification	2018-11-15 23:59:23 +01:00
README	Global-Layer-Renaming: rearrange directories	2018-11-15 23:28:03 +01:00
session-structure-mapping-test.cpp	Global-Layer-Renaming: fix remaining textual usages and IDs in the code	2018-12-10 00:09:56 +01:00
test-gui-test.cpp	Global-Layer-Renaming: fix remaining textual usages and IDs in the code	2018-12-10 00:09:56 +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.