Free take place software for linux

The Plastic File System project is an LD_PRELOAD module for manipulating what the file system looks like for programs. This allows virtual file systems to exist in user space, without kernel hacks or modules.
PlasticFS includes the following file systems:
chroot
The chroot filter may be used to simulate the effects of the chroot(2) system call, in combination with other filters.
dos
The dos filter may be used to simulate an 8.3 DOS file system.
log
The log filter may be used to transparently log file system access, similar to the strace command.
shortname
The shortname filter may be used to simulate file systems with shorter filenames.
smartlink
The smartlink filter may be used to expand environment variables in symbolic links, using the usual $name notation.
upcase, downcase, titlecase and nocase
The upcase filter to make file names appear to be in upper-case when listed. File names are case- insensitive when being opened, etc. The downcase filetr is similar, except it converts to lower-case, titlecase capitalizes, and nocase is simply case insensitive without altering the filenames.
viewpath
The viewpath filter may be used to make a set of directory trees look like a single directory tree. (Also known as a union file system.) All modifications take place in the first directory in the list.
Aka: union and translucent
Note: Filters may be piped from one to the next, forming powerful combinations.
PlasticFS is currently dependent on the implementation of the GNU C Library. It is self configuring using a GNU Autoconf generated configure script.
Enhancements:
- Build problem fixed.

Perl6::Take is a Perl module to gather/take in Perl 5.

SYNOPSIS

use Perl6::Take;

my @foo = gather {
take 5;
};

EXPORT

gather

Accepts a block. take statements inside the dynamic scope of the block are used to accumulate a list, which is gathered as the return value of the block.

take

Accumulates its argument (or list of arguments) on to the nearest gather in the dynamic scope. Arguments are evaluated in list context. The arguments may be passed on to a variable, but note that this assignment should usually be done in list context, as per usual context rules:

$answer = take 42; # 1
($answer) = take 42; # 42

Show the Image is a Firefox extension that shows the largest image in the page.

A very simple extension that can be used to show the largest image on the page - what you want to look at - without all the banners and layout around it.

After installing the extension you can add a new button to the toolbar by right-clicking on the toolbar, clicking customize and dragging the icon into place.

Left-clicking the button (or pressing Control+Q) will take you to the largest image in the current page, left-clicking (or pressing Control+Q) again will take you back again.

Middle-clicking the button (or pressing Control+Shift+Q) will open the largest image in the current page in a new tab, middle-clicking (or pressing Control+Shift+Q) while looking at the image on its own will close the tab if more than one is open.

Right clicking the button will go through all the tabs to the right of the current one, displaying the largest image in each.

Right clicking on a link will give the option to "Show Image following this link" which will open the largest image found at that link in a new tab.

Notes List is a simple and easy way to take Notes.

- Change SIZE (width and height)
- tun on/off the background image
- Auto save notes

Global Village project is a gnome application designed to place a front-end, or graphical user interface onto the CLI interface of Xplanet, by Hari Nair.
Originally intended to create and update the desktop wallpaper in a gnome environment, showing a traditional rectangular projection of the planet Earth, the scope of the project has been expanded. Global Village now provides as many of the features of Xplanet as seem reasonable, and with the ability for plugins the scope is nearly limitless. But do take it with a grain of salt...
Current Status
Currently, Global Village is barely functional. It can be considered in the pre-alpha stage of development.
It can currently show a preview of the final image, and then display that image on the desktop at user specified intervals (in seconds), and has an icon in the notification area of the Gnome panel.
Plugins are semi-working, but undergoing a lot of change as I decide what they do adn dont need to be capable of. The idea is that plugins will manage all the extra features users require, like cloudmaps, marker and arc files.
Main features:
- Select a planet.
- Select a projection.
- Bodys North Type.
- Rotate the bodys North Pole
- The Zoom level
- The Suns glare
- Latitude and Longitude, which can be set as:
- North Pole
- South Pole
- Equator
- Random Latitude and Longitude
- Or any number of user configerable locations.

perlhack is a Perl module that will show you how to hack at the Perl internals.

This document attempts to explain how Perl development takes place, and ends with some suggestions for people wanting to become bona fide porters.
The perl5-porters mailing list is where the Perl standard distribution is maintained and developed. The list can get anywhere from 10 to 150 messages a day, depending on the heatedness of the debate. Most days there are two or three patches, extensions, features, or bugs being discussed at a time.

