Plone's Specific Implementation of Tiles
plone.app.tiles is Plone's UI integration for plone.tiles.
This package contains the following things:
- A view
@@add-tile, and an associated form, which can be used to create a new tile based on the tile's schema. For transient tiles, this merely redirects to a URL with an appropriate query string. For persistent tiles, it will also save the necessary data. This will fire an
IObjectCreatedEventas well as an
IObjectAddedEventfor the newly created tile (a transient object) when successfully submitted. In the case of the
newParentattribute will be the tile's context, and the
newNameattribute will be the tile's id.
@@add-tileview, when accessed directly, allows the user to choose from all available tiles (subject to the tile's add permission) and redirects to the appropriate
@@add-tile/<tile-type>URL to configure the tile.
- A view
@@edit-tile, and an associated form, which can be used to edit a tile based on the tile's schema. This will fire an
IObjectModifiedEventfor the modified tile (a transient object) when successfully submitted.
- A view
@@delete-tile, where the user may select a tile type, enter a tile id, and opt to clear out any persistent data for that tile. This can also be called by AJAX code given appropriate request parameters. This will fire an
IObjectRemovedEventfor the removed tile (a transient object). The
oldParentattribute will be the tile's context, and the
oldNameattribute will be the tile's id.
The default add and edit forms should suffice for most use cases. You can use plone.autoform to configure alternative widgets.
If you need a custom form,
you can register an add view as an adapter from
(context, request, tileType),
tileType is an instance providing
The actual integration of the various views is left up to other packages (such as the Mosaic editor).