>
> > [snip]
> > I would prefer to see the html attributes always override the xml
> > definitions.
> I say that because it favors the web designer
> > instead of the developer.
> > However, this new proposed attribute (allowOverriding="false") would give
> > the
> developer the final decision.
>
> The same as with my solution. The developer provides a value or not.
This is a bit off tangent to this discussion but I thought it would be worth
bringing up in the context of creating solutions that promote reuse.
We have a half baked CMS where I work. It provides a way to apply
customizations/overrides to a hierarchy horizontally verses the traditional
vertical OO approach. This works very well for customizing sites for various
customers because all pages include the same component. The customizations
("generalization relationships") are applied to a hierarchical structure verses
a new hierarchy created for each new component.
This is also something we might consider for Clay. Since the jsfid's are not a
dynamic attribute, it makes it hard to introduce customizations without
creating a new page that references another component. It might be interesting
to think about applying "overrides" to an existing tree.
I see the HTML override to the XML as a similar concept.
>
> > I think we should make the default value "true". The developer could also
> choose to make "false" the default value using
> > some inheritance.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
> _________________________________________________________________________
> Mit der Gruppen-SMS von WEB.DE FreeMail können Sie eine SMS an alle
> Freunde gleichzeitig schicken: http://freemail.web.de/features/?mc=021179
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
