doc/book/en/development/webstdlib/autoform.rst
author Sylvain Thénault <sylvain.thenault@logilab.fr>
Tue, 25 Aug 2009 18:47:25 +0200
branch3.5
changeset 2993 2d06451013ac
parent 2172 cf8f9180e63e
child 4256 bf6e0e75acfa
permissions -rw-r--r--
[actions box] implements #344415, will have to take care to application relying on the old behaviour

The automatic entity form (:mod:`cubicweb.web.views.autoform`)
---------------------------------------------------------------

It is possible to manage attributes/relations in the simple or multiple
editing form thanks to the following *rtags*:

* `primary`, indicates that an attribute or a relation has to be
  inserted **in the simple or multiple editing forms**. In the case of
  a relation, the related entity editing form will be included in the
  editing form and represented as a combobox. Each item of the
  combobox is a link to an existing entity.

* `secondary`, indicates that an attribute or a relation has to be
  inserted **in the simple editing form only**. In the case of a
  relation, the related entity editing form will be included in the
  editing form and represented as a combobox. Each item of the combobox
  is a link to an existing entity.

* `inlineview`, includes the target entity's form in the editing form
  of the current entity. It allows to create the target entity in the
  same time as the current entity.

* `generic`, indicates that a relation has to be inserted in the simple
  editing form, in the generic box of relation creation.

* `generated`, indicates that an attribute is dynamically computed
  or other,  and that it should not be displayed in the editing form.

If necessary, it is possible to overwrite the method
`relation_category(rtype, x='subject')` to dynamically compute
a relation editing category.