On Tuesday 18 October 2005 03:26, Dominik Huber wrote:
... the current viewlet implementation lacks of this pattern, because it
use different adaptions for content providers and viewlets. Looking from
this composite subview perspective, the view and manager parameters of
viewlets brings some
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
On Oct 15, 2005, at 9:52 PM, Roger Ineichen wrote:
[...]
The content provider package offers just the API for collecting
additional content. This pattern can be used directly in python
or in page templates.
There is no reason that we have to use a viewlet implementation for
this. The content
On Sunday 16 October 2005 09:01, Gary Poster wrote:
Let's say the content provider package offers the concept and the
viewlet package offers a implementation which depends on page
templates.
OK, that makes sense. The contentprovider package offers up two
bits, then: the pattern of
Hello everyone,
I am pleased to announce that we are finally at a stage with the development
of content providers and viewlets to ask for feedback from the rest of the
community. The code, purposefully leaned on the ideas from the Java world,
was originally written by Roger and I rewrote it a
On Oct 15, 2005, at 8:24 AM, Stephan Richter wrote:
...
What are we looking for?
- Comments on the Python API.
- Comments on the ZCML API.
- Comments on the ZPT API.
- Use cases that you might think are not covered by the design and
implementation.
- Whatever you like to say about it...
Hi
10 matches
Mail list logo
