Modified items

All recently modified items, latest first.

solgema.fullcalendar-2.3.2-1.lbn13.noarch: This calendar allows you to display event type objects in a powerfull and fast ajax agenda. You will be also able to add, edit and more generally manage your events throught the Calendar with a strong AJAX framework. The calendar is a view you can choose on a Topic.The view is named "solgemafullcalendar_view". After that, a new object action permits you to set up the basics parameters for the calendar. The calendar is strongly linked to the Topic as the events it displays are searched by the Topic and it's criterias. In addition to the calendar, there is a small query form you can display in the bottom of the calendar to choose which event you want to display. The fields in this query form are taken from the Topic's Criterions.

solgema.ContextualContentMenu-0.2-1.lbn13.noarch: This Package gives the basics to add a content action viewlet dropdown as a javascript right click on an object. javascript will look for a link with a "contextualContentMenuEnabled" class or for a link contained in a container marked with the class : ".contextualContentMenuEnabled". The link's href must point to an object in the site.

simplon.plone.ldap-1.0-4.lbn13.noarch: Active Directory Active Directory provides an LDAP interface to its data. Using this interface Plone can use both users and groups from an Active Directory system. Writing to Active Directory is not supported. With Active Directory you can use two different properties as login name: userPrincipalName and sAMAccountName. sAMAccountName is the plain account name without any domain information and is only unique within a single domain. If your environment only uses a single AD domain this option is the best choice. For environments with multiple names the userPrincipalName attribute can be used since this includes both account name and domain information. Since Plone does not support binary user ids it is not possible to use the objectGUID attribute as user ids. Instead you can use either sAMAccountName or userPrincipalName. The same criteria for choosing a login name also apply to selecting the user id attribute. Standard LDAP LDAP directory servers are fully supported. LDAP users and groups are usable as standard Plone users and groups can be me managed normally. Creating and deleting users and groups is supported.

scipy-0.10.1-1.fc18.armv6hl: Scipy is open-source software for mathematics, science, and engineering. The core library is NumPy which provides convenient and fast N-dimensional array manipulation. The SciPy library is built to work with NumPy arrays, and provides many user-friendly and efficient numerical routines such as routines for numerical integration and optimization. Together, they run on all popular operating systems, are quick to install, and are free of charge. NumPy and SciPy are easy to use, but powerful enough to be depended upon by some of the world's leading scientists and engineers.

scipy-0.7.1-3.fc13.x86_64: Scipy is open-source software for mathematics, science, and engineering. The core library is NumPy which provides convenient and fast N-dimensional array manipulation. The SciPy library is built to work with NumPy arrays, and provides many user-friendly and efficient numerical routines such as routines for numerical integration and optimization. Together, they run on all popular operating systems, are quick to install, and are free of charge. NumPy and SciPy are easy to use, but powerful enough to be depended upon by some of the world's leading scientists and engineers.

rtf2xml-1.33-1.lbn13.x86_64: The script rtf2xml converts Microsoft RTF to XML. By default, the script outputs to a raw XML, which faitfully represents the strucutre of the original RTF document.

rtf-converter-1.1-3.lbn13.x86_64: rtf-converter is a command line RTF to HTML converter application written in C++. It removes specific font and font-size references leaving only the basic paragraph styles and bold, italic etc.

repoze.zope2-1.0.3-5.lbn13.noarch: repoze.zope2 is a decomposition of the Zope 2 appserver publication machinery (ZPublisher) into a WSGI application component. It relies on separately-distributed middleware pieces to perform some of the features previously handled by ZPublisher and other parts of Zope 2.

repoze.xmliter-0.5-2.lbn13.noarch: Wrapper for ``lxml`` trees which serializes to string upon iteration.

repoze.who-2.0-2.lbn13.noarch: ``repoze.who`` is an identification and authentication framework for arbitrary WSGI applications. It acts as WSGI middleware. ``repoze.who`` is inspired by Zope 2's Pluggable Authentication Service (PAS) (but ``repoze.who`` is not dependent on Zope in any way; it is useful for any WSGI application). It provides no facility for authorization (ensuring whether a user can or cannot perform the operation implied by the request). This is considered to be the domain of the WSGI application. It attemtps to reuse implementations from ``paste.auth`` for some of its functionality.

repoze.vhm-0.13-2.lbn13.noarch: This package provides middleware and utilities for doing virtual hosting within a WSGI/Repoze environment. It is particularly useful within a 'repoze.zope2' environment, where it may be used as an alternative to the classic "VirtualHostMonster":http://www.zope.org/Members/4am/SiteAccess2/info method of doing virtual hosting.

repoze.tm2-1.0b2-3.lbn13.noarch: Middleware which uses the ZODB transaction manager to wrap a call to its pipeline children inside a transaction.

repoze.sphinx.autointerface-0.7.0-2.lbn13.noarch: Sphinx extension: auto-generates API docs from Zope interfaces

repoze.retry-1.2-4.lbn13.noarch: WSGI Middleware which intercepts a ZODB conflict error and retries the WSGI request a configurable number of times.

repoze.lru-0.4-2.lbn13.noarch: A tiny LRU cache implementation and decorator

repoze.errorlog-0.9.1-4.lbn13.noarch: Error logging and reporting middleware

raptus.touchswipe-1.0a1-1.lbn13.noarch: Provides the jQuery TouchSwipe plugin as Plone JS resource

raptus.supersized-1.0a1-1.lbn13.noarch: Provides the supersized jQuery plugin integrated into Plone

raptus.multilanguageplone-1.1a3-1.lbn13.noarch: raptus.multilanguageplone provides a simple way to have internationalization on content objects. raptus.multilanguageplone isn't meant to be a fully fledged multilanguage tool, like LinguaPlone. Translation is done directly in the edit view of a content type and provides a widget to use google's translation api to translate the different fields. Unlike LinguaPlone raptus.multilanguageplone doesn't create an object for each translation, it stores the translation on the object itself and therefor doesn't support translation workflows and language aware object paths.


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