> > IMO it would be great to solve this properly, because one point of
> > using views is to have a fine control over what to publish
> and what not.
> > And this is a bit broken at this point, currently.
> Right, that's why page templates that just provide macros
> should be registered unpublishable browser views and not
> browser pages.
> You see how far into the confusion the <browser:page />
> directive has brought us?
but this is only a problem how we lookup views/pages
via /@@ in templates. The implementation of a *provider*
tales expression for viewlet manager totaly avoids this :-)
> Zope3-dev mailing list
Zope3-dev mailing list