On Sunday 01 January 2006 12:20, Wade Leftwich wrote:
> Since Zope 3 is all about being self-documenting and discoverable, it
> seems odd that something as central as a View has the "implicit"
> attributes 'context' and 'request'. Is there an architectural reason
> that we don't say that a View cla
Jeff Shell wrote:
> [snip]
>
> But if you're looking for a base interface and class:
>
> interface:
> zope.app.publisher.interfaces.IBrowserView
>
> class:
> zope.app.publisher.BrowserView - has the __init__ with context and
> request, and is also locatable (mapping __parent__ to the context).
>
> Thanks Chris, that actually does make things clearer. As a Z3 beginner,
> longtime Z2 user (ZPTs, scripts, ZSQL), and corporate developer who is
> trying to promote Z3 in-house, I am all for the current trend toward
> simplification, especially of ZCML
> (http://www.z3lab.org/sections/blogs/phil
Chris McDonough wrote:
> It will probably not comfort you that the concept of a "view" (at least
> by that name) is going to disappear sometime post-3.2.
>
> I hope I explain this properly; here goes.
>
> A view is a registration for a "named multiadapter". The thing that is
> registered ("the
It will probably not comfort you that the concept of a "view" (at
least by that name) is going to disappear sometime post-3.2.
I hope I explain this properly; here goes.
A view is a registration for a "named multiadapter". The thing that
is registered ("the view") adapts two objects that im
Since Zope 3 is all about being self-documenting and discoverable, it
seems odd that something as central as a View has the "implicit"
attributes 'context' and 'request'. Is there an architectural reason
that we don't say that a View class implements an IView interface that
gives the names of the e
