Hi Stephan

> Betreff: Re: [Zope-dev] Interface for renderable component
> On Tuesday 16 September 2008, Malthe Borch wrote:
> > 2008/9/16 Stephan Richter <[EMAIL PROTECTED]>:
> > > Yeah, I like that. This is the right package, since it defines 
> > > high-level patterns without any heavy implementations.
> >
> > Unfortunately, ``zope.contentprovider`` relies on ``zope.tales`` 
> > because it implements a TALES expression and somehow, this package 
> > pulls in zope.app.*-packages.
> Darn. Let me think about that. I guess a new package to 
> collect our community-agreed high-level UI patterns would be 
> good then.
> From my point of view, it should include the following patterns:
> * update/render
> * generic IRenderer API (based on update/render!)

Is the IRenderer interface not exactly the same
like the IContentProvider?

Does it provide an additional __call__ method?
Or only  __call__ method?

It smells to me that we should name it to something like
IProvider if it's a base for our IContentProvider or
IXHTMLProvider if it provides XHTML based on z3c.pt

I preferre anything with the word provider instead of

> * Probably the concept of content providers
> The package should probably live int he zope.* namespace.
> Anything else?

yes, this package must be a zope.* package.
Then we could move the ITerms interface to this
package too rather then add a new one like zope.term.

> > I think we should work to never have zope.*-packages depend on
> > zope.app.* ––– and perhaps declare a truce on minimizing 
> > dependencies within the zope.* group of packages (it seems 
> very difficult).
> I agree.
> Regards,
> Stephan
> --
> Stephan Richter
> Web Software Design, Development and Training Google me. 
> "Zope Stephan Richter"

Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to