You are here: Home / LBN / Up2date / Plone 5 / BastionLinux 25 / plone.tiles-2.1-1.lbn25.noarch

plone.tiles-2.1-1.lbn25.noarch

Package Attributes
RPM  plone.tiles-2.1-1.lbn25.noarch.rpm Architecture  noarch Size  236484 Created  2018/10/06 11:03:18 UTC
Package Specification
Summary APIs for managing tiles
Group Application/Internet
License BSD
Home Page http://pypi.python.org/packages/source/p/plone.tiles/plone.tiles-2.1.tar.gz
Description

For the purposes of this package, a tile is a browser view and an associated utility providing some metadata about that view. The metadata includes a title and description, an add permission and optionally a schema interface describing configurable aspects of the tile. The idea is that a UI (such as Deco) can present the user with a list of insertable tiles and optionally render a form to configure the tile upon insertion.

A tile is inserted into a layout as a link:

The sub-path (tile1` in this case) is used to set the tile id attribute. This allows the tile to know its unique id, and, in the case of persistent tiles, look up its data. sample.tile is the name of the browser view that implements the tile. This is made available as the __name__ attribute. Other parameters may be turned into tile data, available under the data attribute, a dict, for regular tiles. For persistent tiles (those deriving from the PersistentTile base class), the data is fetched from annotations instead, based on the tile id.

There are three interfaces describing tiles in this package:

  • IBasicTile is the low-level interface for tiles. It extends IBrowserView to describe the semantics of the __name__ and id attributes. ITile describes a tile that can be configured with some data. The data is accessible via a dict called data. The default implementation of this interface, plone.tiles.Tile, will use the schema of the tile type and the query string (self.request.form) to construct that dictionary. This interface also describes an attribute url, which gives the canonical tile URL, including the id sub-path and any query string parameters. (Note that tiles also correctly implement IAbsoluteURL.) IPersistentTile describes a tile that stores its configuration in object annotations, and is needed when configuration values cannot be encoded into a query string. The default implementation is in plone.tiles.PersistentTile. To make it possible to have several tiles of a given type on the same layout, the annotations are keyed by the tile __name__.

In addition, tiles are described by ITileType, which contains attributes for the tile name, title, description, add permission and schema (if required).

A properly configured tile, then, consists of a browser view providing IBasicTile or one of its derivatives, and a utility providing ITileType with the same name as the tile browser view. There is a convenience ZCML directive - - to register both of these components in one go.

To support creation of appropriate tile links, plone.tiles.data contains two methods - encode() and decode() - to help turn a data dictionary into a query string and turn a request.form dict into a data dict that complies with a tile's schema interface.

Requires
/bin/sh  
rpmlib(PayloadFilesHavePrefix)  
rpmlib(CompressedFileNames)  
rpmlib(FileDigests)  
rpmlib(PartialHardlinkSets)  
rpmlib(PayloadIsXz)  
Provides
plone.tiles
python2.7dist(plone.tiles)
python2dist(plone.tiles)
Obsoletes
plone.tiles-egginfo

Document Actions

Distributions
To see exactly what is included in BastionLinux™, visit our online RPMDistro Builder.
Buy Now
Bastion CD
Subscribe Now
and get BastionLinux™ ...
Sponsored Links