Modified items

All recently modified items, latest first.

collective.geo.file-0.6-1.lbn13.noarch: collective.geo.file provides a view for KML, KMZ (Keyhole Markup Language) and GPX (GPS eXchange Format) files. The view renders the file in a openlayers Map using the collective.geo library. The product does not introduce a content type but adds an additional view to the Archetypes file and collection type. When you upload a file with the correct mimetype 'application/vnd.google-earth.kml+xml' (i.e with the extension *.kml), 'application/vnd.google-earth.kmz' (extension *.kmz) or 'application/gpx+xml' (i.e. with the extension *.gpx) the map view will be applied by default. KML, KMZ and GPX files are displayed in the KML Openlayers View of collections and Folders

collective.geo.fastkml-0.3-1.lbn13.noarch: collective.geo.fastkml replaces the template based generation of collective.geo.kml with the objectoriented approch of fastkml collective.geo.fastkml does support Polygons and MultiPolygons with holes. Depending how many holes your polygons have it may take longer to generate you KML file with collective.geo.fastkml (as collective.geo.kml ignores the holes). Generally collective.geo.fastkml is slightly faster than collective.geo.kml and produces smaller files. The style for polygons is created from the linestyle and polygonstyle so polygons can have an outline that is diffrent from the polygon fill style collective.geo.fastkml does not have an interface of its own, it just overrides the kml-document view of collective.geo.kml.collective.geo.fastkml replaces the template based generation of collective.geo.kml with the objectoriented approch of fastkml collective.geo.fastkml does support Polygons and MultiPolygons with holes. Depending how many holes your polygons have it may take longer to generate you KML file with collective.geo.fastkml (as collective.geo.kml ignores the holes). Generally collective.geo.fastkml is slightly faster than collective.geo.kml and produces smaller files. The style for polygons is created from the linestyle and polygonstyle so polygons can have an outline that is diffrent from the polygon fill style collective.geo.fastkml does not have an interface of its own, it just overrides the kml-document view of collective.geo.kml.

collective.geo.exif-0.1-1.lbn13.noarch: This Product extracts latitude and longitude out of the EXIF informations of an Image and sets its coordinates to them. The placemark marker is set to the images thumbnail. It extracts the information when an image is added or you can call it manually by appending /@@extract_exif_geoannotations.html to its url. You may also mass annotate all contents of a folder or an entire site by calling this view on a folder or the site root.

collective.geo.contentlocations-3.1-1.lbn13.noarch: collective.geo.contentlocations is a GUI for collective.geo.geographer. It provides some simple forms to add geographical coordinates and associated settings to Plone content types.

collective.geo.bundle-2.1-1.lbn13.noarch: collective.geo allows to geo-reference Plone content types and to display this information over a map. The core of collective geo is composed by the following packages: collective.geo.geographer provides geo annotation for Plone. (repository) collective.geo.openlayers enables openlayers machinery into Plone. (repository) collective.geo.settings provides some utilities where settings of collective.geo packages can be stored (repository) collective.geo.mapwidget provides some handy page macros and adapters to easily manage multiple maps on one page. (repository) collective.z3cform.mapwidget provides a mapwidget for z3c.form framework. (repository) collective.geo.contentlocations provides a GUI for collective.geo.geographer. It provides some simple forms to add geographical coordinates to Plone content types. (repository) collective.geo.kml provides KML views for georeferenced objects, allowing Plone content types to be visualized in Google Earth. (repository) To display the maps, collective.geo takes advantage of Openlayers, a JavaScript library for displaying map data in web browsers, with no server-side dependencies. As a default map source we can select OpenStreetMap, Google Maps or Bing Maps.

collective.geo.behaviour-1.1-1.lbn13.noarch: This package provides the ability to assign geographical information to Dexterity-based (plone.app.dexterity) content types within Plone and does so using collective.geo.geographer and collective.geo.mapwidget. By applying the behaviour Collective Geo Maps to a Dexterity content type, a Coordinates field becomes available when creating or editing said content. This allows a user to either look-up coordinates for a place or feature via geo-coding, draw a geographical feature (such as a point, line or polygon) on a map, or enter details manually in Well-Known Text (WKT) format. Collective.geo.behaviour also provides Collective Geo Styles behaviour. By this behaviour it is possible to customize the style of the features that will be displayed on the map for each content type. Geographical information can be used by the rest of the collective.geo set of packages. For instance, the coordinates can be displayed on maps against Collections or Folders using collective.geo.kml.

collective.geo-1.0-1.lbn13.noarch: collective.geo module

collective.forgetit-0.0.1-1.lbn13.noarch: Remove uninstalled Products/package residue

collective.flowplayer-3.1.2-1.lbn13.noarch: A simple package using Flowplayer for video and audio content

