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 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. > > 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)? Christian -- Christian Theune · [EMAIL PROTECTED] gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development
signature.asc
Description: This is a digitally signed message part
_______________________________________________ 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 )
