Search results

collective.templateengines-0.3.4-2.lbn13.noarch

collective.templateengines is an template engine abstraction layer for Python. It defines generic Zope interfaces for communicating with various Python template engines to achieve higher code reuse value. This package is still much in development. All contributions and comments are welcome. Features collective.templateengines helps you to achieve * Easy, pluggable, template language switching. Write template tag code only once and use it across all template engines using abstracted tag plug-ings * Clean your codebase from template engine dependencies * Generic error and warning reporting mechanism across template engines * EGG deployment and easy_install support from PyPi repository * Interfaces defined using standard Zope interfaces package * Backends for Django template Language, Cheetah and Jinja2 * Unit tests

collective.templateengines-0.3.4-2.lbn19.noarch

collective.templateengines is an template engine abstraction layer for Python. It defines generic Zope interfaces for communicating with various Python template engines to achieve higher code reuse value. This package is still much in development. All contributions and comments are welcome. Features collective.templateengines helps you to achieve * Easy, pluggable, template language switching. Write template tag code only once and use it across all template engines using abstracted tag plug-ings * Clean your codebase from template engine dependencies * Generic error and warning reporting mechanism across template engines * EGG deployment and easy_install support from PyPi repository * Interfaces defined using standard Zope interfaces package * Backends for Django template Language, Cheetah and Jinja2 * Unit tests

collective.templateengines-0.3.4-2.lbn25.noarch

collective.templateengines is an template engine abstraction layer for Python. It defines generic Zope interfaces for communicating with various Python template engines to achieve higher code reuse value. This package is still much in development. All contributions and comments are welcome. Features collective.templateengines helps you to achieve * Easy, pluggable, template language switching. Write template tag code only once and use it across all template engines using abstracted tag plug-ings * Clean your codebase from template engine dependencies * Generic error and warning reporting mechanism across template engines * EGG deployment and easy_install support from PyPi repository * Interfaces defined using standard Zope interfaces package * Backends for Django template Language, Cheetah and Jinja2 * Unit tests

collective.testcaselayer-1.6-1.lbn13.noarch

Use test cases as zope.testing layers

collective.testcaselayer-1.6.1-1.lbn25.noarch

The support for layers provided by zope.testing helps to lessen the amount of time consumed during test driven development by sharing expensive test fixtures, such as is often requires for functional test. This package provides several well tested facilities to make writing and using layers faster and easier. The collective.testcaselayer.common.common_layer, used in the Quick Start, also includes some commonly useful test fixtures: a mock mail host remove ‘Unauthorized’ and ‘NotFound’ from error_log ignored exceptions puts the resources registries in debug mode (portal_css, portal_javascripts, portal_kss)

collective.testcaselayer-1.6.1-1.lbn25.noarch

The support for layers provided by zope.testing helps to lessen the amount of time consumed during test driven development by sharing expensive test fixtures, such as is often requires for functional test. This package provides several well tested facilities to make writing and using layers faster and easier. The collective.testcaselayer.common.common_layer, used in the Quick Start, also includes some commonly useful test fixtures: a mock mail host remove ‘Unauthorized’ and ‘NotFound’ from error_log ignored exceptions puts the resources registries in debug mode (portal_css, portal_javascripts, portal_kss)

collective.themefragments-1.0.0-1.lbn19.noarch

Diazo Rules may operate on content that is fetched from somewhere other than the current page being rendered by Plone, by using the href attribute to specify a path of a resource relative to the root of the Plone site: <!-- Pull in extra navigation from a browser view on the Plone site root --> <after css:theme-children="#leftnav" css:content=".navitem" href="/@@extra-nav" /> The href attribute can be used with any rule apart from <drop /> and <strip />, and can reference any URL, for example to an existing browser view configured for your site. However, it is often desirable to generate some dynamic content specifically for the purpose of constructing a particular theme. In this scenario, you can use fragments.

collective.themefragments-1.0.0-1.lbn25.noarch

Diazo Rules may operate on content that is fetched from somewhere other than the current page being rendered by Plone, by using the href attribute to specify a path of a resource relative to the root of the Plone site: <!-- Pull in extra navigation from a browser view on the Plone site root --> <after css:theme-children="#leftnav" css:content=".navitem" href="/@@extra-nav" /> The href attribute can be used with any rule apart from <drop /> and <strip />, and can reference any URL, for example to an existing browser view configured for your site. However, it is often desirable to generate some dynamic content specifically for the purpose of constructing a particular theme. In this scenario, you can use fragments.

collective.tinymceplugins.advfilelinks-1.2.1-1.lbn19.noarch

An advanced Plone TinyMCE plugin for handling links to files

collective.tinymceplugins.advfilelinks-1.2.1-1.lbn25.noarch

An advanced Plone TinyMCE plugin for handling links to files