PyStemmer provides access to efficient algorithms for calculating a
"stemmed" form of a word. This is a form with most of the common
morphological endings removed; hopefully representing a common
linguistic base form. This is most useful in building search engines
and information retrieval software; for example, a search with stemming
enabled should be able to find a document containing "cycling" given the
query "cycles".
PyStemmer provides algorithms for several (mainly european) languages,
by wrapping the libstemmer library from the Snowball project in a Python
module. It also provides access to the classic Porter stemming algorithm
for english: although this has been superceded by an improved algorithm,
the original algorithm may be of interest to information retrieval
researchers wishing to reproduce results of earlier experiments.
Redet allows the user to construct regular expressions and test them against
input data by executing any of a variety of search programs, editors, and
programming languages that make use of regular expressions. When a suitable
regular expression has been constructed it may be saved to a file. redet stands
for Regular Expression Development and Execution Tool. For each program, a
palette showing the available regular expression syntax is provided. Selections
from the palette may be copied to the regular expression window with a mouse
click. Users may add their own definitions to the palette via their
initialization file. Redet also keeps a list of the regular expressions
executed, from which entries may be copied back into the regular expression
under construction. The history list is saved to a file and restored on
startup, so it persists across sessions. So long as the underlying program
supports Unicode, redet allows UTF-8 Unicode in both test data and regular
expressions
The HTML::Field set of modules creates objects that represent HTML form fields
which try to make it easier to interact with CGI objects, databases, and
HTML::Template objects.
The objective of an HTML::Field object is to know how to write its own HTML,
how to get its value out of a CGI object or from a hash,
how to add their value to a hash suitable for passing into a HTML::Template
or into a SQL::Abstract object, for example, and thus re-use some of the code
which is typically repeated several times in a CGI script.
This bundle includes also HTML::FieldForm, which is a very simple module to
manage sets of HTML::Field objects.
Load, configure, and compose WSGI applications and servers
Paste Deployment is a system for finding and configuring WSGI
applications and servers. For WSGI application consumers it provides a
single, simple function (loadapp) for loading a WSGI application from
a configuration file or a Python Egg. For WSGI application providers
it only asks for a single, simple entry point to your application, so
that application users don't need to be exposed to the implementation
details of your application.
The result is something a system administrator can install and manage
without knowing any Python, or the details of the WSGI application or
its container.
This tool provides code to load WSGI applications and servers from
URIs; these URIs can refer to Python Eggs for INI-style configuration
files. Paste Script provides commands to serve applications based on
this configuration file.
TurboGears 2 is a reinvention of the TurboGears project to take
advantage of new components, and to provide a fully customizable
WSGI (Web Server Gateway Interface) stack. From the beginning
TurboGears was designed to be a Full Stack framework built from
best-of-breed components. New components have been released which
improved on the ones in the original TGstack, and the Python web
world has been increasingly designed around WSGI.
This has enabled a whole new world of reuse, and TG2 is designed
to take advantage of this fact in order to make a framework which
provides easy to use, productive defaults, while still providing
flexibility where it is useful.
TG2 represents a change from some of the components in TurboGears 1,
but we have now invested in a set of components that we think will
continue to be at the center of python web development for years to
come.
Wysiwyg API allows to use client-side editors (a.k.a. WYSIWYG editors) for
editing content in the Drupal CMS. It simplifies installation of editors
and allows you to define which editor to use depending on the input format.
This module replaces all existing editor integration modules and no other
Drupal module is required.
It is capable of supporting any kind of client-side editor as long as there
are support files for it that integrate the external library with Wysiwyg
API. A client-side editor can be a regular HTML-based editor, a
"pseudo-editor" (that just provides buttons to insert HTML markup into a
plain textarea), or even a Flash-based editor. Support for various editor
libraries is built-in.
The Wysiwyg API also allows Drupal modules to register plugins (or
"buttons") for editors.
Having child-tickets is extremely useful when it comes to
managing multiple releases (ie. a single 'bug-report' ticket and
a single 'bug-fix' ticket for each milestone/branch of
development), for managing sub-tasks of an issue and for managing
'bug-fixes' required when developing a new (larger) enhancement.
This plugin modifies the ticket description box and adds a child
ticket listing table and a 'create' button for adding new child
tickets. It has the following features:
It is possible to control in trac.ini the following aspects of
child-ticket creation/viewing:
allow/disallow child-tickets for a certain type of ticket
to define the table headers displayed in the parent ticket
to define a default for the child type to be created
restrict the type of child-tickets
to define which fields are inherited by child-tickets
This is a simple http server for purely static content. You can
use it to serve the content of a ftp server via http for example.
It is also nice to export some files quickly by starting an http
server in a few seconds without editing a config file first.
Features/Design:
================
* single process: select() + non-blocking I/O
* automatically generates directory listings when asked for a
directory (check for index.html available as option), caches
the listings.
* no config file, just a few switches. Try "webfsd -h" for a
list.
* Uses ${PREFIX}/etc/webfsd/mime.types to map file extentions
to mime/types (not included).
* supports keep-alive and pipelined requests.
* serves byte ranges.
* optional logging in common log file format.
The plugin is quite simple - it displays a progressbar showing the percentage
of the time elapsed. Left-clicking on the plugin area opens a menu of available
alarms. After selecting one, the user can start or stop the timer by selecting
start/stop timer entry in the same menu. New alarms are added through the
preferences window. Each alarm is either a countdown or is run at a specified
time. By default a simple dialog pops up at the end of the countdown. The user
can choose an external command to be run as the alarm and may also choose to
have this repeated a specified number of times with a given interval between
repetitions.
Xplore is a powerful and highly configurable Motif file manager with an
Explorer-like user interface. Besides the usual tree and file views, xplore
also has a "shelf", a kind of clipboard inspired by the NeXT file manager, and
a "log" pane for capturing output from launched programs. The builtin
automounter allows you to access special devices in a transparent manner. Files
can be moved and copied using simple mouse operations, and you can execute
type-specific shell commands when a file is opened, used as the target of a
drag and drop operation, or manipulated using popup menus. File types can be
defined in terms of arbitrary filename and MIME type patterns. Full keyboard
navigation is also supported, including an incremental filename search
facility. Last not least, xplore speaks all standard X11 session management
protocols and thus integrates nicely with most popular desktop environments.