[Zope-CMF] Store development with CMF (new guy)

[sean.upton@uniontrib.com]

Unfortunately, a lot of apps (I think, including CMFDefault, Plone) depend
on accessing decorated "member object" instead of non-decorated users, or at
least accessing certain properties (either via PropertyManager methods or to
my displeasure via direct attribute access).  I've just operated under the
assumption that there are 'official' interfaces that members and the
memberdata tool need to support, and de-facto ones: for example, it isn't
documented anywhere that the memberdata tool needs to implement the
PropertyManager interface, but many applications and skin scripts
applications assume it does, i.e. in ZPTs to iterate through propertyIds()
for a user-properties form.  Given this, I decided in my tools to target the
assumptions that applications make about the interface of these components
instead of just their official interfaces.

Sean

-----Original Message-----
From: Troy Farrell [mailto:troy@entheossoft.com]
Sent: Tuesday, May 27, 2003 12:05 PM
To: Shane Hathaway
Cc: zope-cmf@zope.org
Subject: Re: [Zope-CMF] Store development with CMF (new guy)


I assume you mean no other CMFCore or CMFDefault code or skins...
Some of my custom apps and skins rely upon decorated users.  Should this 
be done differently?

Troy

Shane Hathaway wrote:
> The only dependency on portal_memberdata is from 
> portal_membership, which defaults to not decorating users if there is no 
> portal_memberdata.  No other code or skins should depend on 
> portal_memberdata! (If it does, it has a bug.)


_______________________________________________
Zope-CMF maillist  -  Zope-CMF@zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests