Modified items

All recently modified items, latest first.

zope-ExtensionClass-2.13.2-3.lbn13.x86_64: Metaclass for subclassable extension types

zope-DocumentTemplate-2.13.2-3.lbn13.x86_64: Document Templating Markup Language (DTML)

zope-DateTime-3.0.3-1.lbn13.noarch: The DateTime package ==================== Encapsulation of date/time values. Function Timezones() -------------------- Returns the list of recognized timezone names: >>> from DateTime import Timezones >>> zones = set(Timezones()) Almost all of the standard pytz timezones are included, with the exception of some commonly-used but ambiguous abbreviations, where historical Zope usage conflicts with the name used by pytz: >>> import pytz >>> [x for x in pytz.all_timezones if x not in zones] ['CET', 'EET', 'EST', 'MET', 'MST', 'WET']

zope-Acquisition-devel-2.13.8-3.lbn13.x86_64: Acquisition is a mechanism that allows objects to obtain attributes from the containment hierarchy they're in.

zope-Acquisition-2.13.8-3.lbn13.x86_64: Acquisition is a mechanism that allows objects to obtain attributes from the containment hierarchy they're in.

zope-2.13.22-1.lbn13.x86_64: Zope is an application server framework that enables developers to quickly build web applications such as intranets, portals, and content management systems.

zettwerk.ui-1.1.1-1.lbn13.noarch: Introduction zettwerk.ui integrates jquery.ui's themeroller into Plone 4.1. Themeroller is a tool to dynamically customize the jquery.ui css classes. For details about jquery.ui theming and themeroller see http://jqueryui.com/themeroller/. See it in action: http://www.youtube.com/watch?v=p4_jU-5HUYA Usage With this add-on it is very easy to adapt the look and color scheme of your plone site. After installation, there is a new extension product listed in the plone controlpanel which is called "Zettwerk UI Themer". Use the themes tab to create new themes via themeroller or apply one of the example themes from the themeroller gallery. Note that themeroller is only working in firefox, but the existing themes can be used with all browsers.

zest.releaser-3.43-1.lbn13.noarch: zest.releaser is collection of command-line programs to help you automate the task of releasing a software project. It's particularly helpful with Python package projects, but it can also be used for non-Python projects. For example, it's used to tag buildouts - a project only needs a version.txt file to be used with zest.releaser. It will help you to automate: * Updating the version number. The version number can either be in setup.py or version.txt. For example, 0.3.dev0 (current) to 0.3 (release) to 0.4.dev0 (new development version). * Updating the history/changes file. It logs the release date on release and adds a new section for the upcoming changes (new development version). * Tagging the release. It creates a tag in your version control system named after the released version number. * Uploading a source release to PyPI. It will only do this if the package is already registered there (else it will ask, defaulting to 'no'); the Zest Releaser is careful not to publish your private projects! It can also check out the tag in a temporary directory in case you need to modify it.

zest.pocompile-1.3-2.lbn13.noarch: This package compiles po files. It contains a zest.releaser entry point and a stand-alone command line tool. Goal You want to release a package that has a locales dir (or locale, or something else as long as it has a LC_MESSAGES folder somewhere in it) with translations in .po files. You want to include the compiled .mo files in your release as well, but you do not want to keep those in a revision control system (like subversion) as they are binary and can be easily recreated. That is good. This package helps with that. Want .mo files? Add a MANIFEST.in file. When you use python setup.py sdist to create a source distribution, distutils (or setuptools or distribute or distutils2) knows which files it should include by looking at the information of the revision control system (RCS). This is why in the case of subversion you should use a checkout and not an export: you need the versioning information. (For other RCS or for subversion 1.7+ you currently need to install extra packages like setuptools-git.)

xlhtml-0.5-14.fc18.armv6hl: The xlhtml program will take an Excel 95, or 97 file as input and convert it to HTML. The output is via standard out so it can be re-directed to files or piped to filters or used as a gateway to the internet. pptHtml program converts PowerPoint files to HTML.

xlhtml-0.5-11.fc12.x86_64: The xlhtml program will take an Excel 95, or 97 file as input and convert it to HTML. The output is via standard out so it can be re-directed to files or piped to filters or used as a gateway to the internet. pptHtml program converts PowerPoint files to HTML.

wv2-0.4.1-3.fc13.x86_64: wv is a library which allows access to Microsoft Word files. It can load and parse Word 2000, 97, 95 and 6 file formats. (These are the file formats known internally as Word 9, 8, 7 and 6.) There is some support for reading earlier formats as well: Word 2 docs are converted to plaintext.

wicked-1.1.10-3.lbn13.noarch: wicked is a compact syntax for doing wiki-like content linking and creation in zope and plone

webcouturier.dropdownmenu-2.3.1-2.lbn13.noarch: Overview You will get the dropdown menus for those items in global navigation that have the subitems. Submenus are build based on the same policy as the Site Map, so it will show the same tree as you would get in the Site Map or navigation portlet being in appropriate section. Requires plone.browserlayer to be installed in your site. How it works Dropdown menus are build based on the same policy as the Site Map, so it will show the same tree as you would get in the Site Map or navigation portlet being in appropriate section. This means - no private objects for anonymouses; no objects, excluded from the navigation - exactly the same behavior you would expect from Site Map or navigation portlet.

transmogrify.xmlsource-1.0-2.lbn13.noarch: Simple xml reader for a transmogrifier pipeline

transmogrify.webcrawler-1.2.1-2.lbn13.noarch: A source blueprint for crawling content from a site or local html files. Webcrawler imports HTML either from a live website, for a folder on disk, or a folder on disk with html which used to come from a live website and may still have absolute links refering to that website. To crawl a live website supply the crawler with a base http url to start crawling with. This url must be the url which all the other urls you want from the site start with.

transmogrify.sqlalchemy-1.0.1-2.lbn13.noarch: Feed data from SQLAlchemy into a transmogrifier pipeline

transmogrify.siteanalyser-1.3-2.lbn13.noarch: Transmogrifier blueprints that look at how html items are linked to gather metadata about items. transmogrify.siteanalyser.defaultpage Determines an item is a default page for a container if it has many links to items in that container. transmogrify.siteanalyser.relinker Fix links in html content. Previous blueprints can adjust the '_path' and set the original path to '_origin' and relinker will fix all the img and href links. It will also normalize ids. transmogrify.siteanalyser.attach Find attachments which are only linked to from a single page. Attachments are merged into the linking item either by setting keys or moving it into a folder. transmogrify.siteanalyser.title Determine the title of an item from the link text used.

transmogrify.regexp-0.5.0-1.lbn13.noarch: transmogrify.regexp allows you to use regular expressions and format strings to search and replace key values in a transmogrifier pipeline.


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