Search results

Products.MasterSelectWidget-0.4.5-1.lbn25.noarch

Master Select Widget is an Archetypes widget which looks and feels like a normal select dropdown; however, any time an item is selected it triggers javascript events which control the behavior of other fields in the schema. It can hide other fields using CSS, disable other widgets, and alter the vocabulary of other fields using XMLHttpRequest calls to a methods that produce AT DisplayLists (the subordinate fields must use Select, MultiSelect, or MasterSelect widgets). You may have many of these 'master' widgets on a page and each can control multiple 'slave' fields. The 'slave' fields themselves can use 'master' widgets controlling their own 'slaves'. Currently a 'master' can only control one aspect (vocabulary, visibility. etc.) for each of its slaves, but multiple 'masters' can control the same 'slave'.

Products.MimetypesRegistry-2.1.1-1.lbn25.noarch

* mimetypes_registry (the mimetypes tool) : handle mime types information

Products.NuPlone-1.0b3-2.lbn19.noarch

NuPlone is a new theme for Plone 3.0 made by Cornelis Kolbach Visual design, design studies, initial CSS implementation. Alexander Limi Plone integration, additional CSS work, usability guidance.

Products.OFSP-2.13.2-2.lbn25.noarch

General Zope 2 help screens.

Products.OFolder-2.0.1-2.lbn25.noarch

Ordered folder for Zope

Products.OpenXml-1.1.0-2.lbn19.noarch

OpenXml provides Plone resources for OpenXml documents : * A set of icons for Office 2007 documents * A set of PortalTransforms plugins suitable to OpenXml documents indexing

Products.OrderedFolder-0.4.0-10.lbn25.noarch

Ordered Folders actually patches the ObjectManager to become the OrderedObjectManager and then simply provides a Base Class for the OrderedFolder. Ordered Folders allow your objects inside the Folder to have a specific order. This is especially useful, if you want to display the object in a certain order that is not dependent on any variable. Let's take Martijn Faassen's product Formulator for example, where the single Form Fields need to be in a certain, user-defined order. He could simply use the OrderedFolder as a base class for his form and receives instantanously order support. At iuveno AG we needed this product to implement similar functionality for some new parts of the Kontentor (which will be published soon).

Products.PasswordResetTool-2.0.19-1.lbn25.noarch

The Password Reset Tool hooks into the standard mechanisms for password mailing provided by the CMF in the Registration Tool and certain skins and replaces this with a facility for resetting passwords with email authentication. This is useful not only to keep passwords out of cleartext email and is absolutely necessary if you choose to encrypt your passwords (and you should.) See the INSTALL.txt file for details on installation, and the LICENSE.txt file for the license this Product is under. Note, of course, that you must have a working MailHost to send email! The Password Reset Sequence from the User's Point of View The user will observe the following steps. * User forgets a password and * clicks "Forgot your password?", which * goes to a form that asks for a username. User fills this in and clicks a button to proceed, which * goes to a form explaining that an email has been sent. * User receives an email with a URL containing a random, unguessable key and opens it in a web browser. * This is a form that asks for username and password, which goes to * a form reporting success (or failure, if expired or illegitimate.)

Products.PlacelessTranslationService-2.0.7-1.lbn25.noarch

What is PlacelessTranslationService? ------------------------------------ PTS is a way of internationalizing (i18n'ing) and localizing (l10n'ing) software for Zope 2. It's based on the files supported by the GNU gettext set of utilities. A good source of information and background reading is the gettext documentation: http://www.gnu.org/software/gettext/manual/ Using PlacelessTranslationService --------------------------------- PTS is used in the following steps: 1. i18n your software 2. Prepare a translation template 3. Prepare translations of the template 4. Install translations Each of these is explained below. 1. Internationalizing Your Software A good overview of this can be found at: http://www.upfrontsystems.co.za/Members/jean/mysite-i18n 2. Preparing a Translation Template A translation template is an empty Portable Object file as defined by the gettext standard with a special header block. The PO format is described in detail here: http://www.gnu.org/software/gettext/manual/html_node/gettext_9.html#SEC9 The header block is fairly self explanatory and can be seen in the sample.pot file included in this directory. All phrases in capitals, the language code, language name and (optionally) the content type and preferred encodings should be replaced with their correct values. There are several ways to prepare a PO template: -- By hand: This can be done by copying the blank.pot included in this directory, replacing the sample values as described above and and then manually adding msgid and empty msgstr pairs for each of the msgid's used in your software. -- Using i18ndude: i18ndude is a tool that is useful when all your software is in the form of ZPT's that are stored in files on the filesystem. It can be downloaded from: http://plone.org/products/i18ndude 3. Prepare Translations of the Template Preferably, find a translation company that can handle the gettext standards and send them your .pot file. They should send back .po files for the languages you require. If you're doing it yourself, copy the .pot file to a file on the name of the language you're translating to and with a .po extension. Then go through that file and fill in the msgstr sections. Finally, update all the metadata fields at the top of the file so they are correct for the translation you have just completed. At this point, you should have a .pot file and a collection of .po files. 4. Install Translations PTS will look in folders called 'i18n' for .po files to use as translations. These 'i18n' folders will be searched if they are in the INSTANCE_HOME or in the directories of any of the Products you have installed. Copy your .po files to a 'i18n' folder of your choice in one of these locations. Once that's done, restart Zope.

Products.PloneArticle-4.2.0-3.lbn19.noarch

PloneArticle : A Plone Document that can incorporate images and attachments and that allows you to choose from different layout models. Behaves mostly like the standard Plone Document type. When you add a Plone Article, you can enter the name, title, description and text information. When you look at the Plone Article, the images will appear in the right column as a thumbnail and optionally with their title. When you click on the thumbnail, a popup window will appear with the image at its actual size. Attachments will be listed below the article for download in rows of three. You will notice two tabs that don't exist on the standard Plone Document: images and attachments. The Images Tab: This interface shows the Images that you have uploaded to the article, and allows you to add new images as well as deleting them. Images can have an optional title. The position of images as they will appear in the right column of the Plone Article View can be changed with up and down arrows that allow you to individually move images up or down one step. Thanks to the ImageTag hotfix, Images are shown as a thumbnail on all pages, and only when you click on them, a popup window will appear with the original size of the image. Attachments Tab: This interface shows the Attachments that you have uploaded to the article, and allows you to add new attachments as well as deleting them. If no title is given, the name of the uploaded file is taken in its place. Links Tab: This interface shows the Links that you have added to the article, and allows you to add new links as well as deleting them. The Models Tab: Here you can choose from the stock layout models that come with PloneArticle, and also the models that you have created somewhere in the skins path.