Tim Peters wrote:
The bad news is that Martin is an extremely capable PhD who worked on
this across months; i.e., this was a major undertaking. The good news
is that large parts of it are probably easily reusable -- by Martin
;-)
Can we tempt him with beer to build a purdie one for Zope too?
Hi Stephan,
I just looked at the examples. I like the current implementation much
more, because a viewlet is adapted to its original context (- complex
example) and content providers (or viewlet managers) can render itself.
Those changes are providing a better encapsulation and a more ca-like
On Oct 17, 2005, at 11:23 AM, Dominik Huber wrote:
...
IMO it is very important to provide a standardized way to handle
complex, formbased views properly (- prefix like nested widgets)
Agreed. FWIW, this is another part of the subview package. I tried
to spell this out very explicitly.
On Saturday 15 October 2005 15:48, Gary Poster wrote:
viewlets look like a clever pattern. I can see that they can be
applied to many use cases; I'll have to think about them to see how
much I like the application compared to others we have used, but I
have a generally favorable impression so
On Saturday 15 October 2005 15:48, Gary Poster wrote:
The rough README is here: http://svn.zope.org/Zope3/branches/
f12gsprint-widget/src/zope/subview/README.txt?view=auto . The whole
package is rough; I had to put work on this aside, but it it is
currently slated to be my next project,
On Oct 17, 2005, at 12:08 PM, Stephan Richter wrote:
On Saturday 15 October 2005 15:48, Gary Poster wrote:
I also really wish we could agree on a subview-addressing story (for
AJAX) and a drag-and-drop story. We have experience with our drag
and drop story, and are proposing a new AJAX
Thank you Fred. Read the Friendly Zope3 Site, ha!
Your response does beg the question though - of the packages on the
branch *not* included in the Z3.1.0 release, which are considered to
be optional-good and optional-not-ready-for-prime-time?
I have read that SchoolTool/Schoolbell needed
