Modified items

All recently modified items, latest first.

collective.cover-1.0a3-1.lbn13.noarch: collective.cover is a package that allows the creation of elaborate covers for website homepages, especially for news portals, government sites and intranets that require more resources than a simple page or collection can offer. However, despite offering rich resources to build a cover, collective.cover also provides a very easy mechanism for managing its contents, built around a drag-and-drop interface. collective.cover is based on Blocks and Tiles, like Deco, the new layout composition system for Plone. Use cases Suppose you are running The Planet, a news site that has a bunch of editors focused on getting news on different topics, like Economy, Health or Sports. If you are the main publisher of the site, you may want to delegate the construction of the cover page of the Economy section to the people working on that section content, but you might not want them messing around the Sports section as well. Also, suppose you have the final game of the World Cup and the match is going to be defined on penalties: you may want to prepare a couple of cover pages and publish the right one focused on the team that won in the end. These are the kind of issues we want to solve with this package; we are still far from it, but that is the idea.

collective.contentlicensing-2.2.6-2.lbn13.noarch: This tool is used to manage copyright licenses within plone. It allows for both a site wide copyright license to be set by default, and the ablility to set licenses on individual objects. It supports a number of licenses including all rights reserved, GFDL, and Creative Commons (with an integrated license picker). You can also enter and select licenses not supported by default, or configure new licenses that will appear in the selection widget for your Plone instance.

