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 implement something
>> useful for handle ISource objects.
>> =20
>> If it comes to implement a widget framework is looks a little bit
>> different. A widget framework can define an API which othter can use.
>> ITerms in zope.app.form does that already. You can do what ever
>> you need to do in such an ITerms adapter for access the ISource and
>> return standard ITerm objects which the widget can handle.
>> =20
>> 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 different than ITerms
> but that you see a structural similarity between what you want and what
> ITerms already do.
> 
> I think this causes some confusion (and resistance by my side) right
> now.
> 
> Can you try to phrase what you want to achieve and maybe not use the
> word 'ITerms' (for now)?

Right. What's the difference from the ITerms we have now? Why do I need it?

-- 
Christian Zagrodnick · [EMAIL PROTECTED]
gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 4 · fax +49 345 1229889 1
Zope and Plone consulting and development


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

Reply via email to