Skip to content

Commit 41f2c8c

Browse files
committed
improve How behaviors work - fine tuning
1 parent 2394487 commit 41f2c8c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/backend/behaviors.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -139,6 +139,8 @@ Based on the now-provided interface, i.e specific views can be registered with t
139139
In other cases, there is also an adapter factory (usually a class), which will be invoked (initialized) to get an appropriate adapter when requested.
140140
If an adapter factory is used an explicit marker interface is required.
141141

142+
With an adapter factory in place, custom getters and setters for form fields can be implemented, or even new methods i.e. for calculations or to combine data can be added.
143+
142144
### Registration
143145

144146
Behaviors are registered globally using the <plone.behavior /> {term}`ZCML` directive.
@@ -150,8 +152,6 @@ Plone content objects have logic to look up the behaviors names registered from
150152
At runtime, the logic provides the interface (or marker) from the behavior to the object.
151153
This dynamically provided interface enables the component architecture to react to this new interface by adding additional form fields, bindings events, enabling more specific views, and more.
152154

153-
With an adapter factory in place, custom getters and setters for form fields can be implemented, or even new methods i.e. for calculations or to combine data can be added.
154-
155155
### Additional information
156156

157157
```{seealso}

0 commit comments

Comments
 (0)