Search results

collective.sylvester-0.2-2.lbn25.noarch

collective.sylvester (Sylvester for short) is a twitter client for Plone. It aims to make tweeting and twitter account management available from within a Plone site. Overview ======== Sylvester has a pluggable dashboard. All other views are loaded via ajax into the dashboard. These pages are currently available: - The main feed. Eerily similar to the homepage on twitter.com. - Friends page. Shows people your are following as tiled portlets. - Replies. Shows messages where you are mentioned. These actions are currently available: - Publish to twitter. Tweet about Plone content on twitter. The URL is shortened by tinyurl.com. - A "Twitter Dashboard" link appears in your personal bar.

collective.tabr-1.2-1.lbn25.noarch

A simple package to add jQuery Tools Tabs UI support to Plone

collective.templateengines-0.3.4-2.lbn25.noarch

collective.templateengines is an template engine abstraction layer for Python. It defines generic Zope interfaces for communicating with various Python template engines to achieve higher code reuse value. This package is still much in development. All contributions and comments are welcome. Features collective.templateengines helps you to achieve * Easy, pluggable, template language switching. Write template tag code only once and use it across all template engines using abstracted tag plug-ings * Clean your codebase from template engine dependencies * Generic error and warning reporting mechanism across template engines * EGG deployment and easy_install support from PyPi repository * Interfaces defined using standard Zope interfaces package * Backends for Django template Language, Cheetah and Jinja2 * Unit tests

collective.testcaselayer-1.6.1-1.lbn25.noarch

The support for layers provided by zope.testing helps to lessen the amount of time consumed during test driven development by sharing expensive test fixtures, such as is often requires for functional test. This package provides several well tested facilities to make writing and using layers faster and easier. The collective.testcaselayer.common.common_layer, used in the Quick Start, also includes some commonly useful test fixtures: a mock mail host remove ‘Unauthorized’ and ‘NotFound’ from error_log ignored exceptions puts the resources registries in debug mode (portal_css, portal_javascripts, portal_kss)

collective.themefragments-1.0.0-1.lbn25.noarch

Diazo Rules may operate on content that is fetched from somewhere other than the current page being rendered by Plone, by using the href attribute to specify a path of a resource relative to the root of the Plone site: <!-- Pull in extra navigation from a browser view on the Plone site root --> <after css:theme-children="#leftnav" css:content=".navitem" href="/@@extra-nav" /> The href attribute can be used with any rule apart from <drop /> and <strip />, and can reference any URL, for example to an existing browser view configured for your site. However, it is often desirable to generate some dynamic content specifically for the purpose of constructing a particular theme. In this scenario, you can use fragments.

collective.tinymceplugins.advfilelinks-1.2.1-1.lbn25.noarch

An advanced Plone TinyMCE plugin for handling links to files

collective.tinymceplugins.codemagic-1.1-1.lbn25.noarch

Integration of the CodeMagic TinyMCE plugin with Plone

collective.tinymceplugins.imagebrowser-1.0b6-1.lbn25.noarch

A TinyMCE plugin to provide thumbnail image browsing and a ressource library

collective.transcode.star-0.21-1.lbn25.noarch

collective.transcode.* or transcode.star for short, is a suite of modules that provide transcoding services to Plone sites. Both the naming scheme and the basic design priciples were inspired by collective.blog.star. Namely: Be modular. Not everyone wants everything your software has to offer. Be flexible. Don't assume that people want to use your software in one way. Be simplistic. If there is a simple way of doing it, do it that way. Be Ploneish. Plone already has 90% of what we need built in. Use it. It works out of the box with standard Plone Files, providing transcoding services to web friendly formats (mp4, ogv) when uploading video content. Additionally, a jpeg thumbnail is being extracted from the 5th second of the videos and a flowplayer viewlet pointing to the produced mp4 file will be displayed inside the IAboveContentBody viewlet manager when transcoding is complete. Transcode.star can be easily configured through the Plone Control Panel to work with any custom AT content type, as long as there is a File field in the schema. In the Transcode Settings panel you can enter a new line in the supported portal types, following the format customPortalType:fileFieldName where customPortalType the name of your portal_type and fileFieldName the name of the file field that you need transcoding for. Support for Dexterity content types is planned for the coming versions. For the transcoding to work you need to start the transcodedaemon instance provided in the buildout. If your transcoding needs are high, you can configure several transcode daemons in a load balanced setup. Transcode.star will select the daemon with the minimum transcoding queue length. All communication between transcode.star and transcode.daemon is encrypted using symmetric encryption by the pycrypto module so that the transcode server(s) transcode videos sent by the Plone site only, preventing abuse by third parties. Also extra care has been taken to transcode videos in private state (typical senario for a Plone site, when users upload a file) by using the same secure channel.

collective.transmogrifier-1.5.2-1.lbn25.noarch

A "transmogrifier pipeline" refers to a description of a set of pipe sections, slotted together in a set order. The stated goal is for these sections to transform data and ultimately add content to a Plone site based on this data. Sections deal with tasks such as sourcing the data (from textfiles, databases, etc.) and characterset conversion, through to determining portal type, location and workflow state. Note that a transmogrifier pipeline can be used to process any number of things, and is not specific to Plone content import. However, it's original intent is to provide a pluggable way to import legacy content.