Modified items

All recently modified items, latest first.

Products.ArchAddOn-1.7-3.lbn25.noarch: Straightforward toolbox of field types, widgets, and validators for Archetypes.

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.AddThis-4.1.2-2.lbn25.noarch: Viewlet for addthis.com social networking publishing

Products.ATVocabularyManager-1.6.6-2.lbn25.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.ATContentTypes-3.0.0-8.lbn25.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.

PloneHotFixes-20210518-1.lbn25.noarch: Hot fixes for Plone - as per plone.org security mailing list

python2-ply-3.11-6.lbn25.noarch: PLY is a straightforward lex/yacc implementation. Here is a list of its essential features: * It is implemented entirely in Python. * It uses LR-parsing which is reasonably efficient and well suited for larger grammars. * PLY provides most of the standard lex/yacc features including support for empty productions, precedence rules, error recovery, and support for ambiguous grammars. * PLY is straightforward to use and provides very extensive error checking. * PLY doesn't try to do anything more or less than provide the basic lex/yacc functionality. In other words, it's not a large parsing framework or a component of some larger system. Python 2 version.

kss.core-1.6.5-2.lbn25.noarch: KSS is an Ajax framework that allows UI development without writing any Javascript. It uses style sheets with CSS-compliant syntax to declare and bind dynamic behaviors in the browser. The engine supports a set of generic DOM-like commands; they are computed on the server and sent back to manipulate the HTML page. What is KSS? ************ KSS is an AJAX framework. KSS has both a client-side Javascript library and server-side support. The client-side Javascript library needs to be included in your page. It fetches Kinetic style sheets from the server, parses them and binds a set of action to browser events and/or page elements. It is clean Javascript code that can peacefully coexist with other clean Javascript librarys like JQuery or ExtJS. It is about 100k in production mode. You can integrate your own Javascript code by using its extension mechanism through plugins. Server-side code is currently available for Zope (2 and 3, which includes Plone). The kss.base egg (which is currently in alpha) brings server-side support to other pythonic platforms, such as: * pylons * django * grok The Javascript client-side code can be used independently of existing server-side support. In other words, it is usable on platforms where we have not built server-side support like PHP, Ruby or Java. (If you have interest in porting KSS to the server environment you use and need help, please contact us !)

kss-1.6.5-2.lbn25.noarch: kss python module

python2-pyparsing-2.4.7-1.lbn25.noarch: pyparsing is a module that can be used to easily and directly configure syntax definitions for any number of text parsing applications.

plonetheme.diazo_sunburst-0.1.2-1.lbn25.noarch: This is Plone 4’s default theme “Sunburst” reimplemented with Diazo.

plonetheme.bootstrap-2.0-1.lbn25.noarch: plonetheme.bootstrap integrates Twitter Bootstrap CSS/JS framework into Plone. You can checkout the framework at http://twitter.github.com/bootstrap It overrides some templates and uses javascript to transform some markup in order for it to work correctly. It's not perfect, but it's close. This product is based in Twitter Bootstrap version 2.3.x. This product adds both the basic CSS file and also the Responsive one to have a mobile-enabled site from the start. The generated markup is based on 'fluid CSS' and it contains a 12 column grid. The basic HTML markup is a mix of plonetheme.sunburst and Twitter Bootstrap and it uses the same approach of constructing the columns as Sunburst Theme: a simple view that returns the classes needed to have the correct column widths. If you want to change those widths, just override the view following the common Plone overriding patterns. This product is intended to be used in two scenarios: As a theme from Plone As a base theme to build Plone themes for your site following 'old practices' Some designers prefer to work following the old best-practices instead of using the Diazo-way-of-theming, this product is for them. You can create a theme package (check templer skeleton generator), and base your theme on this one.

