This package provides declarative configuration (grokkers) for the plone.tiles package.
Usage
A basic tile is configured like this:
from five import grok
from plone.directives import tiles
from my.package import MyMessageFactory as _
from my.package.interfaces import IMyTileSchema
class MyTile(tiles.Tile):
grok.context(IContext)
grok.require('zope2.View')
grok.name('my.tile')
grok.title(_(u"My title"))
grok.description(_(u"My description"))
tiles.add_permission('mypackage.AddMyTile')
tiles.schema(IMyTileSchema)
Notes
A persistent tile can be configured by deriving from PersistentTile instead of Tile.
The context(), requires(), name(), and layer() directives are used in the same way as they are for a view derived from grok.View.
Templates are associated using the same semantics as are used for views. For example, a tile in mytiles.py defined in the class MyTile would be associated with a template mytiles_templates/mytile.pt by default.
Unlike a view, the name() directive is required and should give a dotted name for the tile by convention.
Dictionary key access (__getitem__()) is defined to work as it does in a tile. In a standard grokked view, it will retrieve a macro from the template. In a tile, it is used as a traversal hook to set the tile id, and subsequently to look up views on the tile. See plone.tiles for details.
Similarly, standard grokked views have a url() method which can be used to construct a URL, possibly with query string parameters. For grokked tiles, this is replaced by a url read-only property, which returns the canonical tile URL, as per plone.tiles.
Changelog
1.2 (unreleased)
Use zope.interface decorators. [gforcada]
Change i18n domain. [thet]
Cleanup package. [maurits]
1.1 (2012-11-26)
Added icon directive to support plone.tiles >= 1.1. [datakurre]
1.0 (2012-06-23)
Initial release [garbas]
Metadata
Release files for plone.directives.tiles 1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| plone.directives.tiles-1.2.tar.gz | 5.8 kB | Without provenance | Details for plone.directives.tiles-1.2.tar.gz |
Release files / plone.directives.tiles-1.2.tar.gz
| Download URL | plone.directives.tiles-1.2.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b6423aa5fdad0890d9504817eeb31741079ae1a25086eda098294bfc1d4f256a
|
|
BLAKE2b-256 checksum How to use checksums |
ff83f0dc60a3270fb9e8964613757459298459291d795c0059d588cf8bea6f0e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for plone.directives.tiles 1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.