Furthermore, use of attributes ensures uniqueness of styling type, which is not guaranteed with nested elements.
E.g. what happens if we write : <wt:widget id="foo"> <wi:styling> <textarea rows="10"/> <password size="20"/> </wi:styling> </wt:widget>
Will this widget be rendered as a textarea or as a password ? With "textarea" or "password" being defined by the unique "type" attribute, this problem cannot happen.
Well, it will be up to the stylesheet to define what will happen. And since we can't control how people will make use of that stylesheet (edit it, or better: import it), I was thinking to just give them an isolated zone where they can add any styling info they want, which most likely will be copied verbatim to the output form. Your suggestion hints at having some definitive list of style widgets, something which I doubt will happen. Or we are in a mutual misunderstanding, of course. ;-)
Or do we want <wi:styling> to be able to hold different styling directives and let the layout stylesheet decide which one is best ? Mmmh... too much magic...
Definitely. People should be prepared to do some XSL hacking, but we shouldn't provide them with anything but a very basic stylesheet.
Cheers,
</Steven> -- Steven Noels http://outerthought.org/ Outerthought - Open Source Java & XML An Orixo Member Read my weblog at http://blogs.cocoondev.org/stevenn/ stevenn at outerthought.org stevenn at apache.org
