Hi Jim, Stephan
> Betreff: Re: [Zope-dev] Make simple ISource usable
>
> On Tuesday 02 September 2008, Jim Fulton wrote:
> > > An alternative to Roger's proposal would be to move the ITerms
> > > declaration and any possible generic implementation of
&g
On Tuesday 02 September 2008, Jim Fulton wrote:
> > An alternative to Roger's proposal would be to move the ITerms
> > declaration and
> > any possible generic implementation of such into its own package
> > zope.terms.
>
> I don't have a problem with that. :)
That's what I thought. Impasse re
On Sep 2, 2008, at 10:38 AM, Stephan Richter wrote:
> On Tuesday 02 September 2008, Jim Fulton wrote:
>>> This whould not affect other implementations like
>>> the ISourceQueriables etc. It only offers the
>>> a way to implement reusable simple ISource components
>>> without the need that every U
On Aug 31, 2008, at 4:51 PM, Marius Gedminas wrote:
> On Sun, Aug 31, 2008 at 10:23:00PM +0200, Christian Zagrodnick wrote:
>> Wait. zope.schema really shouldn't know about terms. Terms are about
>> the user interface, hence title/token. That has really *nothing* to
>> do
>> with zope.schema. F
Hi Jim
> Betreff: Re: [Zope-dev] Make simple ISource usable
>
>
> On Aug 30, 2008, at 10:54 AM, Roger Ineichen wrote:
> > But zope.schema does already know about term.
>
> This was a mistake.
Let's fix that mistake and do it right. That's all
I'm asking
Hi Stephan
> Betreff: Re: [Zope-dev] Make simple ISource usable
>
> On Tuesday 02 September 2008, Jim Fulton wrote:
> > > This whould not affect other implementations like the
> > > ISourceQueriables etc. It only offers the a way to implement
> > > reusab
On Tuesday 02 September 2008, Jim Fulton wrote:
> > This whould not affect other implementations like
> > the ISourceQueriables etc. It only offers the
> > a way to implement reusable simple ISource components
> > without the need that every UI framework needs to
> > implement their own interfaces
On Aug 30, 2008, at 10:54 AM, Roger Ineichen wrote:
> But zope.schema does already know about term.
This was a mistake.
...
> ISource uses ITerm as items.
No it doesn't.
Jim
--
Jim Fulton
Zope Corporation
___
Zope-Dev maillist - Zope-Dev@zope.o
On Aug 29, 2008, at 9:01 AM, Roger Ineichen wrote:
> I'll try to make the ISource API smooth and usable
> for other components. Right now ISource provides no
> simple API for work with terms.
>
> Since a ISource only provides a __contains__ method
> and the IterableSource the __iter__ method,
> t
Hi Christian
> Betreff: Re: [Zope-dev] Make simple ISource usable
>
> On Sun, 2008-08-31 at 16:51 -0400, Marius Gedminas wrote:
> > On Sun, Aug 31, 2008 at 10:23:00PM +0200, Christian
> Zagrodnick wrote:
> > > Wait. zope.schema really shouldn't know about term
Hi Christian
> Betreff: Re: [Zope-dev] Make simple ISource usable
[...]
> > The ITrems is a standard API for handle ISource, doesn't
> nmatter how
> > you will query or get our data form an ISource.
>
> This sounds like you want to implement something differen
Hi Christian
> Betreff: Re: [Zope-dev] Make simple ISource usable
[...]
> > This sounds like you want to implement something different
> than ITerms
> > but that you see a structural similarity between what you want and
> > what ITerms already do.
> >
> >
Hi Christian
> Betreff: Re: [Zope-dev] Make simple ISource usable
[...]
> > Are you arguing that zope.schema.Field should not have a title
> > attribute?
>
> No no no, sorry :)
>
> I only don't see why I need titles for a source all the time.
> If you need
On 2008-08-31 22:51:38 +0200, Marius Gedminas <[EMAIL PROTECTED]> said:
>
>
>
>
> On Sun, Aug 31, 2008 at 10:23:00PM +0200, Christian Zagrodnick wrote:
>> Wait. zope.schema really shouldn't know about terms. Terms are about=20
>> the user interface, hence title/token. That has really *nothing*
On 2008-09-01 06:58:16 +0200, Christian Theune <[EMAIL PROTECTED]> said:
>
>
>
>
> Hi,
>
> sorry for removing all the quotes, but I need to clarify your baseline
> question a bit.
>
> On Sun, 2008-08-31 at 23:23 +0200, Roger Ineichen wrote:
>> Yes exactly, it's up to the developer how they i
Hi,
sorry for removing all the quotes, but I need to clarify your baseline
question a bit.
On Sun, 2008-08-31 at 23:23 +0200, Roger Ineichen wrote:
> Yes exactly, it's up to the developer how they implement something
> useful for handle ISource objects.
>
> If it comes to implement a widget fram
On Sun, 2008-08-31 at 16:51 -0400, Marius Gedminas wrote:
> On Sun, Aug 31, 2008 at 10:23:00PM +0200, Christian Zagrodnick wrote:
> > Wait. zope.schema really shouldn't know about terms. Terms are about
> > the user interface, hence title/token. That has really *nothing* to do
> > with zope.schem
Hi Christian
> Betreff: Re: [Zope-dev] Make simple ISource usable
[...]
> >> IMHO zope.schema doesn't need to know about terms.
> >
> > I agree if you think about the ITerms adapter pattern like
> defined in
> > zope.app.form using (source, request)
On Sun, Aug 31, 2008 at 10:23:00PM +0200, Christian Zagrodnick wrote:
> Wait. zope.schema really shouldn't know about terms. Terms are about
> the user interface, hence title/token. That has really *nothing* to do
> with zope.schema. For searching you don't need titles or tokens. For a
> search
On 2008-08-30 16:54:57 +0200, "Roger Ineichen" <[EMAIL PROTECTED]> said:
> Hi Chritian
>
>> Betreff: Re: [Zope-dev] Make simple ISource usable
>>
>
>> On Fri, 2008-08-29 at 15:01 +0200, Roger Ineichen wrote:
>>> [...]
>>>
>
Hi Chritian
> Betreff: Re: [Zope-dev] Make simple ISource usable
>
> On Fri, 2008-08-29 at 15:01 +0200, Roger Ineichen wrote:
> > [...]
> >
> > The only query API defined for ISource in zope.schema is the
> > ISourceQueriables API. That's defently to
On Fri, 2008-08-29 at 15:01 +0200, Roger Ineichen wrote:
> [...]
>
> The only query API defined for ISource in zope.schema
> is the ISourceQueriables API. That's defently to less
> and makes it required to implement custom query APIs
> in UI frameworks if we need to work with terms.
>
> I no one o
22 matches
Mail list logo
