You are here: Home

Modified items

All recently modified items, latest first.
RPMPackage Products.BlueAwstats-2.0-9.lbn13.noarch
BlueAwstats is a front-end for the third party software AWStats log file analyzer and statistics generator. AWStats itself consists of two parts: A log file analyzer to compute raw-statistical data and a renderer for websites. BlueAwstats is using the raw statistical data and replacing the html-renderer. BlueAwstats consists of three parts: 1. python module bda.awstatsparser to parse raw-data files generated by AWStats, see http://pypi.python.org/pypi/bda.awstatsparser 2. Zope Product BlueAwstatsMangementTool defines the settings i.e. the path to the awstats-raw-data on the filesystem and constraining the sites available. 3. CMF/Plone Product BlueAwstats to be placed as a tool in the Plone-site.
RPMPackage Products.BeakerSessionDataManager-1.0b1-2.lbn13.noarch
Products.BeakerSessionDataManager is a replacement for the default Zope 2 session implementation. It uses Beaker as a backend (via collective.beaker) and adapts the Beaker session to provide the same interface as a normal Zope session. Beaker is a better alternative to the default session implementation for several reasons: * The Zope session implementation does not perform well in high-write scenarios. * Beaker provides better flexibility in where session data is actually stored. * Beaker is used and maintained outside of the Zope ecosystem.
RPMPackage Products.BastionLedger-4.6.0-6.lbn13.noarch
General Ledger, Order Management, Debtor and Creditor Management, Shareholder Management, Asset Register, Forecasting, ...
RPMPackage Products.BastionCrypto-4.2.0-1.lbn13.noarch
BastionCrypto, Zope-ZMI PGP/X509 cryptographic suite
RPMPackage Products.BastionBase-ldap-4.3.2-2.lbn13.noarch
Role management into LDAP/PAS
RPMPackage Products.BastionBase-4.3.2-2.lbn13.noarch
Wrappers to isolate ourselves from Zope source code changes with which we disagree. A set of utility functions to manage Zope installations Useful base classes (Archetypes wrappers) and tools for Plone (timezone tool)
RPMPackage Products.BastionBanking-VeriSign-doc-4.2.2-2.lbn13.noarch
VeriSign PayFlow API documentation
RPMPackage Products.BastionBanking-VeriSign-4.2.2-2.lbn13.noarch
VeriSign PayFlow API
RPMPackage Products.BastionBanking-PinPayments-4.2.2-2.lbn13.noarch
pin.net.au merchant gateway
RPMPackage Products.BastionBanking-PayPalDirect-4.2.2-2.lbn13.noarch
PayPal Name-Value-Pair Direct Payment (no hijacking/rerouting to PayPal)
RPMPackage Products.BastionBanking-PayPal-4.2.2-2.lbn13.noarch
PayPal Internet Merchant Service
RPMPackage Products.BastionBanking-ManualPayment-4.2.2-2.lbn13.noarch
Manual preparation from schedule
RPMPackage Products.BastionBanking-BarclayCard-4.2.2-2.lbn13.noarch
BarclayCard ePDQ Internet Merchant Service
RPMPackage Products.BastionBanking-4.2.2-2.lbn13.noarch
Zope Banking tools and API's, including our ZCurrency class.
RPMPackage Products.BTreeFolder2-2.13.4-2.lbn13.noarch
A BTree based implementation for Zope 2's OFS.
RPMPackage Products.AttachmentField-1.4.5-3.lbn13.noarch
An Archetype field that manages file attachments, to be used in place of a FileField. AttachmentField allows you to index and preview various kinds of documents, such as MSOffice (Word, Excel, Powerpoint), PDF and more in your Archetypes based content types. This product replaces the former ZAttachmentAttribute from Ingeniweb (see ingeniweb.sourceforge.net).
RPMPackage Products.Archetypes-1.9.6-1.lbn13.noarch
Introduction ============ Archetypes is a developers framework for rapidly developing and deploying rich, full featured content types within the context of Zope/CMF and Plone. Archetypes is based around the idea of an `Active Schema`. Rather than provide a simple description of a new data type, Archetype schemas do the actual work and heavy lifting involved in using the new type. Archetype Schemas serve as easy extension points for other developers as project specific components can be created and bound or you can choose among the rich existing set of features. Features -------- * Simple schemas with working default policy. * Power and flexibility with lowered incidental complexity. * Full automatic form generation * Unique Ids for objects * Object References/Relationships * Per Type cataloging in one or more catalogs Documentation ------------- Major resource for documentation is located at plone.org.
RPMPackage Products.ArchAddOn-devel-1.7-3.lbn13.noarch
The PloneSoftwareCenter testing harness should only be used and deployed by power users.
RPMPackage Products.ArchAddOn-1.7-3.lbn13.noarch
Straightforward toolbox of field types, widgets, and validators for Archetypes.
RPMPackage Products.AdvancedQuery-3.0.3-2.lbn13.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.