The below classes are just a basic guide to facilitating a proof of concept only, and do not necessarily reflect actual production.
Upon loading a saved layout, it will generate a blueprint of LayoutDataModel and LayoutVisualModel respectively.
and ….
Node ids are in the following format:
In the format of “Channel.n.n”, etc. To faciliitate in quick contextual lookups for possible binding. They are automatically generated by a saved layout, where n is a counter for the given Channel and consecutive level. 3rd “n” refers to a line node.
And for any new nodes being generated on the fly while editing:
In the format of “Channel.New.N”, where “N” is a unique id counter. “n” refers to a consecutive line node.
Tests is to be attempted across various slide layout schemes.
Typing in word-processor to update an example mock slide visuals only.
… create a duplicate of LayoutDataModel keep track of current edits being made to the existing content layout for the existing slide.
… create a new fresh instance of LayoutVisualModel to keep track of any slide visual changes that differ from the blueprint.