Free guido software for linux

Guido van Robot, or GvR for short, is a minimalistic programming language that provides just enough syntax to help students learn the concepts of sequencing, conditional branching, looping, and procedural abstraction.

Guido van Robots biggest strength is that it permits this learning in an environment that combines the thrill of problem-solving with instant visual feedback.

JRicochet is a simple puzzle game. It consists of a 10x10 grid, which contains 5 invisible blocks. From each side a player can shoot probes into the grid. Goal is to find the blocks by the pattern of the ricochetting probes in as few shots as possible.

GSTorrent is a Bittorrent client/server system. A daemon program handles all the file transfers as a Bittorrent client. The GSTorrent daemon also acts as a server for an external GUI client.
The objective is to have a relatively small Bittorrent client, which runs on a small computer without a graphical interface and to control this server from a different machine.
An example of this type of architecture is the mldonkey client/server system for the edonkey protocol.
Enhancements:
- The torrent hash problem is fixed.
- The upload/download rate settings finally work correctly.
- A better torrent selector.

GTestRunner is a Gtk+ based testrunner module for Perl, inspired by JUnit, but with a slightly different user interface and functionality.

If you were not satisfied with the Tk based graphical frontend that ships with Test-Unit, then GTestRunner is probably the tool of choice when you want to do test driven development in Perl.

It also offers some improvements over the other test runner modules that ship with Test-Unit. You can browse through the tree of test suites, and select individual test suites, test cases and even individual tests to run.

You can use this module in two different ways. Most users will just want to run the script "gtestrunner" to run their test suites. If you want to integrate unit testing into your own software, you will probably use the module Test::Unit::GTestRunner.

Some stupid test suites and test cases are included with this package. Try

gtestrunner Suites/TS_TopLevel.pm

or

gtestrunner Suites::TS_TopLevel

to see gtestrunner in action. The test suites fails five times, and you have probably guessed that this is intentionally, so that you can see all features.

GTestRunner is fully internationalized. See the file README-NLS for details. See the file TRANSLATIONS for information about the currently available languages. Feel free to contact the author if you want to contribute a translation for your own native langauge.

Kvdr program lets you watch the output of VDR on a monitor in X11.
Main features:
- anything vdr can do and will do
- handles the overlay of your dvb-cards
- lets you zap through your video devices or display up to for overlays at once (if you have more than one card). However - changing the channel via vdr is currently only supported on the "primary" dvb-interface.
- The picture in picture allows you to follow the movie at the other device in the small image. You can exchange those by a single key-press.
- the Xv-mode lets you zoom the image to larger resolutions and optionally handles deinterlacing by 50Hz half frame upscaling or field1 upscaling.
- fullscreen-mode (mouse, dpms and screensaver automatically handled)
- can be used for "remote" viewing of vdr-recordings if you have 2 dvb-cards and the remote-video-directory mounted
- lets you grab images during viewing, playback or recording in jpg or pnm format, filename is automatically generated out of channel-name, date and time.
- lets you control Brightness, Colour, Hue and Contrast of the overlay (not applied to grab-images!)
- handles 4:3 and 16:9 aspect ratios corrected with viewport-dimensions (currently at 4:3 monitors only)
- handles PAL and NTSC accordingly (but only PAL tested so far - iam living in Germany ;-)
- stores all configuration to file
- sound-handling: mixer-channel, volume and mute using alsa/amixer
- Front/Rear-volume balance

Locale::TextDomain is a Perl Interface to Uniforum Message Translation.

SYNOPSIS

use Locale::TextDomain (my-package, @locale_dirs);

use Locale::TextDomain qw (my-package);

my $translated = __"Hello World!n";

my $alt = $__{"Hello World!n"};

my $alt2 = $__->{"Hello World!n"};

my @list = (N__"Hello", N__"World");

my @plurals = (N__ ("One world", "{num} worlds"),
N__ ("1 file", "%d files"));