A searchable archive of the list is at either:

http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/

or

http://archive.develooper.com/perl5-porters@perl.org/

List subscribers (the porters themselves) come in several flavours. Some are quiet curious lurkers, who rarely pitch in and instead watch the ongoing development to ensure theyre forewarned of new changes or features in Perl. Some are representatives of vendors, who are there to make sure that Perl continues to compile and work on their platforms. Some patch any reported bug that they know how to fix, some are actively patching their pet area (threads, Win32, the regexp engine), while others seem to do nothing but complain. In other words, its your usual mix of technical people.

Over this group of porters presides Larry Wall. He has the final word in what does and does not change in the Perl language. Various releases of Perl are shepherded by a "pumpking", a porter responsible for gathering patches, deciding on a patch-by-patch, feature-by-feature basis what will and will not go into the release. For instance, Gurusamy Sarathy was the pumpking for the 5.6 release of Perl, and Jarkko Hietaniemi was the pumpking for the 5.8 release, and Rafael Garcia-Suarez holds the pumpking crown for the 5.10 release.
In addition, various people are pumpkings for different things. For instance, Andy Dougherty and Jarkko Hietaniemi did a grand job as the Configure pumpkin up till the 5.8 release. For the 5.10 release H.Merijn Brand took over.

Larry sees Perl development along the lines of the US government: theres the Legislature (the porters), the Executive branch (the pumpkings), and the Supreme Court (Larry). The legislature can discuss and submit patches to the executive branch all they like, but the executive branch is free to veto them. Rarely, the Supreme Court will side with the executive branch over the legislature, or the legislature over the executive branch. Mostly, however, the legislature and the executive branch are supposed to get along and work out their differences without impeachment or court cases.

You might sometimes see reference to Rule 1 and Rule 2. Larrys power as Supreme Court is expressed in The Rules:

Larry is always by definition right about how Perl should behave. This means he has final veto power on the core functionality.

Larry is allowed to change his mind about any matter at a later date, regardless of whether he previously invoked Rule 1.

Got that? Larry is always right, even when he was wrong. Its rare to see either Rule exercised, but they are often alluded to.

New features and extensions to the language are contentious, because the criteria used by the pumpkings, Larry, and other porters to decide which features should be implemented and incorporated are not codified in a few small design goals as with some other languages. Instead, the heuristics are flexible and often difficult to fathom. Here is one persons list, roughly in decreasing order of importance, of heuristics that new features have to be weighed against:

Does concept match the general goals of Perl?

These havent been written anywhere in stone, but one approximation is:

1. Keep it fast, simple, and useful.
2. Keep features/concepts as orthogonal as possible.
3. No arbitrary limits (platforms, data sizes, cultures).
4. Keep it open and exciting to use/patch/advocate Perl everywhere.
5. Either assimilate new technologies, or build bridges to them.

Where is the implementation?

All the talk in the world is useless without an implementation. In almost every case, the person or people who argue for a new feature will be expected to be the ones who implement it. Porters capable of coding new features have their own agendas, and are not available to implement your (possibly good) idea.

Backwards compatibility

Its a cardinal sin to break existing Perl programs. New warnings are contentious--some say that a program that emits warnings is not broken, while others say it is. Adding keywords has the potential to break programs, changing the meaning of existing token sequences or functions might break programs.

Could it be a module instead?

Perl 5 has extension mechanisms, modules and XS, specifically to avoid the need to keep changing the Perl interpreter. You can write modules that export functions, you can give those functions prototypes so they can be called like built-in functions, you can even write XS code to mess with the runtime data structures of the Perl interpreter if you want to implement really complicated things. If it can be done in a module instead of in the core, its highly unlikely to be added.

Is the feature generic enough?

Is this something that only the submitter wants added to the language, or would it be broadly useful? Sometimes, instead of adding a feature with a tight focus, the porters might decide to wait until someone implements the more generalized feature. For instance, instead of implementing a "delayed evaluation" feature, the porters are waiting for a macro system that would permit delayed evaluation and much more.

Does it potentially introduce new bugs?

Radical rewrites of large chunks of the Perl interpreter have the potential to introduce new bugs. The smaller and more localized the change, the better.

Does it preclude other desirable features?

