> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Jim Fulton
> Sent: Sunday, September 25, 2005 12:47 PM
> To: [EMAIL PROTECTED]
> Cc: firstname.lastname@example.org; 'Stephan Richter'
> Subject: [Zope3-dev] Re: Content provider API
> Roger Ineichen wrote:
> > Hi together
> > I added a proposal where is important for the CPSSkin work and the
> > zope.app.viewlet implementation.
> > Can you take a look at it and tell me what do you think about.
> > I hope it will be possible to implement a generic lookup concept
> > in page templates where we can use for CPSSkin or the viewlet
> > implementation form Stephan.
> > I have some need for such a base API in the Tiks framework and
> > plan to implement this at the Neckar sprint if possible.
> > Proposal
> > iderAPIForSkins
> I find this proposal a bit light on motivation.
I think it's important to have such a API. Otherwise we get
imcompatible 'additional content provider' implementations.
> What is a content provider and why do you need one?
A content provider is a comonent where knows about additional
content where should get rendered into a region of the page template.
Additional content is a 'html fragment'. Right now there is a
vielwet implementation in zope.app.viewlet and before was a
pagelet implementation which can be defined as 'additional content'.
Regions are implemented in the zope.app.viewlet.interface right now.
But I guess a region should be able to collect more then only viewlets.
The same pattern could be used for JSR 168 like portlet implementations.
> Jim Fulton mailto:[EMAIL PROTECTED] Python Powered!
> CTO (540) 361-1714 http://www.python.org
> Zope Corporation http://www.zope.com http://www.zope.org
> Zope3-dev mailing list
Zope3-dev mailing list