Sylvain Wallez wrote:
Christoph Hermann wrote:
_Imho_ this is not really needed.
Sure we don't _need_ it. But I'm really surprised to see people not
being interested by an evolution that makes templates much more readable
and faster to type and update...
I'm interested :-)
Digging in all cforms stylesheets, I've seen only 2 stylings that
optionally use elements in their configuration: double-listbox (for the
list headers) and htmlarea (for a custom init script). All other
stylings use only attributes.
And it raises the problem with the "buggy" template, if the same
attribute name is used in widget and styling.
The buggy template is what can happen if we don't do anything against
it. It rather easy to enforce the use of either fi: attributes or
<fi:styling>.
Yes and a check that the style is either set by @fi:* or <fi:styling> and throw
a meaningful exception in the case that a user tries to go both ways there
shouldn't be any problems.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
