Miles Waller wrote: > AFAICS, CMFMember covers two sets of requirements: > > - put members through a workflow
Very useful.
> - use archetypes to configure member objects which behave like normal > zope objects
I'm not familiar enough with archetypes to tell what the actual benefits of this is. Could someone summarize?
_______________________________________________
Zope-Dev maillist - [EMAIL PROTECTED]
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 )
