Ichthyostega 723d1e0164 settle architectural considerations regarding the TreeMuator concept ... so yes, it is complicated, and inevitably involves three layers of indirection. The alternative seems to bind the GUI direcly to the Session interface -- is there a middle gound? For the messages from GUI to Proc, we have our commands, based on PlacementRef entities. But for feeding model updates to the GUI, whatever I consider, I end up either with diff messages or an synchronised access to Session attributes, which ties the responsiveness of the GUI to the Builder operation.		2015-04-03 20:10:22 +02:00
..
diff-index-table-test.cpp	allow for iterative access to the snapshot data in the lookup table	2015-01-04 14:23:12 +01:00
diff-list-application-test.cpp	settle architectural considerations regarding the TreeMuator concept	2015-04-03 20:10:22 +02:00
diff-list-generation-test.cpp	Implementation of List Diff detection finished. Unit Test PASS	2015-01-04 15:13:16 +01:00
gen-node-basic-test.cpp	decide on the foundations of tree diff representation	2015-03-21 02:00:55 +01:00
generic-record-representation-test.cpp	decide on the foundations of tree diff representation	2015-03-21 02:00:55 +01:00
generic-tree-mutator-test.cpp	initial syntax draft	2015-04-02 03:30:20 +02:00
generic-tree-representation-test.cpp	decide on the foundations of tree diff representation	2015-03-21 02:00:55 +01:00