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 objects, I'll start a zope.schema branch and 
> let you know about the progress and a hopfully a simple
> solution. Additional to them I started allready a 
> z3c.form branch for adjust the ITerms implementation.
> As far as I can see right now this refactoring will only 
> provides additional features.
> What do you think? Any objections or hints about that?

Terms require access to a request. Any application's model code should
be happy to only deal with the values of sources.

Terms are used to map values to the UI parts of an application (by
providing identification tokens and user readable titles).

IMHO zope.schema doesn't need to know about terms.

I do agree that the whole issue of searching/querying sources is
currently underdesigned.


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

Attachment: signature.asc
Description: This is a digitally signed message part

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