Am 17.09.2008 um 01:57 schrieb Roger Ineichen:
[...]
>> Could this package be called ``zope.browser`` then?
>
> +1 to this hot topic
>
> I like the idea to have a pure interface package
> for some basic (context, request) adapter components
> called views, browser pages or contentprovider etc.
Hi
Hi Malthe
> Betreff: Re: [Zope-dev] Interface for renderable component
>
> 2008/9/16 Roger Ineichen <[EMAIL PROTECTED]>:
> > yes, this package must be a zope.* package.
> > Then we could move the ITerms interface to this package too rather
> > then add a new on
2008/9/16 Roger Ineichen <[EMAIL PROTECTED]>:
> 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.
Could this package be called ``zope.browser`` then?
\malthe
___
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
> > >
2008/9/16 Roger Ineichen <[EMAIL PROTECTED]>:
> Are you thinking about a basic UI interface package.
> where we probably define some interfaces e.g.
> IBrowserPage and friends and nothing else?
It really depends on how much we want to play with frameworks like
repoze.bfg that do not want complete
Hi Malthe
> Betreff: Re: [Zope-dev] Interface for renderable component
>
> 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.
>
> Unfo
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``
> bec
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 packa
On Monday 15 September 2008, Roger Ineichen wrote:
> Why not define a IHTMLProvider or someting like that
> located in the zope.contentprovider package.
Yeah, I like that. This is the right package, since it defines high-level
patterns without any heavy implementations.
Regards,
Stephan
--
Step
