Modified items

All recently modified items, latest first.

collective.js.showmore-1.0a4-2.lbn13.noarch: collective.js.showmore provides a JQuery plugin. The plugin hides a set of nodes and replaces them with a "Show more..." link. When the link is clicked, the hidden nodes are made visible again.

collective.js.nivoslider-3.0.1.1-1.lbn13.noarch: Integration of nivoslider in Plone This version include nivoslider v3.0.1 (first responsive version) It is used by collective.plonetruegallery

collective.js.nivogallery-1.0-1.lbn13.noarch: Integration of nivogallery in Plone4(tested) and Plone3 (untested). This version include nivogallery v0.7.1 It was made for using it with collective.plonetruegallery

collective.js.jqueryui-1.10.3-1.lbn13.noarch: Integration of jqueryui in Plone, like collective.js.jquery. It is different from collective.jqueryui in many ways: * no skin dirs (js and css are in resource dirs) * no all the bunch of files and documentations from original jqueryui * this one is minified * just add all jqueryui to portal_js, and default css to portal_css (if you apply the profile) Notes ===== There are three profiles in this package: - ``default``: use this one with Plone 3.2/3.3 if you don't use plone.app.jquerytools. It will replace the jQuery version in Plone by the one included in collective.js.jquery because Plone <= 3.3rc2 include an old version of jQuery (1.2) and jqueryui 1.7 requires jQuery 1.3+. - ``withjqtoolsplone3``: use this one if you include plone.app.jquerytools yourself in a Plone 3.2, this profile installs a jqueryui library without the tabs plugin which conflicts with plone.app.jquerytools. It will replace the jQuery version in Plone by the one included in collective.js.jquery. - ``withjqtools``: use this one if you use Plone 3.3/4. It will keep the jQuery version included in Plone and is compatible with plone.app.jquerytools. You need to include plone.app.jquerytools yourself on Plone 3.3.

collective.js.jquery-1.3.2.1-6.lbn13.noarch: collective.js.jquery is a simple packaging of the jQuery library that uses setuptools for version selection and adds as a Zope browser resource. If CMF/Plone is available it is also added to the JavaScript registry.

collective.js.galleria-1.2.5-1.lbn13.noarch: This addon register Galleria JQuery plugin in Plone's resource registries. About Galleria Galleria is a JavaScript image gallery framework built on top of the jQuery library. The aim is to simplify the process of creating professional image galleries for the web and mobile devices. How to install https://secure.travis-ci.org/collective/collective.js.galleria.png This addon can be installed as any other Plone addon. Please follow official documentation. Have an idea? Found a bug? Let us know by opening a support ticket. Notes Galleria in its way to manage theme parse all link tags to find the css attached to the theme. To make it work in production mode you must add themes javascript and css called by the template. // look for manually added CSS $('link').each(function( i, link ) { reg = new RegExp( theme.css.replace('\+\+resource\+\+','\\+\\+resource\\+\\+') ); if ( reg.test( link.href ) ) { // we found the css css = true; Galleria.theme = theme; return false; } }); As you can see the original code has been patched to support ++resource++ url.

collective.js.fullcalendar-1.6.4-1.lbn13.noarch: This package include javascripts and css resources from arshaw fullcalendar. It does not provide any view or template. Is meant to be used as dependecy for building your own calendar views. Tested with Plone 3.3.5/4.0.

collective.js.datatables-2.0-1.lbn13.noarch: DataTables is a plug-in for the jQuery Javascript library. It is a highly flexible tool, based upon the principle of progressive enhancement, which will add advanced interaction controls to any HTML table. This version includes datatables 1.9.4 without the examples available in the source distribution of the plugin. It is provided with an @@example.datatables view. Install A genericsetup profile is provided to add jquery.dataTables to portal_javascript in a non-minified version with compression option set to safe. Key features of jquery.dataTables * Variable-length pagination * On-the-fly filtering * Multi-column sorting with data type detection * Smart handling of column widths * Display data from almost any data source * Scrolling options for table viewport * Fully internationalisable * jQueryUI ThemeRoller support * Rock solid - backed by a suite of 1400+ unit tests * Wide variety of plug-ins inc. TableTools, FixedHeader and KeyTable * It's free! * State saving * Hidden columns * Dynamic creation of tables * Ajax auto-loading of data * Custom DOM positioning * Single-column filtering * Alternative pagination types * Non-destructive DOM interaction * Sorting column(s) highlighting * Extensive plug-in support * Fully themeable by CSS * Solid documentation * 60+ pre-built examples * Full support for Adobe AIR * Source available at github Plugins This addon embed extras plugins: * AutoFill 1.1.2 * ColReorder 1.0.5 * ColVis 1.0.7 * FixedColumns 2.0.3 * FixedHeader 2.0.6 * KeyTable 1.1.7 * Scroller 1.0.1 * TableTools 2.0.3 How to use tabletools First include dependencies in your template, or register theses in portal_javascripts: <link rel="stylesheet" type="text/css" media="screen" href="++resource++jquery.datatables/media/css/jquery.dataTables.css"> <link rel="stylesheet" type="text/css" media="screen" href="++resource++jquery.datatables/extras/TableTools/media/css/TableTools.css"> <script type="text/javascript" src="++resource++jquery.datatables.js"></script> <script type="text/javascript" src="++resource++jquery.datatables/extras/TableTools/media/js/ZeroClipboard.js"></script> <script type="text/javascript" src="++resource++jquery.datatables/extras/TableTools/media/js/TableTools.js"></script> <style type="text/css">.clear{clear:both}</style> Next you can create your datatable: var oTable = $('#mydatatable').dataTable({ "sDom": 'T<"clear">lfrtip', "oTableTools": {"sSwfPath": "++resource++jquery.datatables/extras/TableTools/media/swf/copy_csv_xls_pdf.swf"} });

