* A root component with @DesignRoot must always use its superclass for
default values. Otherwise the written design will be empty as the
design is read in the constructor.
* A component which is not the root must not write its component tree
if the component tree is generated in the constructor. This is a
simplification which should be good enough for most cases (can't add
children in constructor and also using addComponent - in this case
the component added with addComponent will not be written).
* Test cases for nested templates
Change-Id: I3a384d1d8654b9865a3a790ebeb055a300a62135
Support for automatic binding of the fields of the root layout (#7749)
The fields are bound to the components generated when parsing the design. The binding is done based on localId, id or caption.
Change-Id: I32ecac3cb76737c9d9d05a123db85fe65d55369c
The parser creates a Component hierarchy from a given html file. The
html generator does the converse, outputs html given a component
hierarchy with a single root.
Current TODOs: 1) add automatic tests - some of the functionality may
not have been tested in any way. 2) Remove files that are not relevant
for this change set but were accidentally included in a commit.
Change-Id: I222e01291aab75c2249d4aa4904f16fb153d4397