Ichthyostega
305ff8e6cc
basically this attempts to work around an "impedance mismatch" caused by relying on Lumiera's Diff framework. Applying a diff might alter the structural order of components, without those componets being aware of the change. If especially those components are attached into some UI layout, or otherwise delegate to display widgets, we need a dedicated mechanism to reestablish those display elements in proper order after applying the change. The typical examples is a sequence of sub-Tracks, which might have been reordert due to applying rules down in the Steam Layer. The resulting diff will propagate the new order of sub-Tracks up into the UI, yet now all of the elaborate layout and space allocation done in the presentation code needs to be adjusted or even recomputed to accomodate the change. |
||
|---|---|---|
| .. | ||
| ctrl | ||
| interact | ||
| model | ||
| test | ||
| abstract-tangible-test.cpp | ||
| bus-term-test.cpp | ||
| gen-node-location-query.hpp | ||
| README | ||
| session-structure-mapping-test.cpp | ||
| 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.