Skip to content

Commit 6408ba3

Browse files
MrTangojensens
andcommitted
Update docs/classic-ui/forms.md
Co-authored-by: Jens W. Klein <[email protected]>
1 parent e67cc36 commit 6408ba3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/classic-ui/forms.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,8 @@ Fields, Widgets, Vocabularies aso are descripted in detail in there own chapter
2020
Plone uses the [z3c.form](http://pythonhosted.org/z3c.form) library to build its web-forms.
2121
The package responsible for integrating with Plone is [plone.z3cform](http://pypi.python.org/pypi/plone.z3cform).
2222

23-
For an easy way to structure a form and define its widgets and fields, Plone relies on [plone.autoform](http://pypi.python.org/pypi/plone.autoform), in particular its AutoExtensibleForm base class.
24-
Which is responsible for processing form hints and setting up [z3c.form](http://pythonhosted.org/z3c.form) widgets and groups (fieldsets).
23+
To simplify the process of organizing a form and specifying its widgets and fields, Plone utilizes [plone.autoform](http://pypi.python.org/pypi/plone.autoform), in particular its `AutoExtensibleForm` base class.
24+
It is responsible for handling form hints and configuring z3c.form widgets and groups (fieldsets).
2525

2626
A form, therefore, is simply a view that uses these libraries, although [plone.autoform](http://pypi.python.org/pypi/plone.autoform) provides some helpful base classes that make it easier to construct forms based on the form schema or {ref}`Dexterity behaviors <backend-behaviors-label>`.
2727

0 commit comments

Comments
 (0)