Search results

collective.idashboard-1.2.5-2.lbn19.noarch

Pimp your Plone dashboard! This is a Plone Product that makes your user dashboard behave similarly to the iGoogle dashboard. Specifically, it adds the following functionality: * Drag and drop portlets within and between rows * Ajax enabled inline portlet editing and saving * Ajax removal/deletion of portlets with themable confirmation modal dialog. * Toggle show/hide portlets

collective.idashboard-1.2.5-2.lbn25.noarch

Pimp your Plone dashboard! This is a Plone Product that makes your user dashboard behave similarly to the iGoogle dashboard. Specifically, it adds the following functionality: * Drag and drop portlets within and between rows * Ajax enabled inline portlet editing and saving * Ajax removal/deletion of portlets with themable confirmation modal dialog. * Toggle show/hide portlets

collective.indexing-2.0a3-2.lbn13.noarch

collective.indexing is an approach to provide an abstract framework for queuing and optimizing index operations in Plone as well as dispatching them to various backends. The default implementation aims to replace the standard indexing mechanism of CMF to allow index operations to be handled asynchronously in a backwards-compatible way. Queuing these operations on a transaction level allows to get rid of redundant indexing of objects and thereby providing a substantial performance improvement. By leveraging the component architecture and Zope event system collective.indexing also makes it much easier to use backends other than or in addition to the standard portal catalog for indexing, such as dedicated search engine solutions like Solr, Xapian or Google Search Appliance. One backend implementation designed to be used with this package has already been started in the form of collective.solr.

collective.indexing-2.0a3-2.lbn19.noarch

collective.indexing is an approach to provide an abstract framework for queuing and optimizing index operations in Plone as well as dispatching them to various backends. The default implementation aims to replace the standard indexing mechanism of CMF to allow index operations to be handled asynchronously in a backwards-compatible way. Queuing these operations on a transaction level allows to get rid of redundant indexing of objects and thereby providing a substantial performance improvement. By leveraging the component architecture and Zope event system collective.indexing also makes it much easier to use backends other than or in addition to the standard portal catalog for indexing, such as dedicated search engine solutions like Solr, Xapian or Google Search Appliance. One backend implementation designed to be used with this package has already been started in the form of collective.solr.

collective.indexing-2.0a3-2.lbn25.noarch

collective.indexing is an approach to provide an abstract framework for queuing and optimizing index operations in Plone as well as dispatching them to various backends. The default implementation aims to replace the standard indexing mechanism of CMF to allow index operations to be handled asynchronously in a backwards-compatible way. Queuing these operations on a transaction level allows to get rid of redundant indexing of objects and thereby providing a substantial performance improvement. By leveraging the component architecture and Zope event system collective.indexing also makes it much easier to use backends other than or in addition to the standard portal catalog for indexing, such as dedicated search engine solutions like Solr, Xapian or Google Search Appliance. One backend implementation designed to be used with this package has already been started in the form of collective.solr.

collective.jqganalytics-1.1.1-2.lbn13.noarch

Introduction collective.jqganalytics uses the jQuery Google Analytics plugin to load Google Analytics asynchronously by default. Custom Variables Google Analytics tracking now provides for setting at most 5 user variables. These can be managed through the control panel in Plone under the 'Google Analytics settings' tab. There is no limit on the number of variables that can be set in the control panel since they can be disabled or optionally disabled using an expression. In the end though, the last one that is set for each slot is the one that will end up getting sent to Google for that slot. The name and value for the variables are both TALES expressions with the normal context variables (context,`here`,`request`, etc) available for use. For a complete list, see Products.CMFCore.Expression.createExprContext.

collective.jqganalytics-1.1.1-2.lbn19.noarch

Introduction collective.jqganalytics uses the jQuery Google Analytics plugin to load Google Analytics asynchronously by default. Custom Variables Google Analytics tracking now provides for setting at most 5 user variables. These can be managed through the control panel in Plone under the 'Google Analytics settings' tab. There is no limit on the number of variables that can be set in the control panel since they can be disabled or optionally disabled using an expression. In the end though, the last one that is set for each slot is the one that will end up getting sent to Google for that slot. The name and value for the variables are both TALES expressions with the normal context variables (context,`here`,`request`, etc) available for use. For a complete list, see Products.CMFCore.Expression.createExprContext.

collective.jqganalytics-1.1.1-2.lbn25.noarch

Introduction collective.jqganalytics uses the jQuery Google Analytics plugin to load Google Analytics asynchronously by default. Custom Variables Google Analytics tracking now provides for setting at most 5 user variables. These can be managed through the control panel in Plone under the 'Google Analytics settings' tab. There is no limit on the number of variables that can be set in the control panel since they can be disabled or optionally disabled using an expression. In the end though, the last one that is set for each slot is the one that will end up getting sent to Google for that slot. The name and value for the variables are both TALES expressions with the normal context variables (context,`here`,`request`, etc) available for use. For a complete list, see Products.CMFCore.Expression.createExprContext.

collective.jqueryuithememanager-1.0-2.lbn13.noarch

This add-on let you manage the jqueryui theme used in Plone. Features: * Import a theme from a zip file built on http://jqueryui.com/themeroller * Import multiple themes from a zip file * Create or modify themes within the control panel * Load all default jqueryui themes in one click in the control panel * Delete selected themes * Update themes * External add-on can embed themes within a zope browser resource directory * Select a theme

collective.jqueryuithememanager-1.0-2.lbn19.noarch

This add-on let you manage the jqueryui theme used in Plone. Features: * Import a theme from a zip file built on http://jqueryui.com/themeroller * Import multiple themes from a zip file * Create or modify themes within the control panel * Load all default jqueryui themes in one click in the control panel * Delete selected themes * Update themes * External add-on can embed themes within a zope browser resource directory * Select a theme