Re: Overriding work around

On Wednesday 23 March 2005 09:09, Jan-Wijbrand Kolman wrote:
> Andrew C. Altepeter wrote:
> >>>AFAIK, this behaviour has been there forever
> >>
> >>By which I don't mean to say we shouldn't change it!
> >>
> >>I just didn't regard it as a bug, since it was the intended behaviour all
> >> a long. We now might have other requirements of course.
> >
> > I don't necessarily think it's a bug either, but in our environment we
> > have always changed changed the acquisition behavior, removing the
> > '.aq_explicit'.
>
> How's the behaviour of 'override.html' different from 'content.html' if you
> remove the explicit acquisistion?
>
> Content.html was meant to set the rendering of content for a complete
> subtree, where the override.html was meant to set the rendering for the
> context it is in only.

Good question.  I probably never completely understood content.html's purpose.  
I should have mentioned that I wrote an extension to silva, which adds a 
'template' tab to folders and publications.  Our environment has many various 
sites, all of which use one of two templates, and minimal customization.  In 
the ZMI, you define the template, it's cusomizable preferences, and in Silva, 
you select which template and edit the prefs for your site.

When I developed this (I think around Silva 0.9) I felt that using 
override.html, along with removing the 'aq_explicit' restriction, completely 
fit our needs.

I think I used override instead of content because content uses metal...and at 
the time I wasn't, and didn't understand metal (I do now, at least kinda ;-)

Currently, each area of silva (each 'site') has an override.html file.  This 
override file uses a site-override-macro.html file, located at the Silva 
root.  This macro retrieves the template specified for the site, and inserts 
the right stuff in the right places.  Now that I think about it, it sounds 
very much like your content.html and layout_macro.html combo...huh!

Cheers,
Andy
>
>
>
> regards,
> jw