You can extend the functionality of your dexterity object by writing an adapter that adapts your dexterity object to add another feature or aspect.
But if you want to use this adapter, you must somehow know that an object implements that. Also, you could not easily add more fields to an object with such an approach.
Dexterity has a solution for it, with special adapters that are called and registered by the name behavior.
A behavior can be added to any content type through the web and during runtime.
All default views know about the concept of behaviors and when rendering forms, the views also check whether there are behaviors referenced with the current context and if these behavior have a schema of their own, these fields get shown in addition.
Names and Theory¶
The name behavior is not a standard term in the software development. But it is a good idea to think of a behavior as an aspect. You are adding an aspect to your content type and you want to write your aspect in such a way, that it works independent of the content type on which the aspect is applied. You should not have dependencies to specific fields of your object or to other behaviors.
Such an object allows you to apply the Open/closed principle to your dexterity objects.
So, let us write our own small behavior.
In the future, we want our presentation be represented in Lanyrd (a Social Conference Directory - Lanyrd.com) too. For now we will just provide a link so that visitors can collaborate easily with the Lanyrd site.
So for now, our behavior just adds a new field for storing the url to Lanyrd.
We want to keep a clean structure, so we create a
behaviors directory first, and include it into the zcml declarations of our
<include package=".behaviors" />
Then, we add an empty
behaviors/__init__.py and a
Lets get through this step by step.
- We register a behavior in behaviors/configure.zcml. We do not say for which content type this behavior is valid. You do this, through the web or in the GenericSetup profile.
- We create a marker interface in behaviors/social.py for our behavior and make it also a schema containing the fields we want to declare. We could just use define schema fields on a zope.intereface class, but we use an extended form from plone.supermodel, else we could not use the fieldset features.
- We also add a fieldset so that our fields are not mixed with the normal fields of the object.
- We add a normal URI schema field to store the URI to lanyrd.
- We mark our schema as a class that also implements the IFormFieldProvider interface. This is a marker interface, we do not need to implement anything to provide the interface.
Adding it to our talk¶
We could add this behavior now via the plone control panel. But instead, we will do it directly properly in our GenericSetup profile
We must add the behavior to
1 2 3 4 5 6 7 8 9 10 11
<?xml version="1.0"?> <object name="talk" meta_type="Dexterity FTI" i18n:domain="plone" xmlns:i18n="http://xml.zope.org/namespaces/i18n"> ... <property name="behaviors"> <element value="plone.app.dexterity.behaviors.metadata.IDublinCore"/> <element value="plone.app.content.interfaces.INameFromTitle"/> <element value="ploneconf.site.behaviors.social.ISocial"/> </property> ... </object>