collective.flexitopic-0.7-1.lbn13.noarch: Flexitopic integrates the easy use of plone collections with a Flexigrid AJAX view. The criteria from the topic are taken to construct a simple query form to narrow down a search inside a collection. Subtopics are displayed inside tabs of the (old style) collection. It works with new (plone.app.collection.Collection) and old (Products.ATContentTypes.ATTopic) style collections Flexitopic does not install a new content type but just adds an additional view to the collection type. it degrades for non javascript browsers to a simple table - (almost) same usability, no information loss. it requires JQuery only (built into plone 4) no JQuery UI lightweight JS Flexigrid: 27 KB packed JSlider: 22 KB packed

collective.fastview-0.2.2-2.lbn13.noarch: View and viewlet helper modules for Plone theme and five.grok developers

collective.fancyzoomview-1.0.1-2.lbn13.noarch: collective.fancyzoomview provides smooth javascript image zooming for Plone folders, topics and news items based on Steve Smith's jQuery version of Fancy Zoom.

collective.externaleditor-1.0.0-2.lbn13.noarch: This package add a Control Panel to enable or disable external editor (ext_editor property in Plone seems to be unused) and to choose on which content types action will be available. Technically this package add a skin layer to override external_edit.py and externalEditorEnabled.py python scripts from Plone to make them call views. These views respect the same behavior as today in Plone but add security checks (now you need "Modify Portal Content" to call external_edit) and add the support for content types you choose in the configlet. Permissions 'WebDAV Unlock items' and 'WebDAV Lock items' are given to the 'Editor' role. IMPORTANT : previous settings for these permissions will be erased.

collective.elephantvocabulary-0.2.4-1.lbn13.noarch: Like elephants don't forget anything, so does not collective.elephantvocabulary. It provides a wrapper around for existing zope.schema vocabularies and make them not forget anything. Example usecase would be a vocabulary (source) of users which from certain point in time wants to hide / deactivate some users for form or listing. But at the same time you want keep old references to user term working. This is where collective.elephantvocabulary comes into the picture. With it you wrap existing vocabulary of users and provide set of hidden list of users (term values).

collective.easytemplate-0.7.10-2.lbn13.noarch: Easy Template (collective.easytemplate) products brings easy dynamic texts to Plone. You don't need to create full blown product just for few dynamic pages anymore - the most simplest things can be typed straight from the visual editor. Templating is a way to add simple programming logic to text output. This products adds or enhances templating supports on various parts of Plone site.

collective.doormat-0.1-2.lbn13.noarch: collective.doormat

collective.documentviewer-2.2.1-1.lbn13.noarch: This package integrates documentcloud's viewer and pdf processing into plone. Example viewer: https://www.documentcloud.org/documents/19864-goldman-sachs-internal-emails Features * very nice document viewer * OCR * Searchable on OCR text * works with many different document types * plone.app.async integration with task monitor * lots of configuration options * PDF Album view for display groups of PDFs Works with Besides displaying PDFs, it will also display: * Word * Excel * Powerpoint * HTML * RTF Install requirements * docsplit: http://documentcloud.github.com/docsplit/ * graphicsmagick * ghostscript * poppler * tesseract * pdftk * openoffice(for doc, excel, ppt, etc types) * md5 or md5sum command line tool Async Integration It it highly recommended to install and configure plone.app.async in combination with this package. Doing so will manage all pdf conversions processes asynchronously so the user isn't delayed so much when saving files.

collective.dancingnotlikely-1.0.0-2.lbn13.noarch: This product patches the elements that shouldn't been show in newsletter with Singing and Dancing. It add content-history id and DocumentByLine class to the list.

collective.dancing-0.9.10-5.lbn13.noarch: Singing & Dancing is the next generation newsletter Product for Plone. It's an out of the box solution that works without modification for most of your use cases. And should you find something that Singing & Dancing can't do, it's built to be easily extended via plug-ins using the Zope 3 Component Architecture. Features Modern and extensible Singing & Dancing builds on the latest and greatest efforts in the Zope and Plone world. It makes heavy use of the excellent z3c.form library and the Zope 3 Component Architecture. This allows you to easily plug in and extend Singing & Dancing to fit your needs. Well tested An extensive suite of automated tests make Singing & Dancing exceptionally stable and reliable. We currently have 200+ tests. Singing & Dancing is not gonna leave you in the lurch! Fully managable through the Plone interface Singing & Dancing is fully usable out of the box. An extensive set of forms reachable through the configuration panel let you as the user configure many details of your newsletters, like when they're sent (periodically or manually), what is sent (through the use of the Smart Folder interface, or manually), and to whom. Subscriptions Singing & Dancing uses confirmed subscription, i.e. subscribers receive an e-mail to confirm their subscription. Users can subscribe via a standard subscription form that lists all available newsletters in the site, or through individual subscription forms, e.g. in portlets.

collective.dancefloor-0.4.4-2.lbn13.noarch: Provides local configuration for collective.dancing, thus allowing for news letter channels to be context-based. This is done by registering local utilities for channel lookup. UI-wise this is done by having a additional boolean field in the settings schemata injected by archetypes.schemaextender.

« Previous 20 items Next 20 items » 1 ... 2318 2319 2320 2321 2322 2323 2324 ... 2359


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

Sections

Modified items