Free api2 0.53 software for linux

PDF::API2 is The Next Generation of Text::PDF::API, a Perl module-chain that facilitates the creation and modification of PDF files.
It features support for the 14 base PDF Core Fonts, TrueType fonts, and Adobe-Type1, with unicode mappings, embedding of bitmap images, compression via zlib, and a rich object-oriented API.
Main features:
- Works with more than one PDF file open at once
- It presents a object-oriented API to the user
- Modification of existing PDF Documents
- Import Pages from existing PDF Documents
- the 14 base PDF Core Fonts
- a subset of the base PDF CJK Fonts
- a subset of the Microsoft Webfonts (not embedded)
- Adobe-Type1 Fonts in both ascii and binary format (.pfa/pfb)
- TrueType fonts (.ttf)
- OpenType Fonts with TrueType Outlines (.ttf)
- OpenType Fonts with Postscript Outlines (.otf)
- Joint Photographics Experts Group images (.jpeg)
- Portable Network Graphics images (.png)
- Graphics Interchange Format images (.gif)
- Tagged Image File Format images (.tiff)
- Portable AnyMap images (.pbm/pgm/ppm)

Otk is a portable widget library for making graphical user interfaces (GUIs) for application programs. Otk project emphasizes simplicity without eliminating capability. Open graphics Tool Kit supports neutrally: Linux, Unix, Microsoft Windows, and Mac OSX. It is based on OpenGL, and C. Otk provides the following basic widgets:
- Panel - The "container" widget.
- Text Label - Text labels.
- Button - Buttons with labels and call-backs to user functions.
- Text Form Box - Accept text with function call-back. Also scrollable editor window.
- Pull-down Menu - Display hierarchical menu-lists with user function call-backs on mouse release.
- Slider Control - Slider control with call-back.
- Sub-windows - Detachable self-managed windows.
- Many other widgets ...
- Gadgets - High level widgets.
Although initially intended for use with C programs, Otk can be accessed from, or extended to, other languages. Otk addresses several issues with previous graphics toolkits, such as X-Windows, X-Motif, MFC, Tcl/TK, Gtk, Awt, Swing, Glow, FLTK, etc..
Otk deviates from previous graphics environments in several important ways.
- Based on OpenGL - Well supported on most platforms. Clients tend to have the right support files. Easily builds on all platforms. Uses graphics card acceleration when available. Common look and feel. Contains internal default font with arbitrary scale, boldness and slant. Additional fonts can be added.
- API designed from application programmers viewpoint - Simplified interface. Sensible defaults. Most common functions require one line. But flexibility is not limited because defaults can be modified.
- Minimal library files - Link to-, or include-, one file.
- Direct window-size % relative layout - Specify positions and sizes as percentage of container window. Resizing is automatic and proportional. Traditional pixel-coordinate or framework modes can also be supported.
- Colors can be expressed directly as r,g,b values. (No indirect color index tables.)
Enhancements:
- Paste from the clipboard was added.
- A fix was mde to disk-draw for elliptical disks and the control-key handler.
- The slider knob was widened.
- A new indicator-light gadget was started.
- Several updates were made to support Otk-GuiBuilder.

a2pdf project converts ASCII text to PDF format, with optional line/page numbering and Perl syntax highlighting.

Usage:

a2pdf [options] input.txt >output.pdf

Options:

a2pdf recognises the following command line options:

--help
Prints usage details and exits.

--doc
Displays full documentation and exits.

--version
Prints version number and exits.

--title
Sets the title to be included in the page header. If unspecified, the title will default to the name of the file which is being converted, or to STDIN if a2pdf is processing from standard input.

--timestamp
Boolean option - if set, the timestamp of the file to be converted will be included in the page header. This option is turned off by default.

--icon
Path to an image file which will be included as part of the header in the top left of each page. Image files may be in any format supported by PDF::API2.

--icon-scale
Scaling value for icon images, default is 0.25.

--header | --noheader | --notitle
Prints a header consististing of the page title, and optionally the timestamp and an image icon at the top of each page. This option is enabled by default, use "--notitle" or "--noheader" to disable.

