Re: [Zope3-dev] RFC: Content Providers and Viewlets

2005-10-18 Thread Dominik Huber
Gary Poster wrote: ... and to sketch the difference between widgets and viewlets out. The zope.widget package in the branch is currently in disrepair, but the intent is for widgets to be subviews. The subview package actually grew out of the widget work. This won't be ready for 3.2.

Re: [Zope3-dev] RFC: Content Providers and Viewlets

2005-10-18 Thread Stephan Richter
On Monday 17 October 2005 13:27, Stéphane Brunet wrote: * If I decide to create a brand new skin, based heavily on content provider and viewlets, which sounds easier to do than the present way to do it, how should I provide the glue between the components which are not content provider-capable

Re: [Zope3-dev] RFC: Content Providers and Viewlets

2005-10-18 Thread Stephan Richter
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

Re: [Zope3-dev] RFC: Content Providers and Viewlets

2005-10-17 Thread Dominik Huber
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

Re: [Zope3-dev] RFC: Content Providers and Viewlets

2005-10-17 Thread Gary Poster
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.

Re: [Zope3-dev] RFC: Content Providers and Viewlets

2005-10-17 Thread Stephan Richter
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

Re: [Zope3-dev] RFC: Content Providers and Viewlets

2005-10-17 Thread Stephan Richter
On Saturday 15 October 2005 15:48, Gary Poster wrote: I have been working on a subview package off in another branch.  It   addresses a class of bugs caused by subviews that affect non- contained subviews; sets the stage for AJAX components and for   independently-configurable drag and drop

Re: [Zope3-dev] RFC: Content Providers and Viewlets

2005-10-17 Thread Gary Poster
On Oct 17, 2005, at 12:02 PM, Stephan Richter wrote: Right, this is a serious problem. I would really like to see some more detailed documentation about this approach. But I am pretty sure this is a problem orthogonal to the content provider code and can be solved in a different package

Re: [Zope3-dev] RFC: Content Providers and Viewlets

2005-10-17 Thread Stephan Richter
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 story for subviews.  The   subview package only sets up

Re: [Zope3-dev] RFC: Content Providers and Viewlets

2005-10-17 Thread Stephan Richter
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,

Re: [Zope3-dev] RFC: Content Providers and Viewlets

2005-10-17 Thread Gary Poster
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

Re: [Zope3-dev] RFC: Content Providers and Viewlets

2005-10-17 Thread Stephan Richter
On Monday 17 October 2005 12:07, Gary Poster wrote: On Oct 17, 2005, at 12:02 PM, Stephan Richter wrote: Right, this is a serious problem. I would really like to see some more detailed documentation about this approach. But I am pretty sure   this is a problem orthogonal to the content

Re: [Zope3-dev] RFC: Content Providers and Viewlets

2005-10-17 Thread Gary Poster
On Oct 17, 2005, at 12:17 PM, Stephan Richter wrote: Thanks for your thoughts and review. ... I really want to talk to you over a higher-bandwidth medium about this. If we could agree on everything but the persistent bits for the 3.2 inclusion then I'd be thrilled. That will mean a number

Re: [Zope3-dev] RFC: Content Providers and Viewlets

2005-10-17 Thread Stephan Richter
On Monday 17 October 2005 12:21, Gary Poster wrote: I think this can only happen, if we can get Roger, Benji, you and   me at the same location for a couple of days. Our ues cases are somewhat   different, but all equally important, especially the update bug of yours. Sounds great to

Re: [Zope3-dev] RFC: Content Providers and Viewlets

2005-10-17 Thread Stéphane Brunet
Stephan Richter wrote: On Monday 17 October 2005 12:21, Gary Poster wrote: Similarly to your comments, I'm worried about viewlets getting in Zope 3.2 without addressing the update problem, myself. Maybe you can simply put an XXX or a warning and be happy with it: not my call. :-)

Re: [Zope3-dev] RFC: Content Providers and Viewlets

2005-10-16 Thread Gary Poster
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

Re: [Zope3-dev] RFC: Content Providers and Viewlets

2005-10-16 Thread Stephan Richter
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

Re: [Zope3-dev] RFC: Content Providers and Viewlets

2005-10-16 Thread Gary Poster
On Oct 16, 2005, at 9:42 AM, Stephan Richter wrote: 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

RE: [Zope3-dev] RFC: Content Providers and Viewlets

2005-10-16 Thread Roger Ineichen
Hi Gary -Original Message- From: Gary Poster [mailto:[EMAIL PROTECTED] Sent: Sunday, October 16, 2005 4:09 PM To: [EMAIL PROTECTED] Cc: zope3-dev@zope.org; [EMAIL PROTECTED] Subject: Re: [Zope3-dev] RFC: Content Providers and Viewlets On Oct 16, 2005, at 9:42 AM, Stephan

Re: [Zope3-dev] RFC: Content Providers and Viewlets

2005-10-15 Thread Gary Poster
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