Free water features software for linux

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.

KAdventure is a nice and simple adventure game providing fun and challenging puzzles. The player is presented with a 2D view from above a playing field, where he has to move his player to the exit.
To get to the exit he has to overcome several obstacles, like walls, moving blocks, water and creatures.
I encourage anyone to create new levels using the new level editor, or even new objects and artwork.
Finally, if someone manages to create a Windows port hes welcome as well.
Version restrictions:
- Clicking Save Level immediately saves the current level, and will overwrite the old level without warning.
- Saving levels only works when the level files are writable. So you should have installed in your home directory or made the directory with the levels writable. No warning is given when saving fails.
- Pressing +/- to change the resolution has some redrawing issues in Edit mode. You can minimize and re-open the window to get a correct redraw.
- If you have changed the size of a level, you need to save and reload the level for the new size to take effect.
Enhancements:
- Fixed the crash when a mine exploded.
- Some small fixes and tidying up.
- Added 2 small new levels.

Lingua::Phonology::Features is a module to handle a set of hierarchical features.

SYNOPSIS

use Lingua::Phonology;

my $phono = new Lingua::Phonology;
my $features = $phono->features;

# Add features programmatically
$features->add_feature(
Node => { type => privative, children => [Scalar, Binary, Privative] },
Scalar => { type => scalar },
Binary => { type => binary },
Privative => { type => privative }
);

# Drop features
$features->drop_feature(Privative);

# Load feature definitions from a file
$features->loadfile(phono.xml);

# Load default features
$features->loadfile;

Lingua::Phonology::Features allows you to create a hierarchy of features of various types, and includes methods for adding and deleting features and changing the relationships between them.

By "heirarchical features" we mean that some features dominate some other features, as in a tree. By having heirarchical features, it becomes possible to set multiple features at once by assigning to a node, and to indicate conceptually related features that are combined under the same node. This module, however, does not instantiate values of features, but only establishes the relationships between features.

Lingua::Phonology::Features recognizes multiple types of features. Features may be privative (which means that their legal values are either true or undef), binary (which means they may be true, false, or undef), or scalar (which means that their legal value may be anything). You can freely mix different kinds of features into the same set of features.

Finally, while this module provides a full set of methods to add and delete features programmatically, it also provides the option of reading feature definitions from a file. This is usually faster and more convenient. The method to do this is "loadfile". Lingua::Phonology::Features also comes with an extensive default feature set.

Deep-Water Linux is a half minimalist software distribution using the linux kernel released under the terms of the gnu gpl license v2.

Originaly i designed it for myself to make my work a bit easyer - it was a few years ago when there were not so many live distributions that fit my needs - i needed something more than "minimal" but not something that would need more than 2-3 minutes to load requireing hardware, that i couldnt afford.

So i designed a small system for myself that i could use whenever i broke my "harddisk" distro so much, that it was impossible to repair the system from inside of it. I started using the system as a sort of a rescue system and i installed it on my computer as a sort of a neighbour to other systems that i have used.

Then i thought other people might find it interesting, if not as a whole, than atleast a part of it, or maybe they might like to use it for some "rescue job". I was messing arround with xlib and tcl/tk, so i added some programs to ease a users life - like a panel, icons, file-manager. You see, i thought it is stupid to just copy someones work and then re-distribute it in my name - i hate the kind of distros where the "developers" just change the background of some well known distro and then give it a new name.

In my distro you wont find so many tools, it evean might not work good, it evean can make you angry "make you laugh, or cry", but atleast i can say, that many things in this system is my work - i programmed deep-panel/ deep-view/ deep-icons/ made a new hackedbox"a hack of blackbox"/designed the startup and many other things.

There are 2 version-types of the distro - the first copying the whole system in the memmory and the second copying only a part of itself - the first is for people with older hardware with little memmory and the second for boxes with memmory atleast 128MB. I know that there are many systems out there that are better and im not saying that its good to use this distro on an everyday basis, but if you find some inspiration in it, or if you use it as a rescue system, or want to use deep-view to browse/edit some files or to display image galleries and your "real" system is broke, if you find any use of it than im happy enough.

Bio::DB::GFF::Feature is a relative segment identified by a feature type.

Bio::DB::GFF::Feature is a stretch of sequence that corresponding to a single annotation in a GFF database. It inherits from Bio::DB::GFF::RelSegment, and so has all the support for relative addressing of this class and its ancestors. It also inherits from Bio::SeqFeatureI and so has the familiar start(), stop(), primary_tag() and location() methods (it implements Bio::LocationI too, if needed).

Bio::DB::GFF::Feature adds new methods to retrieve the annotations type, group, and other GFF attributes. Annotation types are represented by Bio::DB::GFF::Typename objects, a simple class that has two methods called method() and source(). These correspond to the method and source fields of a GFF file.