--footer | --nofooter | --page-numbers | --nopage_numbers
Adds the current page number to the bottom of each page. This is enabled by default, use --nofooter or --nopage-numbers to disable.

--line-numbers | --noline-numbers
By default, line numbers will be included in the output PDF file. To disable this behaviour, use the --noline-numbers option.

--perl-syntax | --noperl-syntax
Enables or disables (default is enabled) Perl syntax highlighting. This feature requires that the Perl::Tidy module is installed.

--page-height
Page height in points. Default is 842 (A4).

--page-width
Page with in points. Default is 595 (A4).

--margins
--left-margin
--right-margin
--top-margin
--bottom-margin
Specifies the non-printable area of the page. The margin option will set all margins to the same value, however individual margins may be altered with the appropriate options. Values must be given in points. The default value for all margins is 48 points (0.75").

--font-face
Sets the font to use for the PDF file - currently this must be one of the PDF core fonts. The default font face is Courier.

--font-size
Font size in points, default value is 10.

--line-spacing
Line spacing in points, default value is the font size + 2.

--noformfeed
By default, any formfeed characters in the input stream will be processed and will act as expected, i.e. a new page will be started in the output PDF file. This can be disabled with the "--noformfeed" option which will cause all formfeed characters to be ignored.

Options may be given in any format recognised by the Getopt::Long Perl module, e.g. --name=value or --name value. Option names may be abbreviated to their shortest unique value.

If the input filename is not given, then a2pdf will expect to receive input from STDIN.

mcl project is a MUD client for Linux.
mcl is a MUD client running in a Virtual Console under Linux or using standard TTY routines under any other UNIX.
Embedded Perl or Python offer very high tweakability. Other features include huge scrollback, a stable input line with the MUD prompt, Perl regexps for actions and substitutions.
Main features:
- Runs under Virtual Console in Linux (fast) or under a TTY (slower, but works under any UNIX and xterms)
- Color scrollback buffer, the size of which is limited only by available memory.
- Telnet GA support - prompt and input line are at the bottom, and the prompt is not displayed in the main window.
- Command history - press arrow up to get a window with the last commands which you can scroll through using standard navigation keys.
- Aliases - tintin style, multiple commands per alias, aliases can call other aliases.
- Automatic login - specify commands to be run on connect to remote server (e.g. name and password).
- Stable ANSI color code support: if an ANSI color code is received broken in two packets (as it often happens to me on a color-heavy MUD on a PPP connection) the color code is reassembled and displayed correctly.
- Windows that display output from commands (e.g. traceroute, finger).
- Windows that you can print to using built-in commands: useful for e.g. logging all tells to a separate window.
- Actions using regular expressions as well as substitutions using Perls powerful regexp library
- Macro keys - key e.g. Keypad 8 to send "north"
- User interface is fairly configurable (done using a text file).
- Embedded Perl or Python support for scripting (embedded interpreter modules are dynamically loaded)
- Supports the MCCP compression standard
- Partial support for the zChat and MudMaster peer-to-peer chat protocols
Enhancements:
- Generally fixups for compilation with modern gcc

Class::Meta::Type is a Perl module for data type validation and accessor building.

SYNOPSIS

package MyApp::TypeDef;

use strict;
use Class::Meta::Type;
use IO::Socket;

my $type = Class::Meta::Type->add( key => io_socket,
desc => IO::Socket object,
name => IO::Socket Object );

This class stores the various data types used by Class::Meta. It manages all aspects of data type validation and method creation. New data types can be added to Class::Meta::Type by means of the add() constructor. This is useful for creating custom types for your Class::Meta-built classes.

Note:This class manages the most advanced features of Class::Meta. Before deciding to create your own accessor closures as described in add(), you should have a thorough working knowledge of how Class::Meta works, and have studied the add() method carefully. Simple data type definitions such as that shown in the SYNOPSIS, on the other hand, are encouraged.

Apache::WeSQL::Display is a library of functions to create web-pages based on a Journalled SQL database.

SYNOPSIS

use Apache::WeSQL::Display qw( :all );

This module contains the functions necessary to deal with the jform.wsql, jdetails.wsql, and jlist.wsql web calls. These calls read their configuration from the form.cf, details.cf, and list.cf files. Also, they use certain (see LAYOUT.CF below to know which) entries from the layout.cf file for the layout. The structure of the .cf files is outlined below.

.CF FILES

STRUCTURE

The .cf files (except for layout.cf, see below) have the following syntax:
< view-name >
< key >:< value >
< value_line2 >
< key >:< value >
< value_line2 >
< value_line3 >
...

< view-name >
< key >:< value >
...
Multi-line values are allowed as long as the extra lines begin with whitespace. Of course they can not be all whitespace, or they would be seen as a view separator!

Overnet is the distributed search network that the donkey uses to find files. It was a standalone application but we have now EDonkey and overnet are the same application.
Main features:
- Elegant easy to use interface
- International versions. Now available in many languages
- Share and Download any type of file.
- Downloads are automatically continued from session to session.
- Completely distributed and self organizing network. No central servers.
- Horde Anti-leeching system (see side bar)
- Multiple source downloads. Download a file from several different users at once.
- Network wide searches (see side bar)
- Support for other download protocols such as http and bittorrent
- Private messaging
- Simultaneous uploading and downloading of the same file. Providing the fastest distribution of files possible.
- Dynamic ports. eDonkey can be configured to run over any port.
- Plugin System
- Skins
- ed2k links. You can embed links in webpages that will initiate downloads within eDonkey.
- Statistics. Keep track of how much your client is sending and receiving
- Multiple search tab interface
- Automatic fake file detection
- Catalogs. Allow you to verify content before you download it. They are like distributed web pages.
Enhancements:
- Create all new files in 00644 mode (no need to make them executable)

XML::SimpleObject is a Perl extension allowing a simple object representation of a parsed XML::Parser tree.

SYNOPSIS

use XML::SimpleObject;

# Construct with the key/value pairs as argument; this will create its
# own XML::Parser object.
my $xmlobj = new XML::SimpleObject(XML => $XML, ErrorContext => 2);

# ... or construct with the parsed tree as the only argument, having to
# create the XML::Parser object separately.
my $parser = new XML::Parser (ErrorContext => 2, Style => "Tree");
my $xmlobj = new XML::SimpleObject ($parser->parse($XML));

my $filesobj = $xmlobj->child("files")->child("file");

$filesobj->name;
$filesobj->value;
$filesobj->attribute("type");

%attributes = $filesobj->attributes;
@children = $filesobj->children;
@some_children = $filesobj->children("some");
@chilren_names = $filesobj->children_names;

This is a short and simple class allowing simple object access to a parsed XML::Parser tree, with methods for fetching children and attributes in as clean a manner as possible. My apologies for further polluting the XML:: space; this is a small and quick module, with easy and compact usage. See XML::SimpleObject::LibXML for the same interface for XML::LibXML.

USAGE

$xmlobj = new XML::SimpleObject($parser->parse($XML))

$parser is an XML::Parser object created with Style "Tree":

my $parser = new XML::Parser (ErrorContext => 2, Style => "Tree");
After creating $xmlobj, this object can now be used to browse the XML tree with the following methods.

$xmlobj->child(NAME)

This will return a new XML::SimpleObject object using the child element NAME.

$xmlobj->children(NAME)

Called with an argument NAME, children() will return an array of XML::SimpleObject objects of element NAME. Thus, if $xmlobj represents the top-level XML element, children will return an array of all elements directly below the top-level that have the element name NAME.

$xmlobj->children

Called without arguments, children() will return an array of XML::SimpleObject s for all children elements of $xmlobj. These are not in the order they occur in the XML document.

$xmlobj->children_names

This will return an array of all the names of child elements for $xmlobj. You can use this to step through all the children of a given element (see EXAMPLES). Each name will occur only once, even if multiple children exist with that name.

$xmlobj->value

If the element represented by $xmlobj contains any PCDATA, this method will return that text data.

$xmlobj->attribute(NAME)

This returns the text for an attribute NAME of the XML element represented by $xmlobj.

$xmlobj->attributes

This returns a hash of key/value pairs for all elements in element $xmlobj.