Free wants to software for linux

Want is a Perl module created to implement the `want command.

SYNOPSIS

use Want;
sub foo :lvalue {
if (want(qwLVALUE ASSIGN)) {
print "We have been assigned ", want(ASSIGN);
lnoreturn;
}
elsif (want(LIST)) {
rreturn (1, 2, 3);
}
elsif (want(BOOL)) {
rreturn 0;
}
elsif (want(qwSCALAR !REF)) {
rreturn 23;
}
elsif (want(HASH)) {
rreturn { foo => 17, bar => 23 };
}
return
}

This module generalises the mechanism of the wantarray function, allowing a function to determine in some detail how its return value is going to be immediately used.

...

EXAMPLES

use Carp croak;
use Want howmany;
sub numbers {
my $count = howmany();
croak("Cant make an infinite list") if !defined($count);
return (1..$count);
}
my ($one, $two, $three) = numbers();


use Want want;
sub pi () {
if (want(ARRAY)) {
return [3, 1, 4, 1, 5, 9];
}
elsif (want(LIST)) {
return (3, 1, 4, 1, 5, 9);
}
else {
return 3;
}
}
print pi->[2]; # prints 4
print ((pi)[3]); # prints 1


sub backstr :lvalue {
if (want(qwLVALUE ASSIGN)) {
my ($a) = want(ASSIGN);
$_[0] = reverse $a;
return undef;
}
elsif (want(RVALUE)) {
my $t = scalar reverse $_[0];
}
else {
carp("Not in ASSIGN context");
}
return
}

print "foo -> ", backstr("foo"), "n"; # foo -> oof
backstr(my $robin) = "nibor";
print "$robin is now $robinn"; # $robin is now robin

Crown and Cutlass project is a 3D pirate action/adventure game in the spirit of Sid Meiers Pirates!.
It is simultaneously being developed in Linux and Windows, with a strong emphasis on cross-platform compatability. The project is still early on in development, although it is just beginning to look like an actual game.
Crown and Cutlass is written in C++, using OpenGL and SDL in order to allow cross-platform compatibility.
Main features:
- Sail around the Carribean in your pirate ship
- Sail into port in Carribean towns
- Ability to save and load game
Enhancements:
- This is the data to go along with the code in our Subversion repository.
- We have rearranged the data (and added a few files) since our 1.4 release.
- However, we may not release 1.5 until after our redesign is complete.
- As a result, anyone who wants to use the code in Subversion needs this package.
- Once the next release is complete, we will remove this file as the data will be in future releases.

Kana no quiz project is a little tool to memorize japanese kana (hiragana & katakana).

The method is quite simple: kana randomly appear and you have to find their transcription in rōmaji (Hepburn). There are several possibilities, but only one anwser is right!

Thanks to this method, you memorize the kana to its transcription, and thus know how to pronouce it!

It has been translated into several languages, and many quiz options are configurable. Kana images have been initially modelled in SVG and are placed under the Free Art License.

Through its option panel, Kana no quiz allows you to tune up
the quiz precisely, like choosing which group of kana you want
to train yourself upon.

First, hiragana and katakana are separated, both are then di-vided into big sets of kana according to their type ("Basic", "Modified", "Combined"; and a special "Additional" set for katakana only) which are thus composed of various portions containing 5/6 kana, following the traditional alphabet order (i.e.: ``ka ki ku ke ko").

According to your need and level, you may select one or more portions of the same or different sets, whole sets, all the kana... Once you feel comfortable (you can check it with the results displayed at the end of each quiz), you may also increase the number of possible answers in the random list, or even choose to answer directly through the text entry. Difficulty can be adapted to your skill: this is progressive learning.

From the complete beginner who has to start easily and learn step by step, to the wizard who just wants to confirm his/her absolute master of the kana, everyone should get satisfated with Kana no quiz!

Ginanh project is a 3D MMORPG that gives the players freedom in interactions with the environment.
Ginanh is a Massive Multiplayer Online Role-Playing Game (MMORPG) set in the dark Middle Ages with some oriental influence.
It should be devoid of any artificial limitations and have a very complex NPC logic. The player is located in a huge world where he can do almost everything and lead his (in-game) life as he wants to.
He can become just a passive observer and spend his time on a tree with a telescope, or face many monsters during dangerous expeditions.
Enhancements:
- This is mostly a code cleanup and bugfix release.
- An administrative console has been implemented in the server, and color support has been added to the curses user interface.
- Work on a graphical PyGame-based user interface has been started.

RearSite is a simple collaborative Web site manager. RearSite is an automated Web publishing tool allowing to control who is allowed to access the published documents and also to manage per directories collaboratives tools well adapted to distance learning (forums, chats, shareable calendars, or multimedia quizzes).

An administrator can create users accounts (user name, user passwd, and user home directory), users get logged in and then receive access to their documents.


RearSite is written in PERL (CGI.pm based) and use a FastCGI compliant HTTP server (like APACHE).

Using RearSite is quite simple : after login, the user has access to his home dir and is able to delete, rename, create and edit documents. RearSite is well adapted to install WWW directories previously cooked (using any editors). Its very easy to transfer and install archives (ZIP, tar or tar.gz by now), they are automatically unpacked.

Published documents are public (by default), access restriction may be done using user/password couples, DNS domains or LDAP filters.

The user interface is WWW forms like, so RearSite only needs (on the client side) a Java, JavaScript and frames compliant WWW browser (accepting cookies).

RearSite is now quite secured, the login process (developped in Java) use an MD5 encryption of the user password (combined with a one time key). So, people spying the network cannot use the keys they may have seen. After login, users receive a cookie associated with their computers IP numbers.

RearSite also allows the user to specify who can retrieve his documents by configuring access rights :

documents are public (the default).
documents are restricted to users coming from trusted domains.
documents are restricted to users coming from trusted domains or to HTTP authenticated users.
* documents are restricted to class of users existing in an LDAP directory. This kind of HTTP client authentication needs auth_ldap for Apache (See restricted access by users classes).

Since 1.1, if the administrator wants it, the user is able to use templates to specify per directories access rights. By default (and as an example), the user can easily say that a directory is public, for frenchies only or for frenchies excepted those in the ripoux.fr domain (french joke!).

The user is also able to share his directories with other RearSite users (trusted users). When a directory is shared, a trusted user user is able to delete, rename, add ... files within the directory he received rights for.

The user is also able to recursively process all the file names of all his embeded directories. The functionality provided is to rename all files (lowercase, replace a string within all file names, ...) which simplyfies migration from systems with case-insensitive file names. These functionalities are available by selecting the Special tools button which also give a way to export the current directory within an archive (ZIP or tar.gz).

Since 1.4, a forum can directly be attached to each directories. When a user wants to create a forum, the result is a Forum.html file located within the current directory. This file will give access to the forum. People having access to this file are allowed to post in the forum.

Since 1.6, a chat can directly be attached to each directories. When a user wants to create a chat, the result is a Chat.html file located within the current directory. This file will give access to the chat. People having access to this file are allowed to talk in the chat.

Since 1.9, a shareable calendar can be directly attached to each directories. When a user wants to create a calendar, the result is a Calendar.html file located within the current directory. This file will give access to the calendar. People having access to this file are allowed to read the calendar. Only the owner of a calendar is allowed to update it, but he may allow other users. Accessing his calendar via RearSite allows the owner to update it immediatly. When accessing a calendar via a normal WWW access, the user (owner or not) must be authenticated (via Rearsite configured authentication scheeme) before being allowed to update it.

The chat,forum and calendar functionalities are accessible via the Communications button, they have been designed for distance learning purposes but can easily be used for any groupware needs.

X-Chat NewsWindow is a perl script for X-Chat (or X-Chat Aqua) implements one of those annoying announcer scripts that announce your currently playing audio track in iTunes or your current audio or video track in VLC to your IRC channel because you feel for some reason that everyone wants to know.

I basically consider this script to be a better counterattack than just abusing the annoying mIRC users and getting the usual ignorant "pfft. sif mac" response. Since VLCs meta-data support leaves a bit to be desired, it obtains the album name from the containing folders name and the track name from the filename (minus the extension). This works quite well if you have a well labelled music collection. Note: If you use this script, exercise discretion. Not everyone cares what youre listening to.

To use this, you must first turn on logging in VLC. To do this, open VLCs preferences, and under the "Interface > Control Interfaces" preference page, tick the "File Logging" option. Then under the "Interface > Control Interfaces > Logging" page, enter "/tmp/vlc_log.txt" as the log filename. You can choose a different name or location if you wish, but if you do, change the path definition to it in the vlc_announce function below. You may have to choose the "Add Interface > Debug Logging" menu option (under the VLC menu) if VLC hasnt already turned it on via the preferences change.

usb-mount project provides desktop integration for systems using the hotplug scripts and the KDE desktop. It automatically mounts and unmounts USB storage partitions and modifies the users desktop, via the addition of icons representing USB storage device partitions.
The user can interact with the storage device by opening the desktop icons to reveal the folders corresponding to each partition. Each partitions mount status can be altered by using icon control options.
These scripts work for me on Fedora Core 2 and Redhat 9. Several people have reported that they can be made to function on many other Linux distributions with minor configuration changes and some editing.
To get them to work on your system you may need knowledge of Linux and shell scripting. If the scripts dont work out of the box, you should look for errors in /var/log/messages (or where ever your system log is kept). If you are not comfortable with reading logs and editing scripts - perhaps these scripts arent for you.
I no longer have any Linux systems with 2.4 kernels, I think the scripts will still work. All recent modifications have only been tested on Fedora Core 4 running kernel 2.6.
Many distributions are now adequately handling usb - so I havent spent much time improving usb-mount. If anyone wants to fork a new version, feel free. The new kernel, dbus, etc should make it quite easy to create a simpler script from scratch.
Enhancements:
- More fixes for newer kernels/distibutions that take longer to setup usb devices;
- Handle flash card readers that have more than one device (thanks to Edward);
- Ignore non usb-storage devices (thanks to Wolfgang Klein).