Andreas Hartmann wrote:
Jörn Nettingsmeier schrieb:
i'm thinking of committing the attached patch, which will make
<resources/> and <modules/> optional, but forces them to have at least
one resource or module element inside.
andreas, since you changed that code: is there a particular reason for
the current behaviour, i.e. mandate the wrappers and make the content
elements optional? i find it a little counter-intuitive...
The wrappers were already mandatory, I just had to make the content
elements optional because child publications might have no modules
or resource types. I considered to change this like you proposed above,
but I think this would require to change the Instantiator. But when
I gave it more thought, I came to the conclusion that mandatory
wrappers aren't so bad because they serve as a scaffolding for the
file structure, and thus the files are more similar to each other.
i see your point. but given that most other elements are optional (and
thus do not provide much of a scaffold), i'd prefer these to be optional
as well, for consistency. i'm not sure about the instantiator - iirc it
should handle non-existing resource-types and modules elements just
fine, but i'll need to look. will do tonight.
--
jörn nettingsmeier
home://germany/45128 essen/lortzingstr. 11/
http://spunk.dnsalias.org
phone://+49/201/491621
Kurt is up in Heaven now.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
