Content Provider API for skins

Status

IsProposal

Author

Roger Ineichen (dev@projekt01.ch)

Problem/Proposal

Implement API for lookup additional content.

Goals

First, I try to explain this idea wihtout to use pagelets, viewlets or portlets, but this concept describes something like a manager for this kind of implementation.

Additional content means content where will be included in a page template wihtout to define the content in the page template directly.

A additional content provider is a component where knows how to provide additonal content where will be rendered in a page.

Right now we have the viewlet implementation zope.app.viewlet which replaces the pagelet implementation.

Since the lookup for such additional content isn't defined as a base concept in zope3 where additional concept can use, we have to use the lookup implemented in the viewlet package.

This will make it impossible to use other additional content provider like portlets (what ever this will be) in the same region (content area) of a page template if the lookup concept doesn't fit.

Proposed Solution

Something like the IRegion? interface defined in the zope.app.viewlet.interfaces and it's lookup concept with the TALES expression can be a concept for this kind of API.

The lookup concept for additional content and it's reqiured interfaces should be defined in a zope.app package. This whould make it possible to implement different future concept.

Risks

Other template concept uses different lookup mechanism. (e.g. Quicksilver)