Search results

ftw.dashboard.portlets.postit-1.3.4-1.lbn13.noarch

How to use ftw.dashboard.postit ================================== 1.) Install the ftw.dashboard.portlets.postit product with the portal_setup tool. 2.) add a postit portlet to your dashboard 3.) create notes ... Description: ============ the postit portlet is a usefull plone 3 portlet for your dashboard. The adding and removing function are ajax implemented (jquery).

ftw.dashboard.portlets.postit-1.4.0-2.lbn25.noarch

How to use ftw.dashboard.postit ================================== 1.) Install the ftw.dashboard.portlets.postit product with the portal_setup tool. 2.) add a postit portlet to your dashboard 3.) create notes ... Description: ============ the postit portlet is a usefull plone 3 portlet for your dashboard. The adding and removing function are ajax implemented (jquery).

ftw.dashboard.portlets.postit-1.4.0-2.lbn25.noarch

How to use ftw.dashboard.postit ================================== 1.) Install the ftw.dashboard.portlets.postit product with the portal_setup tool. 2.) add a postit portlet to your dashboard 3.) create notes ... Description: ============ the postit portlet is a usefull plone 3 portlet for your dashboard. The adding and removing function are ajax implemented (jquery).

ftw.datepicker-1.3.4-1.lbn25.noarch

ftw.datepicker provides a date/time picker widget for your z3c.form fields using the jQuery based DateTimePicker widget from XDSoft (http://xdsoft.net/jqplugins/datetimepicker/). Usage You can apply the widget to your field with the help of plone.directives.form: from plone.directives import form from plone.supermodel import model from ftw.datepicker.widget import DateTimePickerWidgetFactory class MySchema(model.Schema): form.widget(due_date=DateTimePickerWidgetFactory) due_date = schema.Datetime() This renders a widget which allows to select the date and time. You can pass a custom configuration of the widget like this: from plone.directives import form from plone.supermodel import model from ftw.datepicker.widget import DateTimePickerWidgetFactory class MySchema(model.Schema): form.widget('due_date', DateTimePickerWidgetFactory, config=my_config) due_date = schema.Datetime() config can either be a dict or a callable which produces a dict. The value is then converted to a JSON object and passed to the template for the widget to be picked up. Example: {‘format’: ‘d.m.Y’, ‘timepicker’: False}. See http://xdsoft.net/jqplugins/datetimepicker/ for a full list of options. You could apply the widget even to a TextLine field if you need to.

ftw.datepicker-1.3.4-1.lbn25.noarch

ftw.datepicker provides a date/time picker widget for your z3c.form fields using the jQuery based DateTimePicker widget from XDSoft (http://xdsoft.net/jqplugins/datetimepicker/). Usage You can apply the widget to your field with the help of plone.directives.form: from plone.directives import form from plone.supermodel import model from ftw.datepicker.widget import DateTimePickerWidgetFactory class MySchema(model.Schema): form.widget(due_date=DateTimePickerWidgetFactory) due_date = schema.Datetime() This renders a widget which allows to select the date and time. You can pass a custom configuration of the widget like this: from plone.directives import form from plone.supermodel import model from ftw.datepicker.widget import DateTimePickerWidgetFactory class MySchema(model.Schema): form.widget('due_date', DateTimePickerWidgetFactory, config=my_config) due_date = schema.Datetime() config can either be a dict or a callable which produces a dict. The value is then converted to a JSON object and passed to the template for the widget to be picked up. Example: {‘format’: ‘d.m.Y’, ‘timepicker’: False}. See http://xdsoft.net/jqplugins/datetimepicker/ for a full list of options. You could apply the widget even to a TextLine field if you need to.

ftw.dictstorage-1.2-3.lbn13.noarch

This package provides a layer for storing key / value paires. The storage can be configured dinamically by providing a IConfig adapter of the context on which the dict storage is used.

ftw.dictstorage-1.2-3.lbn25.noarch

This package provides a layer for storing key / value paires. The storage can be configured dinamically by providing a IConfig adapter of the context on which the dict storage is used.

ftw.dictstorage-1.2-3.lbn25.noarch

This package provides a layer for storing key / value paires. The storage can be configured dinamically by providing a IConfig adapter of the context on which the dict storage is used.

ftw.geo-1.3-1.lbn19.noarch

Introduction This product helps integrating the collective.geo.* packages and aims to provide some sensible defaults. Besides some integration glue it defines a new interface IGeocodableLocation that can be used to create adapters that knows how to represent the location of a content type with address-like fields as a string suitable for passing to a geocoding API. Purpose Automatic geocoding of IGeoreferenceable content types via an IGeocodableLocation adapter Caching of geocoding responses Only trigger geocoding lookups if location related fields on the content item changed Facilitate doing automatic geocoding based on location fields and still allow for manually setting custom coordinates Usage Automatically geocoding your content types In order for your content types to be automatically geocoded on ObjectEdited or ObjectInitialized events, you need to create an adapter for your content type that implements IGeocodableLocation and knows how to build a geocodable location string from the content type's location related fields. In order to implement the interface you need to define a getLocationString method on your adapter that returns the complete location as a comma separated string, with the location parts getting less specific from left to right.

ftw.geo-1.3-1.lbn25.noarch

Introduction This product helps integrating the collective.geo.* packages and aims to provide some sensible defaults. Besides some integration glue it defines a new interface IGeocodableLocation that can be used to create adapters that knows how to represent the location of a content type with address-like fields as a string suitable for passing to a geocoding API. Purpose Automatic geocoding of IGeoreferenceable content types via an IGeocodableLocation adapter Caching of geocoding responses Only trigger geocoding lookups if location related fields on the content item changed Facilitate doing automatic geocoding based on location fields and still allow for manually setting custom coordinates Usage Automatically geocoding your content types In order for your content types to be automatically geocoded on ObjectEdited or ObjectInitialized events, you need to create an adapter for your content type that implements IGeocodableLocation and knows how to build a geocodable location string from the content type's location related fields. In order to implement the interface you need to define a getLocationString method on your adapter that returns the complete location as a comma separated string, with the location parts getting less specific from left to right.