A patch is likely to be rejected if it closes off future avenues of development. For instance, a patch that placed a true and final interpretation on prototypes is likely to be rejected because there are still options for the future of prototypes that havent been addressed.

Is the implementation robust?

Good patches (tight code, complete, correct) stand more chance of going in. Sloppy or incorrect patches might be placed on the back burner until the pumpking has time to fix, or might be discarded altogether without further notice.

Is the implementation generic enough to be portable?

The worst patches make use of a system-specific features. Its highly unlikely that nonportable additions to the Perl language will be accepted.

Is the implementation tested?

Patches which change behaviour (fixing bugs or introducing new features) must include regression tests to verify that everything works as expected. Without tests provided by the original author, how can anyone else changing perl in the future be sure that they havent unwittingly broken the behaviour the patch implements? And without tests, how can the patchs author be confident that his/her hard work put into the patch wont be accidentally thrown away by someone in the future?

Is there enough documentation?

Patches without documentation are probably ill-thought out or incomplete. Nothing can be added without documentation, so submitting a patch for the appropriate manpages as well as the source code is always a good idea.

Is there another way to do it?

Larry said "Although the Perl Slogan is Theres More Than One Way to Do It, I hesitate to make 10 ways to do something". This is a tricky heuristic to navigate, though--one mans essential addition is another mans pointless cruft.

Does it create too much work?

Work for the pumpking, work for Perl programmers, work for module authors, ... Perl is supposed to be easy.

Patches speak louder than words

Working code is always preferred to pie-in-the-sky ideas. A patch to add a feature stands a much higher chance of making it to the language than does a random feature request, no matter how fervently argued the request might be. This ties into "Will it be useful?", as the fact that someone took the time to make the patch demonstrates a strong desire for the feature.

If youre on the list, you might hear the word "core" bandied around. It refers to the standard distribution. "Hacking on the core" means youre changing the C source code to the Perl interpreter. "A core module" is one that ships with Perl.

GalaxyHack project allows you to design a fleet of spaceships which can then be tested in AI script based battles against fleets designed by other players.

Though battles take place in real time, the strategy comes before hand, both in writing short AI scripts in a simple scripting language, and also in the set up and selection of your fleet.

You dont actually have any control over your units at all mid-battle, but rather use the time to see where the set up of your fleets is working, where your fleets weaknesses lie and changes are needed, and perhaps also to learn from the strategy of your opponent.

The game revolves around very large capital ships, from which smaller ships are launched, but which are not designed for attacking themselves, and which cannot be moved mid-battle. To win a battle you must destroy of all of your opponents capital ships before they destroy yours.

There can be hundreds of units in any one battle, but there is no harvesting, resource management or base building.

Fleet customisation:

There are three basic unit types: capital ships, frigates and small ships. All three are customisable with a small range of different weapons and technologies. Fleet selection and unit customisation are done using a windows-and-menus based editor. Each fleet has a points value, which is increased by adding or upgrading units.

You are able to save a fleet, along with a corresponding set of AI script selections.

AI scripting:

A "group" of units - consisting of up to three actual units - has an AI script attached to it. Scripts are written using a simple proprietary language. There are two generic types of weapons in the game: "small" and "big". "small" weapons are always fired automatically when there is an enemy within range, whilst "big" weapons are fired on the basis of AI script commands. The game translates the AI commands for a group into commands for each individual unit within that group.

AI scripts are written externally to the game using any program capable of editing text files.

The chief principle of GalaxyHack AI scripts is "If this then that else the other". For a more concrete example, here are two lines of code from an AI file:

if aenemy type == smallship health < 100
move nenemy type == smallship health < 100

Scripts also support:

* function calls
* a variety of different sorts of variables which can have their value changed by scripts.

Multiplayer:

The game is designed to allow different commanders to test their fleets in battle against one another. Up to four fleets can participate in any one battle. This said, the game is not properly "multiplayer" in that you never actually play in real time against other players. Instead, you can download fleets designed by other players from an online database. You are encouraged to submit your own fleets to this database for other players to download and battle against.

Graphics and sound:

The game engine is a 2D affair, with ships and what have you shuffling about. It is fairly easy to create your own custom art for your units, should you so wish.

There are various basic graphical effects for firing weapons of various sorts, units being destroyed, etc.

The game features music composed by The Embryo.

The game does not feature any sound effects.