[
Lists Home |
Date Index |
Thread Index
]
- From: "Bent Rasmussen" <runnable@hotmail.com>
- To: xml-dev@ic.ac.uk
- Date: Wed, 08 Dec 1999 18:20:21 CET
>Thoughts?
yes - one
> Layer *layer = new Layer((*it).GetAttribute("name"));
> layer->Parse(*it);
> doc->AddLayer(layer);
Why do you call a parse method outside of Layer? The parse method might be
there but it seems to me that giving the constructor the whole DOM node will
reduce complexity and since it is implied that the object should use the
information during construction to build its internal state - it might as
well just start off by parsing the node during the actual construction. If
you had a method that returned the object state (fx a wrapper object with a
DOM node containing state information) you could then easily throw in a
history mechanism for your program (by letting the document object holding
the shapes catch and reset states of objects in a sequential manner).
I'm rookie (only know about Java) but I think it makes sense, and hope it
does since I intend redesigning my own java-based drawing application this
way; using XML for serialization syntax and feeding/outputting it directly
to/from the objects using it.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo@ic.ac.uk the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)
|
