Jim Fulton wrote:
Martijn Faassen wrote:
While the browser:page directive can take a content class for its
'for' attribute (instead of an interface), the browser:defaultView
directive doesn't accept this. I tried changing the interface of the
defaultView directive so it also accepts classes, but that by itself
does not appear to make it work. This somewhat limits the utility of
the ability to pass in classes instead of interfaces to the page
directive; the point is to have a shortcut so an interface doesn't
always need to be defined.
Before I dig deeper, I'd first like to know whether this would indeed
be considered to be bug? If so, should I check this into trunk or also
the Zope 3.1?
The intent was to deprecate the use of the defaultView directive to
specify anything but the default view name. This decision was made
before we had a deprecation mechanism.
The recommended way to create a default view is to create a view named
"index.html", which can be done with the page directive.
Aaah, I didn't realize that. I'll just use that then.
Thanks,
Martijn
_______________________________________________
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
