Free water features for the garden software for linux

The amaroK bindings for Python is a fairly complete amaroK remote control class. It is extremely useful for amaroK scripts and other applications. Basically, you can remote control amaroK by calling methods from an amaroKProxy instance.

In addition, it implements the Observer/Observable pattern so you can deal with events in an object-oriented, loosely coupled fashion. Even better, you can call an amaroKProxy instances collection.getSong(filename) method to get a Song object, with track, artist, album name, and elegant "Artist - Track name" strings.

Nearly all DCOP functions for communication with amaroK are implemented.

It will use KDE bindings DCOP module if available, otherwise it will default to the command-line DCOP dcop command, through python-commandsplus. If using KDE bindings, a slave process is spawned, and IPC is used to marshal and unmarshal function calls, so as to not contaminate your applications sys.modules with KDEs Python modules. This all happens automatically in the background.

To use it, you import the module in your script and instantiate an amaroKProxy instance, then call your instances startMonitoring() method, which will start reading from standard input, monitoring for amaroKs events. You can then sleep(1) until your instances .isAlive() method returns False (which means amaroK is now gone.

amaroKProxy is an Observable class, and so are its members:

- player
- contextBrowser

This means that you can implement Observer objects or Threads in your amaroK script, and have them be notified of amaroK events, instead of having to read standard input and act accordingly (plus error-prone exceptional condition handling).

Packet Garden is a project that allows you to grow a world from network traffic.

Packet Garden captures information about how you use the internet and uses this stored information to grow a private world you can later explore.

To do this, Packet Garden takes note of all the servers you visit, their geographical location and the kinds of data you access.

Uploads make hills and downloads valleys, their location determined by numbers taken from internet address itself.

The size of each hill or valley is based on how much data is sent or received.

Plants are also grown for each protocol detected by the software; if you visit a website, an HTTP plant is grown. If you share some files via eMule, a Peer to Peer plant is grown, and so on.

The Battle for Wesnoth is a turn-based strategy (TBS) game with a fantasy theme.
Build your army, selecting, from one mission to the next one, your most experienced fighters. Fighters you did recruit among a great number of units, offering various strategic strengths and weaknesses on different terrains and against different opponents.
Fight to gain back the throne of Wesnoth, of which you are the legitimate heir. Or use your dreaded power on undead to achieve domination on those foul mortals, or get a revenge for your glorious orcish tribe against these puny human armies who dared stealing your land... stories are waiting to be told. Or maybe you want to challenge your friends or strangers on multiplayer epic fantasy battles.
Main features:
- Build a Hero, and lead your army.
- Different races, with distinctive abilities, weapons and spells.
- GNU/Linux, Windows, MacOSX, BeOS, Solaris, FreeBSD, OpenBSD and NetBSD compatible.
Whats New in 1.2.6 Stable Release:
- WML engine
- fix [variables] not working properly in scenarios (bug #9342)
- language and i18n:
- updated translations: British English, Danish, Finnish, Spanish, Swedish
- updated DejaVuSans font to version 2.18
- user interface:
- Enable "Save Game" and "View Chat Log" menu entries in replay mode.
- Add an additional line below the minimap in the "Multiplayer->Create game"
screen that displays the size of the selected map. (patch #776 by uso)
- Show the (possibly bogus) GPV and fog settings of games with "Use map
settings" on in a darker font. (patch #771 by uso)
- misc:
- added some extra headers for the upcomming gcc 4.3 (debian bug #417764)
- added a .desktop entry for the editor so that it is shown in the kde/gnome
menu
- the unit name generation could with different locales call get_random() a
different number of times. This lead to different names and traits.
Changed to call random a fixed number of times which fixes the traits.
Whats New in 1.3.6 Development Release:
- Since 1.3.5 was a little buggy, now the new version with definatly working minimaps in the lobby. More important: long standing, translation related OOS bugs have been fixed

The TagMogrifier library for PHPs goal is to let you perform fast and easy-to-program transformations on XML documents. Instead of having to write your own parser, or directly using the PHP DOM parser, and having to write your own tree walker and such, you only need to instantiate a class, add a few match expressions, and assign a function to process every XML element that matches, DOM-style.

Do you work with PHP and XML often? If you do, you’ve probably noticed it’s very tedious to manipulate XML from PHP. Be it regular expressions, tree walking of DOM nodes, or SAX, all of these alternatives are hard work.

The purpose of this library is to let you perform fast and easy-to-program transformations on XML documents. Instead of having to write your own parser, or directly using the PHP DOM parser, and having to write your own tree walker and such, you only need to instantiate a class, add a few match expressions, and assign a function to process every XML element that matches, DOM-style.

zengarden is a tool that watches over the installation and building of source archives. It is a fork of installwatch that has been heavily updated with modern features.
It can prevent build tools from interfering with files outside the build directory and create a virtual chroot to perform installations in or backup the files the install overwrites.
Installation
Installwatch has been tested on Linux only.
Before compiling, you can edit the Makefile and change the PREFIX variable. Common values are `/usr and `/usr/local.
To compile it, a simple `make followed by `make install should do the magic.
You need an ELF system, but I dont think its a problem today...
If you want to try installwatch on itself for the first time, do the following instead of `make install.
Bash family:
LD_PRELOAD=./installwatch.so make install
Tcsh family:
setenv LD_PRELOAD ./installwatch.so ; make install
Of course, you must be root in the installwatch source directory.
Remember, if you belong to the tcsh family, LD_PRELOAD will remain set after `make install, so be sure to clear the variable.
Enhancements:
- autoolized - at least for the most part
- minor bug fixes
- viewcvs (not really a feature in the tarball) - thx to sofar

Gimp::Feature is a Perl module that can check for specific features to be present before registering the script.

SYNOPSIS

use Gimp::Feature;
or
use Gimp::Feature qw(feature1 feature2 ...);

This module can be used to check for specific features to be present. This can be used to deny running the script when neccessary features are not present. While some features can be checked for at any time, the Gimp::Fu module offers a nicer way to check for them.

gtk

checks for the presence of the gtk interface module.

gtk-1.1, gtk-1.2

checks for the presence of gtk-1.1 (1.2) or higher.

perl-5.005

checks for perl version 5.005 or higher.

pdl

checks for the presence of a suitable version of PDL (>=1.9906).

gnome

checks for the presence of the Gnome-Perl module.

gtkxmhtl

checks for the presence of the Gtk::XmHTML module.

unix

checks wether the script runs on a unix-like operating system. At the moment, this is every system except windows, macos, os2 and vms.

persistency

checks wether the Gimp::Data module (Gimp::Data) can handle complex persistent data structures, i.e. perl references in addition to plain strings.

The following features can only be checked after Gimp-main> has been called (usually found in the form exit main). See Gimp::Fu on how to check for these.
gimp-1.1, gimp-1.2

checks for the presense of gimp in at least version 1.1 (1.2).

FUNCTIONS

present(feature)

Checks for the presense of the single feature given as the argument. Returns true if the feature is present, false otherwise.

need(feature,[function-name])

Require a specific feature. If the required feature is not present the program will exit gracefully, logging an appropriate message. You can optionally supply a function name to further specify the place where this feature was missing.

This is the function used when importing symbols from the module.

missing(feature-description,[function-name])

Indicates that a generic feature (described by the first argument) is missing. A function name can further be specified. This function will log the given message and exit gracefully.

describe(feature)

Returns a string describing the given feature in more detail, or undef if there is no description for this feature.

list()

Returns a list of features that can be checked for. This list might not be complete.