collective.contentleadimage-1.3.4-1.lbn13.noarch: This products adds complete support for adding descriptive image to any Archetypes based content in Plone site. Each object has new tab "Edit lead image", which allows to upload new or remove current image. It is similar behaviour as Plone News Item (you can add image to news item and this image is displayed in news item overview listing. There is folder_leadimage_view page template, which can be used to list all items in the folder together with images attached. There is configuration control panel, where you can set maximum width and height of the uploaded images. The width and height is applied on each image upload (image is automatically resized). You can specify smaller width and height which is used as image preview in the below content title viewlet (next to content Description). Large image is used in the above content body viewlet (floated left at the top of content body). Below content title viewlet is preffered, but Manager can easily switch the viewlets on/off in the control panel. There is FieldIndex and metadata in portal_catalog: hasContentLeadImage (True/False). This may help developers to create own templates optimized for displaying lead image.

collective.beaker-1.0b3dev_r239026-1.lbn13.noarch: This package provides a means to configure the Beaker session management and caching framework for use within a Zope 2 (and Plone) environment. Ordinarily, Beaker is configured using WSGI middleware. However, Zope 2 does not (yet) run WSGI by default (unless you use repoze.zope2). This package provides an alternative configuration syntax, based in zope.conf.

collective.autorestart-0.2.0-3.lbn13.noarch: Automatically reload changed Python files - putting agility back to Plone development. collective.autorestart monitors Python .py files for changes and triggers a reload when you edit the files. This way you don't need to restart Plone server between your code edit runs. collective.autorestart uses plone.reload package to perform the actual code replacement. File system is monitored using inotify interface which is only available for Linux. The future versions will support other operating systems as long as somebody contributes the file system monitoring code or gives the author a new computer running operating system X. Features * Recursively detect changes in ZCML and Python files which are known to Zope * Automatically trigger reload when files are changed (saved) * Audio playback depending on whether the restart succeed or failed - you can go back to your files and you don't need to watch the terminal

collective.autopermission-1.0b2-1.lbn13.noarch: This package registers an event handler that initialises permissions on the fly. To use it, simply include its ZCML: <include package="collective.autopermission" /> Then, you can use the <permission /> ZCML statement to define a new type of permission, without also needing to make the permission "spring into existence" via ClassSecurityInfo or similar.

collective.amberjack.portlet-1.1-2.lbn13.noarch: collective.amberjack.portlet This package provides portlet for collective.amberjack package. Set up environment This package allows you to create portlets that contain tours. You can select the tours that can be display and choosen by an user on these portlet. So this package allows you to create sets of tours on Plone site.

collective.amberjack.plonetour-1.1-2.lbn13.noarch: Introduction This package allows you to create tours on your site, based on collective.amberjack.core. This package contains the first released tours: * Add and publish a Folder * Add and publish a Page * Add and publish a News Item * Add and publish an Event * Format a page using the visual editor * Create internal links * Create external links * Upload an image * Insert image on a page * Upload and link to a File * Using the Contents tab * Using the Display menu Others will be released soon. Add and publish a Folder This tutorial shows you how to create a new folder and then publish it. At the end of tour you can see a public folder in your Home. Add and publish a Page In this tutorial you learn how create a new page and then publish it. At the end of tour you'll create a new page and publish it on your Plone-powered website. This tutorial uses the folder that you created in a previous tour ("Add and publish a Folder"). Add and publish a News Item In this tutorial you learn how create a new news item and then publish it. At the end of tour you can see a public news item in your Home. This tutorial uses the folder that you created in one of previous tutorials ("Add and publish a Folder"). Add and publish an Event In this tutorial you learn how create a new event and then publish it. At the end of tour you can see a public event in your Home. This tutorial uses the folder that you created in one of previous tutorials ("Add and publish a Folder"). Format a page using the visual editor In this tutorial you will revisit a page that you created and learn how to format content on the page. This tutorial uses the folder and the page that you created in previous tutorials ("Add and publish a Folder" and "Add and publish a Page"). You will learn how to to apply bold, italics, text alignment, and paragraph styles to the page. Create internal links In this tour you learn how insert hyperlinks into a page. You will revisit a page that you created in the previous tutorial "Add and publish a Page". You learn how browse the content of your site and how create a hyperlink to any page, news item, event, image, file or other content type within your Plone site. Create external links In this tutorial you learn how to create link to other webpages, documents or resources online. This tutorial uses the Page that you created in previous tutorials "Add and publish a Page". You learn how find the external link icon and how make a preview, that lets you confirm that you have the correct webpage. Upload an image This tour shows how add a new image to folder that you created in one of previous tutorials ("Add and publish a Folder"). You will browse the content of your site and find the image file you want to place in Plone. Insert image on a page In this tutorial you learn how insert image into a page. You should have at least one image already from a previous tutorial "Upload an image". You will browse to the location of an image you would like to insert and choose Left alignment and a Size or change the 'alt' text for the image. Upload and link to a File In this tutorial you learn how upload to your site binary file such as a PDF, DOC, XLS, PPT, RTF or other file type and how create a link to the file to allow a site visitor to download the file. Using the Contents tab In this tutorial you learn how take a look at the Contents tab, that lets you browse the filesystem of your website and perform administrative tasks. The items you have been creating for previous tutorials will listed in the Contents view. You learn how change the order of contents within a folder, how make copies of a content item and how cut-and-paste. Using the Display menu In this tutorial you learn how change the way that the folders contained items will appear on the screen, using the Display drop-down menu. You will see the Summary view, Tabular View and Select default page.

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>

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] )

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.

collective-2.2.6-2.lbn13.noarch

catdoc-0.94.2-10.fc18.1302272321kf.armv6hl: catdoc is program which reads one or more Microsoft word files and outputs text, contained insinde them to standard output. Therefore it does same work for.doc files, as unix cat command for plain ASCII files. It is now accompanied by xls2csv - program which converts Excel spreadsheet into comma-separated value file, and catppt - utility to extract textual information from Powerpoint files

catdoc-0.94.2-6.fc12.x86_64: catdoc is program which reads one or more Microsoft word files and outputs text, contained insinde them to standard output. Therefore it does same work for.doc files, as unix cat command for plain ASCII files. It is now accompanied by xls2csv - program which converts Excel spreadsheet into comma-separated value file, and catppt - utility to extract textual information from Powerpoint files

