Search results

ftw.dashboard-1.4.0-2.lbn25.noarch

The postit portlet let you add small notes on your dashbord.

ftw.dashboard.dragndrop-1.6.0-4.lbn25.noarch

ftw.dashboard.dragndrop adds persistent dragndrop functionality to the standard plone dashboard. http://onegov.ch/approved.png/image Certified: 01/2013 Features: Drag'n'drop: All dashboard portlets can be moved with drag'n'drop from column to column and reordered in the column. Folding: Dashboard porlets are foldable. Edit portlet icon: Dashboard portlets have an icon on the top (pencil) for editing the portlet. close/remove portlet: Dashboard portlets have an icon on the top (cross) for removing the portlet from the dashboard.

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.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.jsondump-1.1.0-1.lbn25.noarch

ftw.jsondump provides JSON representations for Plone objects. By using adapters the JSON representation can easily be customized.

ftw.lawgiver-1.4.0-1.lbn19.noarch

Motivation Developing and maintaining complex Plone workflows is a time-consuming and cumbersome endeavor. Dozens of permissions need to be managed for different roles and different workflow states. Usually, this has to be done directly in the ZMI of Zope by selecting or unselecting thousands of checkboxes. This process has been shown to be very tedious and prone to errors. Furthermore, it is no simple task to document the workflow and the associated design decisions which led to the resulting configuration of permissions and roles. The extension or adaption of an existing workflow becomes very difficult, leading to workflows which are barely maintainable. Another problem poses the communication between workflow integrator and customer. The security system of Zope is based on a role-based access control (RBAC) which is intrinsically complex due to its use of roles, permissions, and workflow states. Experience has shown that these security concepts can be hard to convey to customers. How it works ftw.lawgiver helps solving these problems by using a DSL to describe how a workflow should work. The lawgiver then generates the complete workflow definition (definition.xml) based on this specification. By separating this specification from the resulting workflow definition (which is in XML) the specification does not have to use permissions--handling the permissions is the job of the lawgiver. Using the specification file the workflow can easily be regenerated at any time and will handle additional permissions automatically when regenerated. However, it is still the task of the developer to regenerate the definition.xml when more or other permissions have to be managed. He or she have to make sure that the workflow is properly installed with an upgrade step / reindexing security.

ftw.mobilenavigation-1.4.6-1.lbn19.noarch

This product helps to create a responsive design. There are following mobile_buttons in portal_actions defined: Toggle personaltools (default personaltools) Toggle searchbox (default searchbox) Toggle special navigation (special navigation, using AJAX to expand children) Navigation types You can choose between: Expandable navigation (install profile default) Sliding navigation (install profile slide navigation)

filebeat-7.3.0-1.git6f0ec01.lbn25.x86_64

Filebeat is an open source file harvester, mostly used to fetch logs files and feed them into logstash. Together with the libbeat lumberjack output is a replacement for logstash-forwarder. To learn more about Filebeat, check out https://www.elastic.co/products/beats/filebeat.