plone

plone.app.collection-1.0.11-1.lbn13.noarch
plone.app.collection
Located in LBN / … / Plone and Zope / BastionLinux 13
plone.app.collection-1.1.4-1.lbn25.noarch
Collections in Plone are the most powerful tool content editors and site managers have to construct navigation and site sections. This is a brand new implementation of collections for Plone, using ajax/javascript to make a simpler, easier and streamlined user experience for using collections. Having a more lightweight backend that does not depend on many nested criteria types. It's designed with simplicity and usability as a main focus, so content editors and site managers can create complex search queries with ease.
Located in LBN / … / Plone and Zope / BastionLinux 25
plone.app.collection-1.1.4-1.lbn25.noarch
Collections in Plone are the most powerful tool content editors and site managers have to construct navigation and site sections. This is a brand new implementation of collections for Plone, using ajax/javascript to make a simpler, easier and streamlined user experience for using collections. Having a more lightweight backend that does not depend on many nested criteria types. It's designed with simplicity and usability as a main focus, so content editors and site managers can create complex search queries with ease.
Located in LBN / … / Plone and Zope / BastionLinux 19
plone.app.content-2.1.3-1.lbn13.noarch
plone.app.content contains various views for Plone, such as folder_contents, as well as general content infrastructure, such as base classes and name choosers.
Located in LBN / … / Plone and Zope / BastionLinux 13
plone.app.content-2.1.7-1.lbn25.noarch
plone.app.content contains various views for Plone, such as folder_contents, as well as general content infrastructure, such as base classes and name choosers.
Located in LBN / … / Plone and Zope / BastionLinux 19
plone.app.content-2.1.7-1.lbn25.noarch
plone.app.content contains various views for Plone, such as folder_contents, as well as general content infrastructure, such as base classes and name choosers.
Located in LBN / … / Plone and Zope / BastionLinux 25
plone.app.contentlisting-1.0.5-1.lbn13.noarch
Listing and working with Plone content objects using plone.app.contentlisting This is valid for Plone 4.1 upwards. Many of the operations for customizations, templates, views and portlets in Plone are related to lists of content objects. Their sources can be different, although usually they are some sort of catalog search, the contents of a particular folder or a list of objects from a relation. To make it simpler to work with these, we have made plone.app.contentlisting, which ensures that lists of content objects always behave in the same way and according to predefined interfaces, regardless of what the source of the objects are. The integrator shouldn't have to care whether the list of objects came from the catalog, an ORM or they are the actual objects.
Located in LBN / … / Plone and Zope / BastionLinux 13
plone.app.contentlisting-1.2-1.lbn25.noarch
Listing and working with Plone content objects using plone.app.contentlisting This is valid for Plone 4.1 upwards. Many of the operations for customizations, templates, views and portlets in Plone are related to lists of content objects. Their sources can be different, although usually they are some sort of catalog search, the contents of a particular folder or a list of objects from a relation. To make it simpler to work with these, we have made plone.app.contentlisting, which ensures that lists of content objects always behave in the same way and according to predefined interfaces, regardless of what the source of the objects are. The integrator shouldn't have to care whether the list of objects came from the catalog, an ORM or they are the actual objects.
Located in LBN / … / Plone and Zope / BastionLinux 25
plone.app.contentlisting-1.2-1.lbn25.noarch
Listing and working with Plone content objects using plone.app.contentlisting This is valid for Plone 4.1 upwards. Many of the operations for customizations, templates, views and portlets in Plone are related to lists of content objects. Their sources can be different, although usually they are some sort of catalog search, the contents of a particular folder or a list of objects from a relation. To make it simpler to work with these, we have made plone.app.contentlisting, which ensures that lists of content objects always behave in the same way and according to predefined interfaces, regardless of what the source of the objects are. The integrator shouldn't have to care whether the list of objects came from the catalog, an ORM or they are the actual objects.
Located in LBN / … / Plone and Zope / BastionLinux 19
plone.app.contentmenu-2.0.10-1.lbn13.noarch
============ plone.app.contentmenu contains the logic that powers Plone's content menu (the green one with the drop-down menus).
Located in LBN / … / Plone and Zope / BastionLinux 13

« Previous 10 items Next 10 items » 1 ... 2526 2527 2528 2529 2530 2531 2532 ... 4873

Sections

Search results


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