buildout.eggtractor-0.6-2.lbn13.noarch: Q: What is a buildout extension ? A: http://pypi.python.org/pypi/zc.buildout#extensions The problem When developing zope/plone eggs with buildout I have to edit the buildout configuration file ( in 3 places ) each time I create/delete/rename a development egg in the src directory or in other development directories (sometime I have more than one). I have to add/delete/rename the egg in the eggs option of the [buildout] and then add/delete/rename the egg path in the develop option of the [buildout] and in the end add/delete/rename the zcml option of the zope [instance] or in the configure.zcml file of my policy package. This is too much specially when the speed is set to development mode. I need a less boring way to develop. Solution buildout.eggtractor is a buildout extension that scans the src directory or a list of directories I give for eggs and picks them up automatically. So no more editing of the buildout's configuration file. When buildout.eggtractor finds an egg in the scanned directory it: 1. adds the egg to the ``eggs`` option of all zope instance parts or to a set of given parts 2. adds the egg's path in the ``develop`` option of the ``[buildout]`` 3. If ``tractor-autoload-zcml`` is not given or set to other thing than false, scans the egg folder for ``configure.zcml``, ``meta.zcml`` and ``overrides.zcml`` and adds the appropriate zcml entries to the ``zcml`` option of the zope instance parts or to a set of given parts. This steps are done on the fly when running buildout. So I can add/delete/rename an egg and it will be picked up. NOTE: The extension does not write to the buildout's configuration file. buildout.eggtractor options tractor-src-directory: A set of directories to scan for development eggs. Defaults to the src directory of the buildout. tractor-target-parts: A set of parts to update their eggs option with eggs found in the tractor-src-directory. Defaults to zope instance parts if any. tractor-autoload-zcml(boolean): Update the zcml option of tractor-target-parts with the eggs found in tractor-src-directory. Defaults to true tractor-zcml-top: A set of eggs to load their zcml files first. Defaults to an empty set. How to use it Using buildout.eggtractor is very simple. As said, it is a buildout extension. All I have to do is to declare it in the extensions option: [buildout] parts = extensions = buildout.eggtractor That's all. buildout.eggtractor will scan the src directory and do its job every time I run the buildout command. When I have other directories I want to scan I just add an tractor-src-directory option in the [buildout] and add my directories there: [buildout] parts = extensions = buildout.eggtractor tractor-src-directory = dev-src1 dev-src2 src In a few cases when the priority of loading zcml files matters. I add the egg to be loaded first in the tractor-zcml-top option in the [buildout]: [buildout] parts = extensions = buildout.eggtractor tractor-src-directory = dev-src1 dev-src2 src tractor-zcml-top = plone.app.mypackage1 If I want to add the eggs found in the development directories to the eggs option of a given set of parts, I add a tractor-target-parts option and add the parts there: [buildout] parts = instance1 instance2 instance3 extensions = buildout.eggtractor tractor-target-parts = instance1 instance3 This way only instance1 and instance3 will be updated. If I have already other way to include the zcml files (ie: z3c.autoinclude) and don't want eggtractor to generate the zcml slugs, I add an tractor-autoload-zcml option and set it to false In most cases you will only need to add buildout.eggtractor to the extensions option of the [buildout] without any extra configuration options. LIMITATION The extension assumes that the egg name reflects its file system structure example: if the egg name is com.mustap.www the extension assumes that the file system structure is one of the following: 1. com.mustap.www/src/com/mustap/www 2. com.mustap.www/com/mustap/www This is where the extension looks for configure.zcml, meta.zcml and overrides.zcml files. If the egg name has nothing to do with how it is structured on the system, the extension will ignore it. XXX: I guess walking through the directory is better than this assumption. In my case this is not a limitation as I choose my egg names that way.

buildout.dumppickedversions-0.5-2.lbn13.noarch: Dump buildout picked versions.

borg.localrole-3.0.2-5.lbn13.noarch: This PAS_ plug-in can be used to assign local roles in a particular context, by adapter. It can be installed via the GenericSetup_ profile in this product.

borg-3.0.2-5.lbn13.noarch: borg python module

bastion-monit-zope-1.4.0-1.lbn13.noarch: Zope start/stop/control

bastion-monit-zeo-1.4.0-1.lbn13.noarch: Zope/ZEO start/stop/control

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


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

Sections

Modified items