Personal tools
Skip to content. | Skip to navigation
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.
Straightforward toolbox of field types, widgets, and validators for Archetypes.
The PloneSoftwareCenter testing harness should only be used and deployed by power users.
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.
BTreeFolder2 is a Zope product that acts like a Zope 2 OFS folder but can store many more items. When you fill a Zope folder with too many items, both Zope and your browser get overwhelmed. Zope has to load and store a large folder object, and the browser has to render large HTML tables repeatedly. Zope can store a lot of objects, but it has trouble storing a lot of objects in a single standard folder. Zope Corporation once had an extensive discussion on the subject. It was decided that we would expand standard folders to handle large numbers of objects gracefully. Unfortunately, Zope folders are used and extended in so many ways today that it would be difficult to modify standard folders in a way that would be compatible with all Zope products. So the BTreeFolder product was born. It stored all subobjects in a ZODB BTree, a structure designed to allow many items without loading them all into memory. It also rendered the contents of the folder as a simple select list rather than a table. Most browsers have no trouble rendering large select lists. But there was still one issue remaining. BTreeFolders still stored the ID of all subobjects in a single database record. If you put tens of thousands of items in a single BTreeFolder, you would still be loading and storing a multi-megabyte folder object. Zope can do this, but not quickly, and not without bloating the database. BTreeFolder2 solves this issue. It stores not only the subobjects but also the IDs of the subobjects in a BTree. It also batches the list of items in the UI, showing only 1000 items at a time. So if you write your application carefully, you can use a BTreeFolder2 to store as many items as will fit in physical storage. There are products that depend on the internal structure of the original BTreeFolder, however. So rather than risk breaking those products, the product has been renamed. You can have both products installed at the same time. If you’re developing new applications, you should use BTreeFolder2.
BastionCrypto, Zope-ZMI PGP/X509 cryptographic suite
General Ledger, Order Management, Debtor and Creditor Management, Shareholder Management, Asset Register, Forecasting, ...
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.
BlueAwstatsManagementTool is a products to manage access to the available statistics from AWStats on a Server. Added outside a plone site in the ZMI you can controll access to statistics in general. Installed Inside a plone site you have better abilities to control access to statistics on user level. There must be at least one Management Tool inside a zope instance to use BlueAwstats (and only one per folder level). The first one found by aquisition is used for the calling plone site.
The action icons tool provides a centralized registry mapping CMF "actions" (identified by their category and ID) to additional presentation metadata (display title and icon). The skins here show alternative mechanisms for using this metadata within a site template.