Ichthyostega
09e7e1f8f5
Actually I arried at the conclusion, that the *receiving* of a diff representation is actually a typical double-dispatch situation. This leads to the attempt to come up with a specialised visitor as standard pattern to handle and apply a diff. Obviously, we do not want the classical GoF-Visitor, but (yes, we had that discussion allready) -- well in terms of runtime cost, we have to deal with at least two indirections anyway; so now I'm exploring the idea to implement one of these indirections through a functor object, which at the same time acts as "Tag" in the diff representation language (instead of using an enum as tag)
30 lines
613 B
Text
30 lines
613 B
Text
TESTING "Component Test Suite: GUI Model Parts" ./test-suite --group=gui
|
|
|
|
|
|
|
|
TEST "Self-check: testing GUI backbone parts" TestGui_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
PLANNED "Concept demonstration: retrieve session contents" SessionStructureMapping_test <<END
|
|
return: 0
|
|
END
|
|
|
|
PLANNED "ModelClip_test" ModelClip_test <<END
|
|
END
|
|
|
|
PLANNED "ModelGroupTrack_test" ModelGroupTrack_test <<END
|
|
END
|
|
|
|
PLANNED "ModelParentTrack_test" ModelParentTrack_test <<END
|
|
END
|
|
|
|
PLANNED "ModelProject_test" ModelProject_test <<END
|
|
END
|
|
|
|
PLANNED "ModelSequence_test" ModelSequence_test <<END
|
|
END
|
|
|
|
PLANNED "ModelTrack_test" ModelTrack_test <<END
|
|
END
|