[z3-five] porting Five to Zope 3.1+

[Martijn Faassen]

Martijn Faassen wrote:
> Martijn Faassen wrote:

> I ran into a few more for browser:page:
> 
> * the ZPublisher in Zope 2 needs a docstring on whatever it publishes or 
> it will refuse to do so. Five currently hacks this in inside the ZCML 
> directive.
> 
> * Five applies its own security to the newly created class. We don't 
> have access to the newly created class outside of the ZCML directive...

Tres solved this last one: we get the newly created class from the ZCML 
_context.actions.

Now I'm entering a big hairball of issues to do with the 
"SimpleViewClass" code in Zope 3. The original browser:page directive 
uses SimpleViewClass as defined in Zope 3, but this builds on top of the 
Zope 3 page template engine and also constructs something that is a Zope 
3 native view class (with browserDefault, publishTraverse, etc).

Thinking aloud:

At the cost of some expense we could change the 'index' attribute of 
this thing to use a Five-based page template.

This leaves the problem of mixing in ZPublisher specific attributes to 
the view class that the Zope 3 generated one doesn't have. Perhaps 
monkey patching is the way to go there too.

Regards,

Martijn