Search results for dexterity

python2-plone-app-stagingbehavior-0.1-1.lbn25.noarch

Introduction The IStagingSupport behavior is used for enabling the plone.app.iterate functionality for Dexterity content. It allows you to perform the checkout and checkin operations to work on a copy of your original content. --Just use the behavior plone.app.stagingbehavior.interfaces.IStagingSupport in your Dexterity content-type.In your *profiles/default/types/YOURTYPE.xml* add the...

python2-plone-app-versioningbehavior-1.4.6-1.lbn25.noarch

Introduction The plone.versioning (IVersionable) behavior is used for enabling the CMFEditions functionality for dexterity contents. It adds a changeNote- field to the edit- and add-forms and creates a new version when the content is edited, if enabled for the content type.It's based on *Products.CMFEditions*. For listing the versions of an object use CMFEdtions' view versions_history_form or...

python2-plone-app-widgets-3.0.7-1.lbn25.noarch

2.x is only to be used with Plone 5 and 1.x is to be used in Plone 4.3.ContentsThe goal of plone.app.widgets is to provide an implementation for a new set of javascript widgets being developed outside Plone as part of Mockup_ project. It overrides explicit widgets used in dexterity and archetypes to provide tested and modularized widgets based on the concept of *patterns*. :target:

python2-plone-dexterity-2.10.5-1.lbn25.noarch

Dexterity "Same, same, but different"Dexterity is a system for building content types, both through-the-web and as filesystem code. It is aimed at Plone, although this package should work with plain Zope + CMF systems.Key use cases -Dexterity wants to make some things really easy. These are:- Create a "real" content type entirely through-the-web without having to know programming.- As a...

python2-plone-directives-dexterity-1.0.2-1.lbn25.noarch

plone.directives.dexterity This package provides optional, Grok-like directives for configuring Dexterity content. It depends on five.grok, which in turn depends on the various re-usable grokcore.* packages, but not Grok itself.See also plone.directives.form, which provides directives for configuring schema interfaces with form hints.Content classes Content extending the Dexterity 'Item' and...

python2-plone-directives-dexterity-1.0.2-4.lbn25.noarch

plone.directives.dexterity This package provides optional, Grok-like directives for configuring Dexterity content. It depends on five.grok, which in turn depends on the various re-usable grokcore.* packages, but not Grok itself.See also plone.directives.form, which provides directives for configuring schema interfaces with form hints.Content classes Content extending the Dexterity 'Item' and...

python2-products-cmfdifftool-3.3.3-1.lbn25.noarch

Diff tool for Plone.Dexterity To enable versioning for a Dexterity content type you need to:1. Install plone.app.versioningbehavior_ and use it on your content type. 2. Enable versioning for the type in the types control panel. 3. Install this package. 4. Go to the portal_diff tool ZMI page. 5. Add Compound Diff for Dexterity types for your content type. Field name can be anything, e.g:...

python2-transmogrify-dexterity-2.0.0-1.lbn25.noarch

Introduction The transmogrify.dexterity package provides a transmogrifier pipeline section for updating field values of dexterity content objects. The blueprint name is transmogrify.dexterity.schemaupdater.The schemaupdater section needs at least the path to the object to update. Paths to objects are always interpreted as being relative to the context. Any writable field who's id matches a key...

python2-wildcard.media-2.1.0-1.lbn25.noarch

Introduction :height: 50 :width: 382This package provides Audio and Video Dexterity content types and behaviors, conversions and players/views.It integrates the HTML5 media player mediaelementjs_ and uses plone.app.async_ if installed to convert videos to common formats... _mediaelementjs: .. _plone.app.async: - Audio and Video types - Integration with mediaelementjs_ designed for maximum...

plone.app.mosaic-1.0b3-1.lbn19.noarch

Plone Mosaic is a new layout solution for Plone. It’s built for Plone 5, but should also work on Plone 4.3 with plone.app.widgets. Read this introduction and the package documentation for more details how to use this package. Concepts Mosaic, Blocks and Tiles provide a simple, yet powerful way to manage the pages on your Plone website. At their core, they rely on semantic HTML and resources with valid, publishable URLs. Mosaic Editor editor is a visual editor for pages rendered using Blocks. It relies on a grid system to place tiles onto a page in an intuitive, WYSIWYG, drag-and-drop manner. Using Mosaic Editor, it is easy to compose pages with complex, balanced and visually appealing layouts. - custom layout behavior for Dexterity content types Currently, the Mosaic Editor is activated, when any content with Custom layout view active is being edited. (Custom layout is available for any content with Layout support behavior enabled.) Blocks is a rendering algorithm based on HTML markup conventions. A page managed by Mosaic Editor is stored as a simple HTML document representing the actual content of that page as a standalone, publishable resource devoid of any site layout content (e.g. global navigation elements). This is referred to as content layout. Tiles represent the dynamic portions of a page. At its most basic level, a tile is simply an HTML document with a publishable URL. In practice, tiles are usually implemented as browser views deriving from the Tile base class and registered with the <plone:tile /> ZCML directive. This allows tiles to have some basic metadata and automatically generated edit forms for any configurable aspects , which Deco will expose to users. See plone.tiles for examples. When work with tiles in Mosaic Editor, there are three types of tiles: Text tiles Static HTML markup (WYSIWYG-edited text) placed into the content or site layout. Strictly speaking, text tiles are not tiles in that they do not involve any tile fetching or merging - instead they are stored as part of the page or site layout. To the user, however, a text tile can be moved around and managed like any other. Field tiles Render the value of a metadata field such as the title or description. The values of field tiles may be edited in-place in the page, but the value is stored in the underlying field and can be indexed in the catalog, used for navigation and so on. In practice, a field tile is an instance of the special tile plone.app.standardtiles.fields with the field name passed as a parameter. App tiles Any other type of dynamic tile. Examples may include a folder listing, a media player, a poll or pretty much anything else you can think of.