Free freespace 2 intro software for linux

XML::SAX::Intro is an Introduction to SAX Parsing with Perl.

XML::SAX is a new way to work with XML Parsers in Perl. In this article well discuss why you should be using SAX, why you should be using XML::SAX, and well see some of the finer implementation details. The text below assumes some familiarity with callback, or push based parsing, but if you are unfamiliar with these techniques then a good place to start is Kip Hamptons excellent series of articles on XML.com.

Replacing XML::Parser

The de-facto way of parsing XML under perl is to use Larry Wall and Clark Coopers XML::Parser. This module is a Perl and XS wrapper around the expat XML parser library by James Clark. It has been a hugely successful project, but suffers from a couple of rather major flaws. Firstly it is a proprietary API, designed before the SAX API was conceived, which means that it is not easily replaceable by other streaming parsers. Secondly its callbacks are subrefs. This doesnt sound like much of an issue, but unfortunately leads to code like:

sub handle_start {
my ($e, $el, %attrs) = @_;
if ($el eq foo) {
$e->{inside_foo}++; # BAD! $e is an XML::Parser::Expat object.
}
}

As you can see, were using the $e object to hold our state information, which is a bad idea because we dont own that object - we didnt create it. Its an internal object of XML::Parser, that happens to be a hashref. We could all too easily overwrite XML::Parser internal state variables by using this, or Clark could change it to an array ref (not that he would, because it would break so much code, but he could).

The only way currently with XML::Parser to safely maintain state is to use a closure:

my $state = MyState->new();
$parser->setHandlers(Start => sub { handle_start($state, @_) });

This closure traps the $state variable, which now gets passed as the first parameter to your callback. Unfortunately very few people use this technique, as it is not documented in the XML::Parser POD files.

Another reason you might not want to use XML::Parser is because you need some feature that it doesnt provide (such as validation), or you might need to use a library that doesnt use expat, due to it not being installed on your system, or due to having a restrictive ISP. Using SAX allows you to work around these restrictions.

Esprit project is a Web-based learning management system, with an emphasis on collaborative work and strong pedagogical scenario.

OpenOffice::OODoc::Intro is a Perl module for an introduction to the Open OpenDocument Connector.

The main goal of the Open OpenDocument Connector (OODoc) is to allow quick application development in 2 areas:

- replacement of old-style, proprietary, client-based macros for intensive and non-interactive document processing;
- direct read/write operations by enterprise software on office documents, and/or document-driven applications.

OODoc provides an abstraction of the document objects and isolates the programmer from low level XML navigation, UTF8 encoding and file compression details. For example:

use OpenOffice::OODoc;
my $document = ooDocument(file => filename.odt);
$document->appendParagraph
(
text => Some new text,
style => Text body
);
$document->appendTable("My Table", 6, 4);
$document->cellValue("My Table", 2, 1, "New value");
$document->save;

The script above appends a new paragraph, with given text and style, and a table with 6 lines and 4 columns, to an existing document, then inserts a value at a given position in the table. It takes much less time than the opening of the document with your favourite text processor, and can be executed without any desktop software connection. A program using this library can run without any OpenOffice.org installation (and, practically, OODoc has been tested on platforms where OpenOffice.org is not available yet).

More generally, OpenOffice::OODoc provides a lot of methods (probably most of them are not useful for you) allowing create/search/update/delete operations with document elements such as:

- ordinary text containers (paragraphs, headings, item lists); - tables and cells; - sections; - images; - styles; - page layout; - metadata (i.e. title, subject, and other general properties).

Battles of Antargis is a realtime strategy game. Battles of Antargiss main purpose lies on conquering not on building.
Battles Of Antargis is an open-source game with GPL license. You have one or more heroes that you can control. They can recruit troops and conquer the world. While doing this they have to gather food and weapons. All around are people and animals which populate the world.
Unlike the typical Warcraft-like games, you have to get by with the existing population and resources.
This is a first tech-demo, so please be patient. Apart from this we are searching for new artists and developers.
Main features:
Visuals:
- animated milkshape models (MilkShape ASCII-importer)
- static models (Wavefront obj-importer)
- shadowmap based shadows (PSMs work in progress)
- fustrum culling
- shader support
Game
- the whole gamelogic is done in ruby, so it should be fairly easy to modify this game.
- the whole layout is done in xml
- basic dialogs and intro-screens implemented, but nice graphics still missing
- loading/saving
Editor
- edit heightmap
- place entities on map

