Re: RFC: Proposal Dexterity API - two variants

> Explicit behaviors proposal: expose behaviors explicitly
> ========================================================

+1

Implicit magical shadowing would cause weird issues sooner or later.

Dexterity does not prevent implementing custom attributes directly in custom baseclass (yet still allow enabling and disabling visible fields with behaviors). E.g. the default dexterity Item and Container implement DublinCore fields in their baseclass, even those fields are not visible by default.

The new default contenttypes already have custom base classes. So, I wonder, why couldn't they implement their default fields similarly DC is implemented with the base types.

-Asko
------------------------------------------------------------------------------