> Unlike other ingredients, the textdata attribute of the text class is
> subject to changes, especially when the text class is inherited in an
> entryField class.
>
> Consequently, this mechanisms of initial copy of the content into the
> textData attribute allows the modification of the octetString stored/shown
> by the text class (either by user interaction in an EntryField only or by
> setData action) even if the content attribute was initially referenced to
> an external file.
Emmanuel,
thanks for the hints. My local implementation problem with this
semantics
is that our engine is not concerned with resolution of references.
Instead,
this is done by the presentation layer on its own. So there was/is no
way
to initialize the textdata attribute in the engine at instanciation time
(since the is no associated presentation object).
I think I have to go for a kind of lazy evaluation requiriring to
presentation
layer to set the value of the textdata attribute later.
I regard that as a problem of our implementation, not of MHEG at this
point of
time.
So long,
- Klaus
-- GMD FOKUS German National Research Center for Information Technology Klaus Hofrichter Hardenbergplatz 2 D-10623 Berlin Germany mailto:hofrichter@fokus.gmd.de http://www.fokus.gmd.de/usr/hofrichter Tel +49 30 25499-211 Fax -202 There is a reexamination, but no reparty