Modified items

All recently modified items, latest first.

plone4artists-z2utils-1.0.2-4.lbn19.noarch: Miscellaneous utilities for Zope 2

plone4artists-videoembed-1.3-2.lbn19.noarch: A registry and adapters for converting urls for various video sharing sites into embed codes.

plone4artists-video-1.4-1.lbn19.noarch: Upload a video file to your Plone site and it is automatically detected as a video file, and an appropriate player is used on the view page. You can also add videos that are hosted at Google Video, YouTube, blip.tv, etc. and they will be embedded in your Plone site.

plone4artists-subtyper-1.2.2-2.lbn19.noarch: p4a.subtyper is a subtyping framework for Plone. In this context, subtyping means to provide additional specific types onto existing content types. An example to standard Plone would be to have only one File content type (and no Image content type). The Image content type would then become a sub-type of the File content type. It also exposes the possible sub-types for a given object in the content menu with a sub-types dropdown menu.Miscellaneous utilities for Zope 2

plone4artists-plonevideoembed-1.3-2.lbn19.noarch: p4a.plonevideo is a video add-on for the Plone CMS.

plone4artists-plonevideo-1.3-2.lbn19.noarch: p4a.plonevideo is a video add-on for the Plone CMS.

plone4artists-ploneevent-0.7.4-2.lbn19.noarch: This package contains extensions to the standard Event of Plone. Currently only the extension is included: Recurrence.

plone4artists-plonecalendar-2.1-1.lbn19.noarch: p4a.plonecalendar is a project which extends the p4a.calendar framework to run natively within a Plone environment. It contains the extensions that require Plone, and the adaptions to Plone. This is mainly support for Plone event types and iCalendar import/export. Plone4Artists calendar can import an iCalendar file over http into a Plone calendar. This is useful for example if another site presents a schedule that you also want to present or integrate into your site. An example url for importing an icalendar file over http is:: http://path/to/calendar/import_from_url?url=http://url/to/icalendarfile.ics This will open up a connection to the other site, get the icalendar file called "icalendarfile.ics" and import it into the folder located at /path/to/calendar/

plone4artists-ploneaudio-1.1rc1-5.lbn19.noarch: The p4a.ploneaudio egg is a Plone product built to expose the p4a.audio framework in a Plone setting. In a nutshell it provides the following features: File support Uploaded File objects are scanned for audio mime types and are audio enhanced automatically if a registered mime type is found. Audio container support Any folder or smart folder can be media activated which turns it into an audio container which knows how to display an overview for all contained audio. Embedded media player support MP3 and Ogg audio files can be played inline within the browser. Audio metadata support Audio information is read from and written to MP3 and Ogg audio files. Podcasting support Audio containers (activated folders or smart folders) can have ther contents broadcast using RSS with enclosures representing the individual audio files. Content Licensing support All audio content can automatically be licensed using the ContentLicensing product.

plone4artists-fileimage-1.0.2-3.lbn19.noarch: p4a.file is a field/widget pair for handling fields that contain binary data.

plone4artists-common-1.1-1.lbn19.noarch: Reusable code-bits for Zope 3 and Plone

plone4artists-calendar-2.1b1-1.lbn19.noarch: The p4a.calendar package is a package for producing calendars from collection of events. Features include: Monthly, Weekly, Daily view Any calendar activated (smart) folder can has several default views including a monthly, weekly and daily view. Chronological event view The events gathered together by the activated calendar can be displayed using a chronological event listing. Past events view Events that have already occurred are grouped into a past events listing page. Color coding by event type Events can be color coded based on what event type (keyword) they have been assigned.

plone4artists-audio-1.1rc1-3.lbn19.noarch: Upload a normal File to your Plone site, and Plone4ArtistsAudio will detect it as an MP3 or Ogg file and "decorate" it with metadata.

plone4artists-1.1-1.lbn19.noarch: Base p4a module

plone4.csrffixes-1.1.1-1.lbn25.noarch: The package aims to backport the auto CSRF implementation from Plone 5 to Plone 4. The reason this is necessary is because there are a lot of CSRF problem with the ZMI that Zope2 will never be able to fix. See https://plone.org/products/plone/security/advisories/security-vulnerability-20151006-csrf for more details.

plone.z3cform-0.9.1-1.lbn25.noarch: plone.z3cform is a library that allows use of z3c.form with Zope 2 and the CMF.

plone.uuid-1.0.6-1.lbn19.noarch: UUIDs for content items

plone.transformchain-1.2.2-1.lbn25.noarch: Hook into repoze.zope2 that allows third party packages to register a sequence of hooks that will be allowed to modify the response before it is returned to the browser

plone.tiles-1.8.1-1.lbn25.noarch: 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: <link rel="tile" target="placeholder" href="./@@sample.tile/tile1?option1=value1" /> 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 - <plone:tile /> - 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.

plone.theme-2.1.5-1.lbn25.noarch: This package lets you mark the request with a "layer" interface conditional on the currently selected skin (theme) in the portal_skins tool. Most Zope 3 "visual" directives, like <browser:page /> or <browser:viewlet /> accept a 'layer' attribute, which should point to an interface. Recall that a view is a multi-adapter on (context, request). Most views are registered so that the 'request' being adapted only needs to provide Interface. This is equivalent to saying layer="*". By applying a marker interface to the request, and registering a view or viewlet with this interface as the adapted 'layer', we can override a more general view, or make a viewlet that is only shown for a particular layer. In the context of CMF and Plone, we'd like to tie the layer to the current skin selection. We do that by name. What you have to do First, you should create a marker interface: >>> from zope.interface import Interface >>> class IMyTheme(Interface): ... """Marker interface for skins part of 'My Theme' ... """ Then, register this as a theme layer in ZCML: <interface interface=".interfaces.IMyTheme" type="zope.publisher.interfaces.browser.IBrowserSkinType" name="My Theme" /> The title here must match the name of the theme/skin selection in portal_skins. How it works Behind the scenes, the <interface /> registration marks IMyTheme with the "IInterface" IThemelayer, and registers IMyTheme as a utility named "My Theme" and providing IBrowserSkinType. We do something to this effect in tests/tests.zcml. Let us define the "My Theme" skin selection: >>> from Products.CMFCore.utils import getToolByName >>> portal_skins = getToolByName(self.portal, 'portal_skins') >>> default_skin = portal_skins.getDefaultSkin() >>> skin_path = portal_skins._getSelections()[default_skin] >>> portal_skins.addSkinSelection('My Theme', skin_path) In tests/tests.zcml we have registered two version of a view called @@layer-test-view. One, for the default skin layer, simply outputs "Default". The other outputs "My Theme". Before we turn on the skin, we will get the default view. >>> from Products.Five.testbrowser import Browser >>> browser = Browser() >>> browser.open(self.portal.absolute_url() + '/@@layer-test-view') >>> print browser.contents Default However, if we turn the skin on, we should see the effects of the marker interface being applied. >>> portal_skins.default_skin = 'My Theme' >>> browser.open(self.portal.absolute_url() + '/@@layer-test-view') >>> print browser.contents My Theme And if we switch back: >>> portal_skins.default_skin = 'Plone Default' >>> browser.open(self.portal.absolute_url() + '/@@layer-test-view') >>> print browser.contents Default

« Previous 20 items Next 20 items » 1 ... 572 573 574 575 576 577 578 ... 2449


	Copyright © 2000-2026 Corporation of Balclutha Inc. All rights reserved.

Sections

Modified items