So Melchior found what is either a bug or a feature. Here's the
background. I broke my model animation code into several separate xml
files that were serially included as a chain. In the last file I noticed
that the first 78 animations were being ignored (actually overwritten by
it's parent
* Josh Babcock -- Monday 04 December 2006 14:35:
PropertyList
merge
filenamefoo.xml/filename
/merge
!-- followed by any number of additional merge or append elements --
/PropertyList
In this case a simple
mergefoo.xml/merge
would do. But introducing a global keyword that is
* Melchior FRANZ -- Monday 04 December 2006 15:10:
* Josh Babcock -- Monday 04 December 2006 14:35:
PropertyList include=foo include=bar
The question here is: is this valid XML?
Apparently not:
$ xmllint foo.xml
foo.xml:3: parser error : Attribute foo redefined
PropertyList foo=123
Melchior FRANZ wrote:
* Melchior FRANZ -- Monday 04 December 2006 15:10:
* Josh Babcock -- Monday 04 December 2006 14:35:
PropertyList include=foo include=bar
The question here is: is this valid XML?
Apparently not:
$ xmllint foo.xml
foo.xml:3: parser error : Attribute foo redefined
* Josh Babcock -- Monday 04 December 2006 15:27:
Melchior FRANZ wrote:
* Melchior FRANZ -- Monday 04 December 2006 15:10:
* Josh Babcock -- Monday 04 December 2006 14:35:
PropertyList include=foo include=bar
Right, I guess I wasn't clear.
You *were* clear. But wrong. :-}
And here
Melchior FRANZ wrote:
Also keep in mind that the xml parser will not accept the following
PropertyList include=foo include=bar
The question here is: is this valid XML?
No it's not valid. In such cases space delimited lists are usually used:
PropertyList include=foo bar
Nine
Quoting Melchior FRANZ :
But we *do* already have a way to include files anywhere in the XML
file. But the contents aren't *inserted* there, but put under a node:
foo include=bar.xml/
This adds the contents of bar.xml under the node foo/. One could
now declare one property name 'void',
* Stefan Seifert -- Monday 04 December 2006 15:47:
Zope Page Templates for example have an attribute for cases where the
tag should be omitted, like:
foo include=bar.xml omit-tag=yes/
Yes, that's probably the cleanest solution. (Using y instead of or
in addition to yes, to be consistent with
* Melchior FRANZ -- Monday 04 December 2006 15:53:
* Stefan Seifert -- Monday 04 December 2006 15:47:
foo include=bar.xml omit-tag=yes/
Yes, that's probably the cleanest solution. (Using y instead of or
in addition to yes, to be consistent with other attribute values.)
My current favorite
Melchior FRANZ wrote:
Does anyone have objections to the whole idea? Or not understand
what it's good for? Or better suggestions for omit-node?
m.
This seems like a very good solution from a model builder's point of view.
Josh
10 matches
Mail list logo