collective.js.d3-3.0.8.1-1.lbn13.noarch: D3.js is a JavaScript library for manipulating documents based on data. D3 helps you bring data to life using HTML, SVG and CSS. D3’s emphasis on web standards gives you the full capabilities of modern browsers without tying yourself to a proprietary framework, combining powerful visualization components and a data-driven approach to DOM manipulation. This products integrates D3.js library in Plone.

collective.js.colorpicker-1.0-2.lbn13.noarch: This product is an integration of JQuery Colorpicker plugin for Plone. Installation This isn't a standalone product. If you need colorpicker jquery plugin for your needs in a plone package, just add collective.js.jquery in the install_requires of your product. And add your own javascript code setting colorpicker on your input.

collective.js-1.3.2.1-6.lbn13.noarch: collective.js module

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.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.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.idashboard-1.2.5-2.lbn13.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.googleanalytics-1.4.3-1.lbn13.noarch: collective.googleanalytics is a product that integrates Plone with Google Analytics. It includes both tracking and reporting functionality. The product enables easy tracking of the standard Google statistics as well as external links, e-mail address clicks and file downloads. It also defines Analytics reports that are used to query Google and display the results using Google Visualizations. Reports are Zope objects that can be imported and exported using GenericSetup XML and modified on a site-by-site basis. The product currently provides a portlet that can display results of reports as well as a control panel for authorizing your site and configuring settings.

collective.geotransform-1.0a2-1.lbn13.noarch: GEO stands for "Gracefully E-mail Obfuscation". This package implements the solution exposed in this post of List Apart web site authored by Roel Van Gils: http://www.alistapart.com/articles/gracefulemailobfuscation/ collective.geotransform uses plone.transformchain to transform the response output from Zope before it reaches your browser. It searches for all "mailto:" occurences inside the response and transform them into encoded harmless links. This codification is done via a simple base64 encoding, but enough to fool a spam robot. This is the form of the encoded mail link: ::<a rel="nofollow" href="contact/dmljdG9yLmZlcm5hbmRlejJAdXBjbmV0LmVz">mymail</a> On the browser side, the encoded links are decoded to their original form by using a Javascript that restore them to normal "mailto:" links. The text of the link is replaced by the full E-mail specified in the original mailto attribute. Authenticated responses are NOT affected by this transform. Only anonymous responses are modified.

collective.geolocationbehavior-1.1.0.2-1.lbn13.noarch: A behavior which makes it possible to mark and item with a geographic location.

collective.geo.zugmap-1.0.2-1.lbn13.noarch: collective.geo.zugmap provides a maplayer for zugmap

collective.geo.wms-0.2-1.lbn13.noarch: collective.geo.wms is a product which enables you to embed WMS, TMS and WMTS layers in your website. It is designed to make adding WMS, TMS or WMTS layers as easy as possible. Why WMS/TMS/WMTS You will find thousands of public Map Servers with interesting and valuable information which you can display on your website. Many of these services provide WMS,TMS or WMTS only. Usage First you have to add a WMS Server to your site. The initial add form only allows you to enter the url and type of a webservice. The title, description and keywords are taken from the service if it produces a valid response to the getCapabilities query. When the server could be successfully added you can change the title, descripton and keywords. You are not allowed to change the server url or protocol. A list of layers that are available on this server will be requested directly from the server. The list of layers will be cached for 100 minutes so if layers are added on the server you may have to wait up to 2 hours for them to refresh. After you added the servers you can add layers to your website. Layers are displayed as a Map. In the add form you choose the service for your maps. You cannot change the server later by editing the layer. After you added the layer you have to choose the layers of the service you want to display in your map. Some WMS Servers do not support overlaying layers on the serverside if this is the case for the server you are connecting to you have to check 'Single Layers' for them to display. When you click on a feature on the map a request is sent to the server to get information about this feature (or features) which are displayed in a pop up. This behaviour can be disabled by unchecking 'Feature Info'

« Previous 20 items Next 20 items » 1 ... 2405 2406 2407 2408 2409 2410 2411 ... 2448


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

Sections

Modified items