KDirStat is a graphical disk usage utility, very much like the Unix "du" command.
KDirStat project displays a directory tree both in classical tree format (like Konqueror, but with accumulated tree sizes, shown as MB / GB and as percentage bars) and in "treemap" format like SequoiaView.
In addition to that, KDirStat provides cleanup facilities to reclaim disk space - both predefined and customizable.
Main features:
Display Features
- Graphical and numeric display of used disk space
- Files kept apart from directories in separate items to prevent cluttering the display
- All numbers displayed human readable - e.g., 34.4 MB instead of 36116381 Bytes
- Different colors in the directory tree display to keep the different tree levels visually apart
- Display of latest change time within an entire directory tree - you can easily see what object was changed last and when.
Treemap Display
- Treemap as alternate (auxiliary) view of a directory tree
- Easily find large in a directory tree: You see the entire tree at once. Large rectangles are large files - you can see them even if they are hidden somewhere deep within the tree.
- Treemap view slaved to the tree (list) view: Click on a file in the treemap, and it is selected in the tree view - and vice versa.
- Treemap tiles are colored by file type - all images in cyan, all audio tracks (MP3 etc.) in yellow, executables in magenta etc.; you can see from the color what a treemap rectangle is.
- Many treemap variants available:
- Plain treemap
- Squarified treemap (no thin elongated rectangles)
- Cushion treemap
- Colored treemap
- All combinations of the above
- Fast implementation: Treemap built in fractions of a second (on quite ordinary machines: Athlon-550 class)
- Treemap subwindow can be resized as the user prefers
- Treemap can be switched off with a single keypress (F9)
- Context menu with cleanup actions etc.
- Zoom the treemap in/out treemap with double click (left/right)
- Many treemap configuration options
Directory Reading
- Stays on one file system by default - reads mounted file systems only on request.
- You dont care about a mounted /usr file system if the root file system is full and you need to find out why in a hurry, nor do you want to scan everybodys home directory on the NFS server when your local disk is full.
- Network transparency: Scan FTP or Samba directories - or whatever else protocols KDE support.
- PacMan animation while directories are being read. OK, this is not exactly essential, but its fun.
Cleaning up
- Predefined cleanup actions: Easily delete a file or a directory tree, move it to the KDE trash bin, compress it to a .tar.bz2 archive or simply open a shell or a Konqueror window there.
- User-defined cleanup actions: Add your own cleanup commands or edit the existing ones.
- "Send mail to owner" report facility: Send a mail requesting the owner of a large directory tree to please clean up unused files.
Misc
- Feedback mail facility: Rate the program and tell the authors your opinion about it.
Whats New in 2.4.4 Release:
- Sparse files and hard links are now properly supported.
Whats New in 2.5.2 Release:
- Can now read and write directory contents from cache files generated by (supplied) Perl script, e.g. in cron job over night

Mbedthis AppWeb is the leading web server technology for embedding in devices and applications. It is an open source, feature rich, embedded web server that has been designed from the ground up with security in mind.
It is integrated directly into embedded systems and applications for simple and convenient deployment and with features such as server side Embedded JavaScript and Embedded Server Pages, AppWeb is in a league of its own when compared with other embedded web servers.
AppWeb is also highly efficient. It has a modular architecture that results in a very small memory footprint and minimal CPU requirements. Compared to other web servers, AppWeb consumes a fraction of the resources that other servers require.
It also offers superior security and provides the easiest way to create dynamic, web based user and management interfaces.
Top Uses for AppWeb
- Embedded Device Management
- Personal Web Servers
- Web enabling Enterprise Applications
- Create a CD of your web site including a local web server
- Diagnostic web based user interfaces for Applications
- Create offline web applications
Enhancements:
- This release migrates the development release to a stable designation.
- Major features over the previous 2.0.5 stable release include: upgraded support for the latest PHP, MatrixSSL, and OpenSSL; a native Debian/Ubuntu package; and FSH conformance.
- Builds have been optimized to be twice as fast. 64-bit support has been improved. configure is more flexible.
- There are fixes for ranged requests, single threaded operation, and putHandler.
- The build system has been reworked.