You are here: Home

Modified items

All recently modified items, latest first.
RPMPackage Products.fatsyndication-1.0.1-7.lbn13.noarch
Five/AT layer for syndication
RPMPackage Products.contentmigration-2.1.5-1.lbn13.noarch
A generic content migration framework for Plone.
RPMPackage Products.basesyndication-1.0.0-2.lbn13.noarch
atom,rss etc feeds
RPMPackage Products.Zpydoc-4.0.5-1.lbn13.noarch
Zpydoc reads and formats python docstrings and much other useful information to dynamically produce automatic documentation for python, Zope, and Plone modules. As of Verion 2.x.x, it supports Plone skins.
RPMPackage Products.ZopeVersionControl-1.1.3-2.lbn13.noarch
 
RPMPackage Products.Zelenium-1.0.3-2.lbn13.noarch
This product allows developers to create TTW Selenium test suites inside their Zope instance, in order to do browser-based functional testing of their site. You can add a 'Zuite' object at any location within your Zope site. It behaves as a standard ordered folder, with a couple of differences: - It's 'index_html' is the "TestRunner.html" view familiar from Selenium. - It derives the test suite (in the upper left corner iframe) from all OFS.Image.File objects whose names start with 'test'. You can use the OrderedFolder support to modify the order in which the test case files are run. - It provides a "Zip" action, which allows you to export the test suite, all test cases, and the supporting Selenium Javascript / CSS files as a single, self-contained zipfile. Adding Tests Tests are just 'File' instances whose names begin with 'test'. They should have a content type of 'text/html', and should contain a table which defines the steps which make up the test case. See http://selenium.thoughtworks.com/testrunner.html for documentation on the table structure and the Selenese language. Using Additional Metatypes as Test Cases On the "Properties" tab of your test suite, you can add / modify the list of meta_types which the suite will allow as test cases. Adding "Script (Python)", for instance, allows you to define test cases in PythonScripts. Nesting Test Suites Each test suite automatically includes the test cases of any suite it contains. You can take advantage of this feature to organize your test cases in a hierarchy, running them in separate segments, or all at once. Including Tests from the Filesystem Test suites now have a property, 'filesystem_path'; if set, the suite will recursively load testcases from files in / under the directory pointed to by that path. The list of files to be included is computed via the following rules: - If the directory contains a file, '.objects', it is presumed to contain a list of files to be included, one per line; only those files / subdirectories (if present) will be included. In this case, the test cases will be presented in the order indicated in the file, followed by any test cases from subdirectories. - Otherwise, if the suite's property, 'filename_glob' is non-empty, it will be expanded (via Python's 'glob.glob') to compute the list of filenames. The test cases will be presented in alphabetical order, followed by any test cases from subdirectories. - Otherwise, any file will be considered a testcase. The test cases will be presented in alphabetical order, followed by any test cases from subdirectories. Capturing Results from the Test Run Selenium has a feature which allows the testrunner to upload result data from an automated test run to the server. Invoke the test suite from your browser as usual, but append the query string '?auto=1', to the URL, e.g.:: http://localhost:8080/test_suite?auto=1 Selenium will run all test cases, and then upload its result data to the 'postResults' method of your suite. (Note that you no longer need the 'postResults' PythonScript in the root of your site, because the latest version of Selenium posts to that name relative to the test suite).
RPMPackage Products.ZSyncer-1.0.3-7.lbn13.noarch
ZSyncer is a project that allows live zope objects to be synchronized from one Zope to another without doing the tedious export / transfer / import dance. It is very easy to use. ZSyncer also allows you to see at a glance which objects are out-of-sync. ZSyncer also allows you to view a diff against the destination object, for many types of objects.
RPMPackage Products.ZScheduler-threaded-4.2.3-2.lbn13.noarch
Internal zope scheduling via a dedicated timer thread. Each event is run in this thread.
RPMPackage Products.ZScheduler-multithreaded-4.2.3-2.lbn13.noarch
Internal zope scheduling via a dedicated timer thread with individual worker threads to run each event
RPMPackage Products.ZScheduler-crontab-4.2.3-2.lbn13.noarch
External zope scheduling via crontab
RPMPackage Products.ZScheduler-4.2.3-2.lbn13.noarch
Zope Event Scheduler
RPMPackage Products.ZSQLMethods-2.13.4-3.lbn13.noarch
SQL method support for Zope 2.
RPMPackage Products.ZPsycopgDA-2.0.8-2.lbn13.noarch
PostgreSQL data connector for Zope
RPMPackage Products.ZChecker-20070819-4.lbn13.noarch
Check Zope Page Templates for correctness and XHTML-compliance
RPMPackage Products.ZCatalog-3.0.1-1.lbn13.noarch
Zope 2's indexing and search solution.
RPMPackage Products.ZCTextIndex-2.13.5-1.lbn13.x86_64
This distribution contains a full text indexing facility for Zope 2 and more specifically for Products.ZCatalog.
RPMPackage Products.ZAUTZ-0.0.1-1.lbn13.noarch
AU Timezones for Zope Monkey Patch to Zope DateTime to correctly use Australian Timezones that clash with US timezones.
RPMPackage Products.UserAndGroupSelectionWidget-3.0b5-1.lbn13.noarch
UserAndGroupSelectionWidget is an Archetypes widget to search and select users and/or groups from a huge base of users. It uses a modernized, fast code-base and is tested with hundreds of groups and thousands of users. It is configureable to select only groups, only users, both or only user of a distinct group. Using translation-adaptors you can use generic group names and genric group filters. The translation adaptor will translate it into real group ids or group id filters.
RPMPackage Products.TinyMCE-1.3.6-1.lbn13.noarch
Adds support for TinyMCE, a platform independent web based Javascript HTML WYSIWYG editor, to Plone.
RPMPackage Products.TextIndexNG-3.4.5.1-4.lbn13.noarch
Features: * DocumentConverters * StemmerSupport for 13 languages * SimilaritySearch for english text (based on the Levenshtein distance) * NearSearch, * PluggableParsers * extended StopWords support * full integration in ZCatalog * TestFunctionality through ZMI * ExtensibleArchitecture * being MoreEfficient than the current !TextIndex * full globbing support (wildcard search) * NormalizationSupport (e.g. reducing accented characters to their base form) * full UnicodeAwareness * Relevance ranking of search results added. Searches are now ranked using an extended cosine measure. The cosine measure is based on a vector model and calculates the document "score" based on the frequency of the query terms inside the document result set. * Much faster phrase/near search: the old implementation of TextIndexNG had to perform a very expensive job at query time when phrase/near search was performed. Re-using the !WidCode module of !ZCTextIndex made this operation less expensive. * Left-truncation added: TextIndexNG can be configured creation-time time to support left-truncation (means you can search for "*suffix") Left-truncation is an option because this feature requires a second reverted index inside the lexicion and much more memory! * optional auto-expansion support: This optional feature allows you to get better search results when some of the query terms could not be found. The index expands a query term "foo" to "foo*" if there was no hit for "foo". This expansion is currently global for the index. This feature will be available on a per-query basis in a later version. (Auto-expansion will be extended in a later version to search for similiar terms) * improved HTML converter: now using Chris Withers "Strip-o-Gram" module instead of the Strip-Tag-Parser * added converter for text/sgml * Similarity search (soundex, metaphone, doublemetaphone) dropped and replace with a more general approach and language indepedant approach using the Levenshtein distance. * range searches like "Fi..Foo" * substring searches "substring"