Modified items

All recently modified items, latest first.

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.

ftw.publisher.core-2.3.3-1.lbn13.noarch: The ftw.publisher packages provide tools for publishing plone contents from one instance to another. This package provides shared tools and utils used by ftw.publisher.sender and ftw.publisher.receiver.

ftw.dictstorage-1.2-3.lbn13.noarch: This package provides a layer for storing key / value paires. The storage can be configured dinamically by providing a IConfig adapter of the context on which the dict storage is used.

ftw.dashboard.portlets.postit-1.3.4-1.lbn13.noarch: How to use ftw.dashboard.postit ================================== 1.) Install the ftw.dashboard.portlets.postit product with the portal_setup tool. 2.) add a postit portlet to your dashboard 3.) create notes ... Description: ============ the postit portlet is a usefull plone 3 portlet for your dashboard. The adding and removing function are ajax implemented (jquery).

ftw.dashboard.dragndrop-1.5.3-1.lbn13.noarch: ftw.dashboard.dragndrop adds persistent dragndrop functionality to the standard plone dashboard. http://onegov.ch/approved.png/image Certified: 01/2013 Features: Drag'n'drop: All dashboard portlets can be moved with drag'n'drop from column to column and reordered in the column. Folding: Dashboard porlets are foldable. Edit portlet icon: Dashboard portlets have an icon on the top (pencil) for editing the portlet. close/remove portlet: Dashboard portlets have an icon on the top (cross) for removing the portlet from the dashboard.

ftw.dashboard-1.3.4-1.lbn13.noarch: ftw.dashboard module

ftw.bridge.proxy-1.1.1-4.lbn13.noarch: ftw.bridge.proxy is a small pyramid based web application for proxying requests between multiple plone instances. It's purpose is to isolate the plone instances by routing through this proxy. This allows to easily move plone instances to other servers. Maintenance mode Each configured client (plone site) can be switched into maintenance mode on the bridge. When maintenance mode is enabled, the bridge answers every request to this client with a HTTP 503 (Service Unavailable). The maintenance mode can be enabled in the manage view of the bridge (/manage).

ftw.bridge.client-1.0.7-1.lbn13.noarch: The ftw.bridge tools are used for communication between several Plone instances. It is also possible to cummuncate with other web services. Requests between web services are proxied through the ftw.bridge.proxy. This makes it possible to move or reconfigure certain dependent webservices (clients) only by reconfiguring the proxy. The clients do not know where other target clients are located - they only communicate with the proxy directly, which forwards the requests to the target client. Features ftw.bridge.client integrates ftw.bridge support into Plone. It provides tools and utilities for communication and authentication. * Authentication: A PAS plugin authenticates requests and logs the user in on the target client without transmitting his password. Only requests from the configured ftw.bridge.proxy are authenticated. * Requests: The IBridgeRequest utility is used for making requesting other clients. It is also able to make remote catalog queries and transmitting the result brains to the sources by using fake brains. * Brain transport: By using a BrainRepresentation it is possible to get brains from a remote client. A BrainSerializer utility serializes and deserializes all brain metadata so that they can be used on the source client. * Watcher portlet: A recently-modified portlet can be used for generic listing a list of recently modified objects on the remote client but it is also possible to list other links. There is a browser view @@watch which creates a recently-modified portlet on the remote client dashboard. The watcher portlet loads its data asynchronously using javascript for not blocking while loading the dashboard. * Favorites: A browser view @@remote-add-favorite adds the context to the favorites on the remote client dashboard.

five.pt-2.2.1-2.lbn13.noarch: This package brings the Chameleon template engine to the Zope 2 platform. Five is supported. It works using monkey-patching onto the existing API (specifically, the TALInterpreter and PageTemplate classes). In simple terms, what the patching does is to replace the TAL interpreter class and make sure that the so-called "cooking" routine uses the Chameleon parser and compiler instead of the zope.* reference implementation.

« Previous 20 items Next 20 items » 1 ... 2400 2401 2402 2403 2404 2405 2406 ... 2448


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

Sections

Modified items