[Framework-Team] Re: wicked integration w/ plone 3

[Rocky Burt]

On Fri, 2007-05-01 at 04:10 -0600, whit wrote:
> what fields get the wicked treatment is current determined in zcml(the 
> zcml marks the specific fields to enact behavior therefore has to happen 
> act configuration time rather than via persistent component). 
> 
> This provides some flexibility, but later we may want to mark the fields 
> more explicitly(say, in the content class itself).   I chose the 3 
> configuration options above mainly to cess out possible problems; I 
> imagine we would decide on a configuration to ship plone with, and then 
> the intrepid could twiddle the zcml if they so desired. 

You might want to consider using content type based utilities to
determine which fields get the treatment.  Say...

  class IWickedFieldMarkers(Interface):
      at_schema_fields = schema.List(title=u'AT Schema Fields')

You could lookup the utilities like
zope.component.getUtility(IWickedFieldMarkers, name=portal_type) to
determine what fields should get transformed.

Of course later on if we move Plone to an IContentType based system we
could instead use adapters that adapt on IContentType instead.

This would allow us to configure everything on a per ISite (read: per
plone portal) basis by using local utilities.  No more zope-wide
settings unless someone setup global utilities for their own custom
type.

Anyhow, just an idea.  I'm sure the names I picked are rather crude :)

- Rocky

-- 
Rocky Burt
ServerZen Software -- http://www.serverzen.com
News About The Server (blog) -- http://www.serverzen.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.plone.org/pipermail/plone-framework-team/attachments/20070105/23a61b51/attachment.asc>