Search results

FusionChartsFree-2.2-1.lbn19.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.

FusionChartsFree-demo-2.2-1.lbn19.noarch

Demonstrations and examples for FusionChartsFree

MySQL_python-1.2.3-5.lbn19.x86_64

MySQLdb is an interface to the popular MySQL database server for Python. The design goals are: * Compliance with Python database API version 2.0 [PEP-0249] * Thread-safety * Thread-friendliness (threads will not block each other) MySQL-3.23 through 5.0 and Python-2.3 through 2.7 are currently supported. Python-3.0 will be supported in a future release.

PloneHotFixes-20210518-1.lbn25.noarch

Hot fixes for Plone - as per plone.org security mailing list

Products.ATContentTypes-3.0.0-8.lbn19.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.

Products.ATVocabularyManager-1.6.6-2.lbn19.noarch

ATVocabularyManager offers central through the Plone management of dynamic vocabularies. This product is based on Archetypes and made to work with Archetypes as well as with other Products. It is intended use is within Archetypes Fields. Using it as a vocabulary provider for CMFMetadata worked out fine too. Integration with different other products will work as well. to use a managed vocabulary simply add the term vocabulary = NamedVocabulary("myvocabulary") to the fields of your Archetypes Schema, import NamedVocabulary from this Product and create your vocabulary with id myvocabulary in 'portal_vocabularies' tool (available through Plone Site-Setup). NamedVocabulary accepts two extra arguments: empty_first_item, needs a boolean for getting an empty item on top of the list, defaults to False; custom_empty_first_item, needs a list of tuple containing a custom first item, defaults to None. ATVocabularyManager supports: simple flat key value vocabularies tree like hierachical vocabularies (see Limitations) IMS Vocabulary Definition Exchange Format (VDEX) aware vocabularies with XML Import and Export. VDEX is i18n-aware by its nature and does not need LinguaPlone! Vocabularies are pluggable types. ATVocabularyManager is prepared for extension with your special vocabulary type. ArchGenXML will help you here. Each vocabulary term needs to be an CMF aware content type. Reuse normal rich content as a vocabularies. ArchGenXML 1.4+ code-generator does full integration of ATVocabularyManager: via tagged value defined named vocabularies are registered transparently, VDEX-XML files are imported at install-time, stub vocabularies are created at install time and custom types are registered by just providing appropriate stereotypes. ATVM is Linguaplone compatible (only tested with SimpleVocabulary, and TreeVocabulary). Add a simple vocabulary with some items, install and configure Linguaplone, translate the vocabulary to the language(s) of your choice, translate every item to the language(s) of your choice. NamedVocabulary() will return the vocabulary as usual, the keys will stay the same disregarding language settings, the values will show in the currently selected language. VDEX vocabularies are not using LinguaPlone, but are i18n-aware (imo much better than everything else). You can do hierachy-aware searches on treevocabularies (for more information on this see doc/search_treevocabulary.txt) attention: curently certain changes in the term hierachy require a catalog rebuild (see Limitations).

Products.AddRemoveWidget-1.5.0-3.lbn19.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.AddThis-4.1.2-2.lbn25.noarch

Viewlet for addthis.com social networking publishing

Products.AdvancedQuery-3.0.4-1.lbn25.noarch

AdvancedQuery ============= AdvancedQuery is a Zope product aimed to overcome several limitations and bugs of ``ZCatalog``'s native search function. Like ZCatalog search, it supports elementary index searches. While ZCatalog can combine such elementary searches only by "and", AdvancedQuery allows to arbitrarily combine them by & (and), | (or) and ~ (not). Besides, it supports an extended range of elementary queries, such as matching, indexed queries, literal result sets. Finally, it supports incremental filtering. AdvancedQuery also extends the sorting capabilities of ZCatalog. ZCatalog supports efficient index based sorting on one level. AdavancedQuery supports sorting on arbitrary levels of field indexes. Furthermore, sorting is performed incrementally -- only as far as the result is accessed. This can drastically speed up sorting. Finally, AdvancedQuery can sort based on query based ranks. Unlike ZCatalog which simply ignores hits for which it does not have a sort value, AdvancedQuery sorts such hits at the end of the respective list. AdvancedQuery works best when used together with Products.ManagableIndex and dm.incrementalsearch. Some of its features depend on these products, e.g. matching and incremental filtering. Furthermore, these additional components can speed up queries by several orders of magnitude. For more information, see AdvancedQuery.html in the doc subfolder.

Products.ArchAddOn-1.7-3.lbn19.noarch

Straightforward toolbox of field types, widgets, and validators for Archetypes.