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
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
Hi :)
I'm a total newbie to Zope3 (and Zope in general) and I would like to
learn it...
Unfortunatelly I can't find any good documentation to start with (it
could be that I'm a very bad researcher)...
Most of the Zope3 documentation on zope.org is about developing the
framework and not
On Jan 1, 2006, at 4:30 PM, Maciej Zięba wrote:
Is there a ZopeBook or something similiar for Zope 3? Zope3Book is
about development of the framework.
Could you please recommend some place I could start learning it
(articles, tutorials, etc.)?
Here is the zope 3 book at zope.org:
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 view)
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
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.
Views as a separate concept have already been gone since Zope 3.1. It
was only Zope X3 3.0 that had them as separate components in a separate
