Modified items

All recently modified items, latest first.

Products.AddThis-4.1.1-1.lbn13.noarch: Viewlet for addthis.com social networking publishing

Products.AddRemoveWidget-1.5.0-3.lbn13.noarch: This is a replacement for KeywordWidget which permits you to add items from a vocabulary (and optionally new items) using a pair of selection boxes with "add" and "remove" buttons to transfer items between them. It overlaps in functionality with InAndOutWidget, but does not suffer from InAndOut's requirement for all items in the "target" list to be selection upon form submission. I believe InAndOut does not allow textual items to be added by the user, though it does support adding of referenced objects, which AddRemove does not. You are advised to test both to find out which one is more suitable for your needs. Please see the docstring in AddRemoveWidget.py for a list of options you may pass to the widget to configure it. You can also use the widget standalone, by defining a couple of variables (notably fieldName and vocabulary) and include the macro add_remove_box from widget_addremove.pt. See the comment in that file for details. Also included is a ComboBoxWidget - it can be seen as supporting the same use case, when only one item may be selected. It presents a selection box from which to select a value, and a text box to enter an "other" value if none of the items in the list are sufficient. Again, see the docstring in ComboBoxWidget.py, and the comment in widget_combobox.pt for details on how to use it within and outside Archetypes.

Products.ATReferenceBrowserWidget-3.0-1.lbn13.noarch: Introduction ============ ATReferenceBrowserWidget is an add-on to Archtetypes. It adds a new reference widget that allows you to search or browse the portal when creating references. This new widget inherits from the standard reference widget so you can use all it's properties. When you use this widget, there are two buttons presented for each widget. One that opens a popup-window that let's you do the search/browsing and one that let's you clear the reference or selected references (will be in effect after the form's Save). The popop window basically consists of two parts. The top half is a search form and the bottom half is the browser/search results part. Both parts can be turned off or on using the widget's properties. The search part has additional configuration in the widget (see properties below). Properties ---------- The popup window can be configured using the following widget properties: * default_search_index: when a user searches in the popup, this index is used by default * show_indexes: in the popup, when set to True, a drop-down list is shown with the index to be used for searching. If set to False, default_search_index will be used. * size: in case of single-select widget, the default is set to 30. In case of multi-select, default is 8. * available_indexes: optional dictionary that lists all the indexes that can be used for searching. Format: {'<catalog index>':'<friendly name'>, ... } The friendly name is what the end-users sees to make the indexes more sensible for him. If you do not use this property then all the indexes will be shown (I think nobody should allow this to happen!). * allow_search: shows the search section in the popup * allow_sorting: allows you change the order of referenced objects (requires multiValued=1) * allow_browse: shows the browse section in the popup * startup_directory: directory where the popup opens. Optional. When omitted, the current folder is used or in the case where a property refwidget_startupdirectories under site_properties is found it is searched for a startup_directory. Property is a lines field having the following format:: path1:path2 path1 is the path where all widgets being under it set startup_directory to path2 if no startup_directory is set. * startup_directory_method: the name of a method or variable that, if available at the instance, will be used to obtain the path of the startup directory. If present, 'startup_directory' will be ignored. * restrict_browsing_to_startup_directory: allows you to restrict the breadcrumbs ('allow_browse' property) to contents inside the 'startup_directory' only. So you are not able to walk up in the hierarchy. (default: 0 = disabled) * image_portal_types: specify a list of image portal_types. Instances of these portal types are being previewed within the popup widget * image_method: specifies the name of a method that is added to the image URL to preview the image in a particular resolution (e.g. 'mini' for thumbnails) * show_review_state: allows you to display the workflow state for objects (off by default) * show_path: display the relative path (relative to the portal object) of referenced objects * only_for_review_states: items are only referencable if their workflow state matches the ones a specified (default: None = no filtering by workflow state) * history_length: enable a history feature that show the paths of the last N visited folders (default : 0 = no history) * force_close_on_insert: closes the popup when the user choses insert. This overrides the behavior in multiselect mode. * base_query: defines query terms that will apply to all searches, mainly useful to create specific restrictions when allow_browse=0. Can be either a dictonary with query parameters, or the name of a method or callable available in cotext that will return such a dictionary. This add-on comes with an example content type that uses this widget. You can enable the installation of the type by uncommenting the appropriate line in Install.py under Extension. See ATReferenceBrowserDemo.py. Design notes ------------ Both the templates (widget and popup) are prototypes. There are still some inline styles, especially in the popup because I didn't want to tweak with plone's css stuff and I didn't want to do hacking and tricking to incorporate a stylesheet myself.So, that's still a point of interest. Furthermore I made some design decisions. Right now, in the popup window, all objects are shown (when browsing) and objects that may be referenced to are bold and the other objects are greyed out. I chose to show the non-referenceable objects too because they may be an important part of the context that help the user search for the desired objects to browse to. Another thing that I chose for is that in case of a multi-value widget, the popup remains open so that you can continue to add references without having to reopen the popup over and over again. Problem is that you have to close the window yourself. This may change if it turns out to be an annoyance. A thing that is more related to forms in general is that the items in the multiselect listbox need to be selected before Save is clicked otherwise only the selected items are submitted. That kinda sucks usability-wise because now the user basically has to make two selections: first by choosing the items in the popup and secondly by selecting them again in the listbox. Right now I made it so that the items are selected by default but if the user starts clicking in the list, then there might be an issue. Btw, the inandout widget has the same problem. Best would be to select all the items in a script just before the form is submitted so that the complete list is submitted. But that requires changes in the base_edit form I think. But it's something to think about since there are now already two widgets that needs to be prepared like this (inandout and this one, haven't looked at picklist though, could have the same problem). Anyway, have fun with it and if you have suggestions please let me know. If you see problems, please fix them when you can.

Products.ATContentTypes-2.1.14-1.lbn13.noarch: AT Content Types ================ Installation ------------ Please read INSTALL.txt for a list of requirements before installing this product. ATContentTypes requires new versions of Python, Zope, Plone and Archetypes. Make sure you've updated all products. Reporting bugs / feature requests --------------------------------- Please use the Plone bug tracker at http://dev.plone.org/plone and use the Content Types component! Comparing CMF types with ATContentTypes --------------------------------------- This is a very rough and short list of differences between the old CMF types and the new ATContentTypes types. * Archetypes: All types are written with Archetypes and have all features default Archetypes based types have like: - autogenerated edit forms based on the schema - referenceable - Easily enhanceable by subclassing or adding fields to the schema - Transformations like restructured text, python source code highlighting, pdf to html, office to html and many more. - plugable validation of fields * Clean and documented API. * Translateable using LinguaPlone. * Dynamic Views: All types are using the new dynamic view FTI that allows you to choose the view template per instance. You can configure the templates in the portal_types tool. This features is used to turn an ordinary folder into a photo album by simple switching to a different view. * Permissions per type and feature: Every type has its own add permission and all features like template mixin have their own modify permission, too. * Numerous small adjustments and enhancements to all types for example: - Images can be rotated through the web and have exif informations - News Items have an image plus caption - Events have a body text - Documents have a history tab to show the last changes as an unified diff view using the ZODB history.

Pound-2.6-3.fc18.armv6hl: The Pound program is a reverse proxy, load balancer and HTTPS front-end for Web server(s). Pound was developed to enable distributing the load among several Web-servers and to allow for a convenient SSL wrapper for those Web servers that do not offer it natively. Pound is distributed under the GPL - no warranty, it's free to use, copy and give away

Pound-2.5-1.fc13.x86_64: The Pound program is a reverse proxy, load balancer and HTTPS front-end for Web server(s). Pound was developed to enable distributing the load among several Web-servers and to allow for a convenient SSL wrapper for those Web servers that do not offer it natively. Pound is distributed under the GPL - no warranty, it's free to use, copy and give away

PloneHotFixes-20130618-3.lbn13.noarch: Hot fixes for Plone - as per plone.org security mailing list

FusionChartsFree-demo-2.2-1.lbn13.noarch: Demonstrations and examples for FusionChartsFree

FusionChartsFree-2.2-1.lbn13.noarch: FusionCharts Free is a flash charting component that can be used to render data-driven & animated charts for your web applications and presentations. It is a cross-browser and cross-platform solution that can be used with PHP, ASP, JSP, ASP.NET, ColdFusion, Ruby on Rails, simple HTML pages or even PowerPoint Presentations to deliver interactive and powerful flash charts. You do NOT need to know anything about Flash to use FusionCharts. All you need to know is the language you're programming in.

gomobile.supporter-0.9.3-4.lbn13.noarch: Add mobile support for various Plone add on products

gomobile.mobile-1.0.5-2.lbn13.noarch: gomobile.mobile packge provides core mobilization functionality for Plone * Mobile theme layering * Mobile settings in the site setup * Image resizing * Mobile analytics and tracking * Mobile simulator * Discriminating web and mobile site requests * Managing mobile domain names * Redirecting and mobile switching links between web and mobile

gomobile.imageinfo-0.9.3-2.lbn13.noarch: Extract and manipulate different Zope image objects

gomobile.convergence-1.0.2-2.lbn13.noarch: Multichannel content discrimination and overrides for Plone CMS

geopy-0.99-1.lbn13.noarch: geopy is a Python 2 and 3 client for several popular geocoding web services. geopy makes it easy for Python developers to locate the coordinates of addresses, cities, countries, and landmarks across the globe using third-party geocoders and other data sources. geopy includes geocoder classes for the ESRI ArcGIS, OpenStreetMap Nominatim, Google Geocoding API (V3), Yahoo! BOSS, geocoder.us, GeocodeFarm, and Bing Maps API geocoder services, as well as several other. The various geocoder classes are located in geopy.geocoders.

funnelweb-1.1.1-2.lbn13.noarch: Funnelweb is also very flexible as it uses a modular collective.transmogrifier framework underneath which advanced users can use if they they need further steps added to their conversion process. The work performed by the funnelweb script can be broken down into four sections: 1. Crawling the site including caching locally so subsequent crawls are quicker and filtering out unwanted content 2. Remove boilerplate/templates (automatically or via rules) so just content remains 3. Analysing the site structure to improve the content quality including working out titles, default views, types of objects to create, what to show in navigation etc 4. Uploading to the CMS such as Plone, or saving cleaned HTML to local directory FunnelWeb now has two modes of operation: 1. Within Plone itself via the mr.migrator plugin. see mr.migrator for how to install. 2. A command line script which can be installed via zc.buildout. Content is uploaded into Plone via it's web services API.

ftw.usermanagement-1.9-1.lbn13.noarch: This package allows users to easily manage users and groups through a new view without having plone's manage portal permission. This is useful when the person who manages users and groups should have full manager access to the site. If the user has the permission "Manage users", a new action is displayed in the user menu, giving him the ability to list and modify users and groups. Features -------- - Manage users - List users - Assign users to groups - Add users - Delete users - Reset password of a user and send a notification - Manage groups - List groups - Add groups - Delete groups

ftw.table-1.12.4-1.lbn13.noarch: The ftw.table package provides a table generator utility, which generates a html table out of a list of almost anything. The Javascript, which will be registered, contains an extensible jQuery plugin. Using the optional extJS addon enables features such as grouping, sorting, filtering drag'n'drop ordering, checkboxes, etc.

ftw.tabbedview-3.3.8-1.lbn13.noarch: Introduction ============ This package provides a generic view with multiple tabs for plone. It provides a generic base tab for listing contents in a table, based on `ftw.table`_. Features ======== - Generic tabbed view - Tabs are registered through FTI actions - Base view for listing tabs - Listing tabs are filterable - Perform configurable actions on listed items - `ftw.table`_'s `Ext JS`_ support works also in listing tables - Fallback tables - Drag'n drop multiple file upload functionality (using quickupload plugin)

ftw.publisher.sender-2.2.0-1.lbn13.noarch: Introduction The ftw.publisher packages provide tools for publishing plone contents from one instance to another. By providing a simple mechanism to invoke the publishing, it's possible to set up the publisher in a variety of ways, such as workflow bound, manually invoked or automated publication. The ftw.publisher package library also provides a variety of surveillance and analysis tools for making maintenance confortable. Staging The ftw.publisher is meant to be used in a environment where there are two seperate plone-sites which do not share their database. The editors work on a editorial site and the contents are published to a public site when they are ready. Setting up such an environment with ftw.publisher let you have a powerful staging solution with completly isolated instances. Network security Using an environment with two isolated installations makes it possible to protect the editorial site with firewalls or to put it even in a private company network. This way the editorial site is completly protected from the internet, which is in some use cases mandatory for protecting other - unpublished - contents (for example when publishing the internet contents from the intranet). Component support * Archetypes objects * Standard Archetypes field types * Topics: criterias are published automatically when topic is published * Backreferences - references are added automatically as soon both objects are published * Additional interfaces added on /manage_interfaces or by other products * Contextual portlets * Properties With the publisher adapter structure it is as easy as creating another adapter to support other components. For instance annotations are not supported by design, because you may not want to publish all annotations but only certain ones. Therefore it is easyer to implement custom adapters for those annotations which need to be published.

ftw.publisher.receiver-2.0.2-1.lbn13.noarch: The ftw.publisher packages provide tools for publishing plone contents from one instance to another. This package should be installed on the receiver instance. It provides tools for unserializing publishing requests and creating, updating or deleting objects.

« Previous 20 items Next 20 items » 1 ... 2311 2312 2313 2314 2315 2316 2317 ... 2359


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

Sections

Modified items