Annotation groups serve the dual purpose of giving the annotation a human-readable name, and providing higher-order groupings of subfeatures into features. The groups returned by this module are objects of the Bio::DB::GFF::Featname class.

Bio::DB::GFF::Feature inherits from and implements the abstract methods of Bio::SeqFeatureI, allowing it to interoperate with other Bioperl modules.
Generally, you will not create or manipulate Bio::DB::GFF::Feature objects directly, but use those that are returned by the Bio::DB::GFF::RelSegment->features() method.
Important note about start() vs end()

If features are derived from segments that use relative addressing (which is the default), then start() will be less than end() if the feature is on the opposite strand from the reference sequence. This breaks Bio::SeqI compliance, but is necessary to avoid having the real genomic locations designated by start() and end() swap places when changing reference points.

To avoid this behavior, call $segment->absolute(1) before fetching features from it. This will force everything into absolute coordinates.

For example:

my $segment = $db->segment(CHROMOSOME_I);
$segment->absolute(1);
my @features = $segment->features(transcript);

WorldForge::Mason is the second game system being developed by WorldForge. The primary focus for Mason is to enable players to build a persistent world in-game. Players will be able to manipulate items by creating new items from raw materials, attaching existing items together or splitting items into component parts.
Complicated structures such as houses can be designed on paper as a blueprint and then built with suitable building blocks and skills.
Reaching this milestone will require expanding not only our existing server and client code, but also refining the Atlas protocal that connects them.
The expansion will cover item creation (using a recipe system), construction of houses and other large structures (attaching items together), creating complex machines (combining simple machine parts), simulating organic reactions (festering wounds, adrenaline rush) with a detailed body system, editing text and other information objects in-game, and running an economy that changes with the world.
To demonstrate these techniques we will create a competitive and cooperative game centering about settling the uninhabited lands in the north-western corner of Moraf in our Dural world.
The players can play either human settlers attracted by the rumors of gold or promises of free land, or orcs, driven down to the plains from the overpopulated dens of the orc tribes of Sarnak.
Game
This section contains things related to the Mason Game in general, such as background story, game objectives, and planned features for version 1.0 of the game. It will also contain an installation guide, a players guide, and a game administrators guide. Theres also a page of links to screenshots and downloads.
If you are a potential future player and would like to know what the game will be like, or a creative writer interested in making the game interesting and fun to play, or if you want to write or translate documentation for end users, then this is the place for you.
Technology
This section contains the design of the various abstract systems that will implement all the central features of Mason. The systems include: the Item System, the Mechanical System, the Information Object System, the Body System, the Mind System, and others.
If you are a developer or game designer, interested in how all the revolutionary features supported by Mason are going to be implemented, then this section is for you.
Content
This section deals with all the general data needed for the Mason Game: item and creature descriptions and stats, maps of the Moraf area in the Dural world, and media for items and terrain. This data can be directly reused in later games.
If you are a world designer, artist, musician, or a MU* wizard who loves creating cool new items, then this section is for you.
Enhancements:
- Mason is now supported in two major 3D clients, Ember and Sear.
- An advanced terrain system has been implemented, including procedural texturing, paths, modified areas, and swimming in water.
- Building materials and resources can be gathered from the world using tools.
- Work has started on a new combat system.

Perilar is a simple, fast computer role-playing game (CRPG), with an epic quest! You will cross a vast monster-infested wilderness to the dungeons to recover ancient weapons and artifacts, then to the dragons lairs, then face the final challenge...

Version 0.4 is a beta release for designing the gameplay, and future versions will have additional art, music, and sound effects.

Save Game Warning: Savefiles from previous versions will not be compatible with later versions until 1.0. At that point, Ill make sure they are always forward-compatible, but it hampers rapid development until then. Sorry for the trouble, but at least youll get to see the new world features in each version!

History

Over a thousand years ago, the world was a peaceful but primitive place. Humans lived in tribal societies, rarely warred, and there were few dangerous animals and no monsters. Your kingdom, Perilar, was one of the safest, as it was protected by four great dragons of Air, Earth, Fire, and Water.

Where the Vampire King came from, nobody knows. He appeared in the far north and turned peaceful farmers into berserker raiders. After conquering the island kingdom of Oradon, he turned their druids to necromancy, raising armies of the dead to war on the next kingdom. Kingdom after kingdom fell, and in each, the people were slain and raised as undead warriors to assault the next kingdom.

As the army of the undead approached Perilar, the dragons closed the kingdom off with a magical seal. For a thousand years, the kingdom has been trapped inside, and none know the fate of the outside world.

In recent times, the seals have begun to fail. The Dragons have not been seen in centuries. Undead and monsters march in towards the castle of King Phalan and the village of Perilar, home to the last free people in the world. A great hero must do something about this, and you are determined to be that hero!