plone

collective-2.2.6-2.lbn13.noarch Located in LBN / … / Plone and Zope / BastionLinux 13
collective-2.2.6-3.lbn25.noarch Located in LBN / … / Plone and Zope / BastionLinux 19
collective-2.2.6-3.lbn25.noarch Located in LBN / … / Plone and Zope / BastionLinux 25
collective-sd.analytics-0.1dev_r80513-7.lbn13.noarch
Simple Google analytics integration for Singing & Dancing Adds tracking parameters to urls in outgoing S&D newsletters. See browser.txt for more in depth info. Note for translators: Titles and descriptions for the configuration ui can be lifted from http://www.google.com/support/analytics/bin/answer.py?hl=en&answer=55578 in almost any language.
Located in LBN / … / Plone and Zope / BastionLinux 13
collective-sd.analytics-0.1.3-1.lbn25.noarch
Simple Google analytics integration for Singing & Dancing Adds tracking parameters to urls in outgoing S&D newsletters. See browser.txt for more in depth info. Note for translators: Titles and descriptions for the configuration ui can be lifted from http://www.google.com/support/analytics/bin/answer.py?hl=en&answer=55578 in almost any language.
Located in LBN / … / Plone and Zope / BastionLinux 19
collective-sd.analytics-0.1.3-1.lbn25.noarch
Simple Google analytics integration for Singing & Dancing Adds tracking parameters to urls in outgoing S&D newsletters. See browser.txt for more in depth info. Note for translators: Titles and descriptions for the configuration ui can be lifted from http://www.google.com/support/analytics/bin/answer.py?hl=en&answer=55578 in almost any language.
Located in LBN / … / Plone and Zope / BastionLinux 25
collective.alerts-1.2.3-2.lbn13.noarch
This product implements Cory LaViska's 'JQuery Alert Dialogs' for Plone. Basically, they are fancy, styleable replacements for the standard 'alert', 'confirm' and 'prompt' browser functions. Please see: http://abeautifulsite.net/notebook/87 for more information. Usage ----- When collective.alerts is installed and the jquery.alerts library registered in portal_javascripts (should be automatic), then the alerts can be called as follows: - jAlert( message, [title, callback] ) - jConfirm( message, [title, callback] ) - jPrompt( message, [value, title, callback] )
Located in LBN / … / Plone and Zope / BastionLinux 13
collective.alerts-1.2.3-2.lbn19.noarch
This product implements Cory LaViska's 'JQuery Alert Dialogs' for Plone. Basically, they are fancy, styleable replacements for the standard 'alert', 'confirm' and 'prompt' browser functions. Please see: http://abeautifulsite.net/notebook/87 for more information. Usage ----- When collective.alerts is installed and the jquery.alerts library registered in portal_javascripts (should be automatic), then the alerts can be called as follows: - jAlert( message, [title, callback] ) - jConfirm( message, [title, callback] ) - jPrompt( message, [value, title, callback] )
Located in LBN / … / Plone and Zope / BastionLinux 19
collective.alerts-1.2.3-2.lbn25.noarch
This product implements Cory LaViska's 'JQuery Alert Dialogs' for Plone. Basically, they are fancy, styleable replacements for the standard 'alert', 'confirm' and 'prompt' browser functions. Please see: http://abeautifulsite.net/notebook/87 for more information. Usage ----- When collective.alerts is installed and the jquery.alerts library registered in portal_javascripts (should be automatic), then the alerts can be called as follows: - jAlert( message, [title, callback] ) - jConfirm( message, [title, callback] ) - jPrompt( message, [value, title, callback] )
Located in LBN / … / Plone and Zope / BastionLinux 25
collective.amberjack.core-1.1-2.lbn13.noarch
How to create new tour First of all you need to define the tour. Starting version 1.1 we are using configuration based style. A tour is a .cfg file. It has an amberjack main section which has two options: title and steps - this is where you define tour steps: [amberjack] steps = my_step1 my_step2 title = My first amberjack tour there are also available two blueprints: 1. Step a step section is defined by collective.amberjack.blueprints.step and has several options: * title * text * url - step url definition * xpath - xpath selector * xcontent - xcontent selector * microsteps - microsteps sections * validators - tales expression validation it looks like that: [my_step1] blueprint = collective.amberjack.blueprints.step title = This is my first Step text = You should now know how to create a step section url = /mystep validators = python: context.isFolderish() xpath = '' xcontent = '' microsteps = microstep_1 microstep_2 2. Microstep a microstep section is defined by collective.amberjack.blueprints.microsteps and it has several options: * idstep * text * description * selector it looks like that: [microstep_1] blueprint = collective.amberjack.blueprints.microstep idstep = menu_state text = This is my dummy microstep description = Now you should now how to define microsteps selector = #insert Tour registration Finally you have to register it. The only acceptable format is an archive (zip or tar) which contains one or multiple .cfg files (tours) Using zcml: <configure xmlns:collective.amberjack="http://namespaces.plone.org/collective.amberjack.core"> <collective.amberjack:tour tourlocation="mytourpackage.zip" /> </configure>
Located in LBN / … / Plone and Zope / BastionLinux 13

« Previous 10 items Next 10 items » 1 ... 299 300 301 302 303 304 305 ... 4852

Sections

Search results


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