plonetheme.barceloneta-1.6.21-1.lbn25.noarch: Barceloneta is the name of the Plone 5 default theme. It's named after the Barcelona beach and neighbourhood. Barceloneta is a Diazo theme made from scratch using modern frontend technologies. It's responsive and spans throught all the Plone UI including the CMS backend part. It's based on Bootstrap 3, but it's not dependent of it in any way. Although it reuses some of the structure and good practices of the original Bootstrap, it has its own personality and is fully adapted to Plone. Structure Barceloneta uses LESS as a pre-processor to generate the resultant stylesheet. The LESS resources live in the plonetheme.barceloneta egg in the plonetheme/barceloneta/theme/less directory: plonetheme/barceloneta/theme/less ├── accessibility.plone.less ├── alerts.plone.less ├── barceloneta-compiled.css ├── barceloneta-compiled.css.map ├── barceloneta.css ├── barceloneta.plone.export.less ├── barceloneta.plone.less ├── barceloneta.plone.local.less ├── behaviors.plone.less ├── breadcrumbs.plone.less ├── buttons.plone.less ├── code.plone.less ├── contents.plone.less ├── controlpanels.plone.less ├── deco.plone.less ├── discussion.plone.less ├── dropzone.plone.less ├── event.plone.less ├── fonts.plone.less ├── footer.plone.less ├── forms.plone.less ├── formtabbing.plone.less ├── grid.plone.less ├── header.plone.less ├── image.plone.less ├── loginform.plone.less ├── main.plone.less ├── mixin.borderradius.plone.less ├── mixin.buttons.plone.less ├── mixin.clearfix.plone.less ├── mixin.forms.plone.less ├── mixin.grid.plone.less ├── mixin.gridframework.plone.less ├── mixin.images.plone.less ├── mixin.prefixes.plone.less ├── mixin.tabfocus.plone.less ├── modal.plone.less ├── normalize.plone.less ├── pagination.plone.less ├── pickadate.plone.less ├── plone-toolbarlogo.svg ├── portlets.plone.less ├── print.plone.less ├── roboto ├── scaffolding.plone.less ├── search.plone.less ├── sitemap.plone.less ├── sitenav.plone.less ├── sortable.plone.less ├── states.plone.less ├── tables.plone.less ├── tablesorter.plone.less ├── tags.plone.less ├── thumbs.plone.less ├── toc.plone.less ├── tooltip.plone.less ├── tree.plone.less ├── type.plone.less ├── variables.plone.less └── views.plone.less They are divided by base styling, layout, function, components and views, so they could be easily reusable and extended from other themes. The main LESS resource that imports all the others is barceloneta.plone.less. It has a set of LESS variables that can be overriden either through the web using the Theming control panel or by reusing it in your own theme. They include colors, sizes, fonts and other useful parameters. Barceloneta makes use of the new Diazo bundle to expose its resources to Plone using the Resource Registries. As it is a pure Diazo theme, it keeps a low profile being Plone agnostic and only containing the theme itself. Changes from previous versions of Plone Regarding markup and comparing to the previous versions of Plone, Barceloneta introduced lots of changes in the default Plone markup to modernize it and make it more accessible. There are few parts of rendering Plone that were not updated. However, any class or id that was stripped away from Plone was done with the purpose of making upgrades and adaptations of existing Diazo themes easy. Whenever possible additional classes and ids were introduced being always domain namespaced plone-*.

plonetheme-1.5.1-1.lbn25.noarch: plonetheme module

python2-whoosh-2.7.4-7.lbn25.py37.noarch: Whoosh is a fast, featureful full-text indexing and searching library implemented in pure Python. Programmers can use it to easily add search functionality to their applications and websites. Every part of how Whoosh works can be extended or replaced to meet your needs exactly.

python2-coverage-5.5-1.lbn25.x86_64: Coverage.py is a Python 2 module that measures code coverage during Python execution. It uses the code analysis tools and tracing hooks provided in the Python standard library to determine which lines are executable, and which have been executed.

python2-html5lib-1.0.1-2.lbn25.noarch: A python based HTML parser/tokenizer based on the WHATWG HTML5 specification for maximum compatibility with major desktop web browsers.

python2-dataflake.fakeldap-2.3-1.lbn25.noarch: dataflake.fakeldap

python2-dataflake.cache-1.11-1.lbn25.noarch: dataflake.cache

python2-zope.testing-4.7-1.lbn25.noarch: This package provides a number of testing frameworks. cleanup Provides a mixin class for cleaning up after tests that make global changes. formparser An HTML parser that extracts form information. Python 2 only This is intended to support functional tests that need to extract information from HTML forms returned by the publisher. See formparser.txt. loggingsupport Support for testing logging code If you want to test that your code generates proper log output, you can create and install a handler that collects output. loghandler Logging handler for tests that check logging output. module Lets a doctest pretend to be a Python module. See module.txt. renormalizing Regular expression pattern normalizing output checker. Useful for doctests. server Provides a simple HTTP server compatible with the zope.app.testing functional testing API. Lets you interactively play with the system under test. Helpful in debugging functional doctest failures. Python 2 only setupstack A simple framework for automating doctest set-up and tear-down. See setupstack.txt. wait A small utility for dealing with timing non-determinism See wait.txt.

« Previous 20 items Next 20 items » 1 ... 655 656 657 658 659 660 661 ... 2449


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

Sections

Modified items