Personal tools
Skip to content. | Skip to navigation
Introduction ============ EEA Relations package redefines relations in Plone. Right now in Plone any object can be in relation with any other object. EEA Relations lets you to define possible relations between objects. EEA Relations also comes with a nice, customizable faceted navigable popup for relations widget. Once installed from "Add-ons", the package will add an utility called "Possible relations" under "Control Panel". .. contents:: Main features ============= Main goal of EEA Relations is to be an alternative to the default Plone related item widget. EEA Relations features: 1. Define/restrict what kind of content types a certain content can relate to 2. Set restrictions on possible relations (e.g. relations can be made only with published content) 3. You can define easy to use faceted searches (using EEA Faceted navigation) on the relate items popup 4. Nice visual diagram showning all the relations and restrictions you defined (Control Panel -> Possible relations)
It is simple to use, you only have to specify the sparql endpoint url and the sparql query. The results will be converted in an exhibit json, what can easily be reused (ex. by eea.daviz). Main features ============= The main features are: 1. create sparql queries 2. create sparql bookmark folders, sparql queries are created automatically, and can be synchronized manually or automatically (with a cronjob). If a query is changed, a new version of the object is created, so older ones are not lost. 3. results are downloadable in various formats: JSON, Exhibit JSON, HTML, XML, XML with Schema, CSV, TSV
EEA Versions is a versioning system based on a version ID to group certains objects and EffectiveDate to determine version number.
TTW customization of template-based Zope 3 views
five.formlib provides integration of the zope.formlib and zope.app.form packages into the Zope2 application server.
This package integrates zope.globalrequest with Zope 2. It is compatible with Zope 2.12 and later. In Zope 2.10, you can install ZPublisherEventsBackport to use it. The only thing you need to do to use this package is to load its configuration from your own ZCML file: <include package="five.globalrequest" /> You can now use zope.globalrequest as normal: from zope.globalrequest import getRequest request = getRequest() The request is set up when publication starts, when the IPubStart event is fired. It is cleared on one of the IPubEnd events: IPubSuccess or IPubFailure. If you have your own event handlers for either of these events, you should be aware that the event setup/clear could happen after/ before your own event handler is executed, since the order of execution for event handlers is not controllable.
five.grok is a development layer for Zope 2, based on Grok framework concepts. The development techniques are similar to the ones used with Grok framework. It is based on grokcore namespace packages that were factored out of Grok framework. Implemented features Coming from Grok, the following components are available to Zope 2 developers: * Zope 3 Component (Adapter, Global utilities, Subscribers), * Permissions, * Views and Viewlets, * Skins and resources directories, * Page Templates (using the Zope 2 Page Templates), * Formlib forms, * Local sites and local utilities, * Annotations.
s package makes it possible to use zope.app.intid (and consequentually other packages that rely on it such as zope.app.keyreference) in a Zope2 environment.
five.localsitemanager attempts to provide a local site manager implementation that is as close to Zope 3's implementation as possible. Some reservations that do not conflict with Zope 3 have been made to ease the path with CMF.