Ports Search

The symon project consists of three parts; a data monitor, a data consolidator and a data displayer. symon is a is a lightweight system monitor that measures cpu, memory, pf, interface and disk statistics every 5 seconds. It sends this data on to symux for further processing. symon has been designed to inflict minimal performance and security impact -- it can be run as nobody on the system it monitors. symux is a non-privileged daemon that listens to incoming symon traffic. symux can write the incoming symon streams into rrd files. Clients interested in monitoring machine state can also log into symux and receive data as ascii as it arrives.

Data::Report is a flexible, plugin-driven reporting framework. The Data::Report framework consists of three parts: - the plugins Plugins implement a specific type of report. Standard plugins provided are Data::Report::Plugin::Text for textual reports, Data::Report::Plugin::Html for HTML reports, and Data::Report::Plugin::Csv for CSV (comma-separated) files. - the base class The base class Data::Report::Base implements the functionality common to all reporters, plus a number of utility functions the plugins can use. - the factory The actual Data::Report module is a factory that creates a reporter for a given report type by selecting the appropriate plugin and returning an instance thereof.

The Text::Striphigh module exports a single function: C<striphigh>. This function takes one argument, a string possibly containing high ASCII characters in the ISO-8859-1 character set, and transforms this into a string containing only 7 bits ASCII characters, by substituting every high bit character with a similar looking standard ASCII character, or with a sequence of standard ASCII characters. Because of precisely the deficiency this package tries to offer a workaround for is present in some of the things that process pod, there are no examples in this manpage. Look at the source or the test script if you want examples. Kai Storbeck kai@xs4all.nl

denature is a perl program that attempts to convert an HTML page into XSL-FO which it then passes off to the FOP (Formatted Objects Formatter) to produce a PDF document. denature trys to use any included CSS stylesheets to figure out the properties used in the document. The CSS processing in denature is not very mature and only handles a limited amount of the available CSS markup. The CSS support does not handle the contextual entries in a CSS document, and the CSS::Tiny module requires that all the :'s in a document have a space after them.

Universal Feed Parser is a Python module for downloading and parsing syndicated feeds. It can handle RSS 0.90, Netscape RSS 0.91, Userland RSS 0.91, RSS 0.92, RSS 0.93, RSS 0.94, RSS 1.0, RSS 2.0, Atom 0.3, Atom 1.0, and CDF feeds. Universal Feed Parser is easy to use; the module is self-contained in a single file, feedparser.py, and it has one primary public function, parse. parse takes a number of arguments, but only one is required, and it can be a URL, a local filename, or a raw string containing feed data in any format.

A Python utilities collection for building WSGI applications. Werkzeug does not try to be a framework, and instead started as a simple collection of various utilities useful for building WSGI applications. It has since become one of the most advanced collections of its kind. It includes a powerful debugger, fully featured request and response objects, HTTP utilities to handle entity tags, cache control headers, HTTP dates, cookie handling, file uploads, a powerful URL routing system and a bunch of community contributed add-on modules.

This class works just like LWP::UserAgent (and is based on it, by being a subclass of it), except that when you use it to get a web page but run into a possibly-temporary error (like a DNS lookup timeout), it'll wait a few seconds and retry a few times. It also adds some methods for controlling exactly what errors are considered retry-worthy and how many times to wait and for how many seconds, but normally you needn't bother about these, as the default settings are relatively sane.

Apache AXIS is an implementation of the SOAP ("Simple Object Access Protocol") submission to W3C. From the draft W3C specification: SOAP is a lightweight protocol for exchange of information in a decentralized, distributed environment. It is an XML based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined datatypes, and a convention for representing remote procedure calls and responses.

Glade is a free user interface builder for GTK+ and GNOME. After designing a user interface with glade-2 the layout and configuration are saved in an XML file. libglade is a library which knows how to build and hook up the user interface described in the Glade XML file at application run time. This extension module binds libglade to Perl so you can create and manipulate user interfaces in Perl code in conjunction with Gtk2 and even Gnome2. Better yet you can load a file's contents into a PERL scalar do a few magical regular expressions to customize things and the load up the app. It doesn't get any easier.

Tk::Role::Dialog is meant to be used as a Moose role to be composed for easy Tk dialogs creation. It will create a new toplevel with a title, and possibly a header as well as some buttons. One can create the middle part of the dialog by providing a _build_gui() method, that will receive a Tk::Frame where widgets are supposed to be placed. The attributes (see below) can be either defined as defaults using the _build_attr() methods, or passed arguments to the constructor call. The only mandatory attribute is parent, but you'd better provide some other attributes if you want your dialog to be somehow usable! :-)