Search results

Products.ArchAddOn-devel-1.7-3.lbn13.noarch

The PloneSoftwareCenter testing harness should only be used and deployed by power users.

Products.ArchAddOn-devel-1.7-3.lbn19.noarch

The PloneSoftwareCenter testing harness should only be used and deployed by power users.

Products.ArchAddOn-devel-1.7-3.lbn25.noarch

The PloneSoftwareCenter testing harness should only be used and deployed by power users.

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.

Products.Archetypes-1.15.4-6.lbn19.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.

Products.Archetypes-1.15.4-7.lbn25.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.

Products.ATContentTypes-2.1.14-1.lbn13.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.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.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.

Products.ATExtensions-1.1-1.lbn25.noarch

This package provides some further fields and widgets for Archetypes as used by Plone. Most generic are the RecordField/Widget (effectively handling a dictionary) and the RecordsField/Widget (handling a list of records). The most advanced application thereof are the FormattableName(s) fields and widgets. To demonstrate their usage, there are demo content types called ‘WorkingGroup’ and ‘FormattbleNameDemo’ which can be installed using the packages ‘demotypes’ profile. To enable the types after install, go to portal types and make them implicitly addable or include them in some folderish type’s ‘allowed_content_types’.