[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Template of describing a component
When we specify a component - the logical puzzle piece of the
document from a user perspective - there are repeating sets of
information to be given:
In our high-level auxiliary model a component consists of one or
more XML nodes. The state of a component is given by its
properties, which are in general being mapped to XML attributes. We should keep in mind, that the component model allows us to
abstract from the design decision of the ODF XML model. For example, although ODF XML differentiate between a paragraph,
a heading and a list item, all three of them are based on a
paragraph. Therefore the change/transformation of a paragraph to a heading
or movement of a paragraph into a a list-item, can be simply
archived by property changes on the paragraph component, not by
complex delete/insert operation of different foreign components. Looking forward to discuss this tomorrow, |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]