my $question = __x ("Error reading file {file}: {err}",
file => $file, err => $!);

printf (__n ("one file read",
"%d files read",
$num_files),
$num_files);

print __nx ("one file read", "{num} files read", $num_files,
num => $num_files);

The module Locale::TextDomain(3pm) provides a high-level interface to Perl message translation.

Textdomains

When your request a translation for a given string, the system used in libintl-perl follows a standard strategy to find a suitable message catalog containing the translation: Unless you explicitely define a name for the message catalog, libintl-perl will assume that your catalog is called messages (unless you have changed the default value to something else via Locale::Messages(3pm), method textdomain()).
You might think that his default strategy leaves room for optimization and you are right. It would be a lot smarter if multiple software packages, all with their individual message catalogs, could be installed on one system, and it should also be possible that third-party components of your software (like Perl modules) can load their message catalogs, too, without interfering with yours.

The solution is clear, you have to assign a unique name to your message database, and you have to specify that name at run-time. That unique name is the so-called textdomain of your software package. The name is actually arbitrary but you should follow these best-practice guidelines to ensure maximum interoperability:

File System Safety

In practice, textdomains get mapped into file names, and you should therefore make sure that the textdomain you choose is a valid filename on every system that will run your software.

Case-sensitivity

Textdomains are always case-sensitive (i. e. Package and PACKAGE are not the same). However, since the message catalogs will be stored on file systems, that may or may not distinguish case when looking up file names, you should avoid potential conflicts here.

Textdomain Should Match CPAN Name

If your software is listed as a module on CPAN, you should simply choose the name on CPANS as your textdomain. The textdomain for libintl-perl is hence libintl-perl. But please replace all periods (.) in your package name with an underscore because ...

Internet Domain Names as a Fallback

... if your software is not a module listed on CPAN, as a last resort you should use the Java(tm) package scheme, i. e. choose an internet domain that you are owner of (or ask the owner of an internet domain) and concatenate your preferred textdomain with the reversed internet domain. Example: Your company runs the web-site www.foobar.org and is the owner of the domain foobar.org. The textdomain for your companys software barfoos should hence be org.foobar.barfoos.

If your software is likely to be installed in different versions on the same system, it is probably a good idea to append some version information to your textdomain.
Other systems are less strict with the naming scheme for textdomains but the phenomena known as Perl is actually a plethora of small, specialized modules and it is probably wisest to postulate some namespace model in order to avoid chaos.

Binding textdomains to directories

Once the system knows the textdomain of the message that you want to get translated into the users language, it still has to find the correct message catalog. By default, libintl-perl will look up the string in the translation database found in the directories /usr/share/locale and /usr/local/share/locale (in that order).

It is neither guaranteed that these directories exist on the target machine, nor can you be sure that the installation routine has write access to these locations. You can therefore instruct libintl-perl to search other directories prior to the default directories. Specifying a differnt search directory is called binding a textdomain to a directory.

Locale::TextDomain extends the default strategy by a Perl specific approach. Unless told otherwise, it will look for a directory LocaleData in every component found in the standard include path @INC and check for a database containing the message for your textdomain there. Example: If the path /usr/lib/perl/5.8.0/site_perl is in your @INC, you can install your translation files in /usr/lib/perl/5.8.0/site_perl/LocaleData, and they will be found at run-time.

Test::Unit::GTestRunner is a Unit testing framework helper class

SYNOPSIS

use Test::Unit::GTestRunner;

Test::Unit::GTestRunner->new->start ($my_testcase_class);

Test::Unit::GTestRunner::main ($my_testcase_class);

If you just want to run a unit test (suite), try it like this:

gtestrunner "MyTestSuite.pm"

Try "perldoc gtestrunner" or "man gtestrunner" for more information.

This class is a GUI test runner using the Gimp Toolkit Gtk+ (which is called Gtk2 in Perl). You can use it if you want to integrate the testing framework into your own application.

For a description of the graphical user interface, please see gtestrunner(1).