Free select a seat software for linux

This is a small application (using GTK+) which lets you select your window manager. It looks for a file named .selectwmrc in the users directory which contains a list of window managers.

When you start X it should show a list which lets you choose your window manager (by double clicking on it with the mouse or with the arrow keys and the return or space key).

Inline::Select contains dynamic selection of ILSM for a package.

SYNOPSIS

use Inline::Select::Register (
PACKAGE => Calc,
Inline => [ Perl => sub {require t/Calc.pm} ]
) ;
use Inline::Select::Register (
PACKAGE => Calc,
Inline => [ CPP => t/Calc.cpp ]
) ;
use Inline::Select::Register (
PACKAGE => Calc,
Inline => [ Java => t/Calc.java ]
) ;
use Inline::Select::Register (
PACKAGE => Calc,
Inline => [ Python => t/Calc.py ]
) ;

use Inline::Select (
PACKAGE => Calc,
Inline => $ARGV[0] # one of Perl, CPP, Java, Python
) ;

my $c = new Calc() ;
ok($c->add(2, 3), 5) ;

USAGE

Usage of Inline::Select is pretty simple. For each programming language, you must speficy a use Inline::Select::Register (or Inline::Select->register() at runtime) statement to register the use of Inline for that language. All the Inline parameters are saved and that Inline block will only be evaluated if that language is selected later on.

When you are done registering Inline blocks, you then spefify a use Inline::Select (or Inline::Select->bind() at runtime) to actually load (in the caller package) the Inline block for the selected language.

Volity::Seat is a Volity seat, containing some players.

SYNOPSIS

# From within a Volity::Game subclasss code:
my @seats = $self->seats;

# Or, given a Volity::Player object:
my $seat = $player->seat;

# Now tell the seat they just picked up the Three of Clubs:
$seat->call_ui_function("draw_card", "3C")

An objects of this class represents a seat at a Volity table. Volity players who are actually playing a game sit in seats, and referees address game-specific RPC calls to seats, not to individual players. See the main Volity documentation for more information about the seat concept: http://www.volity.org/wiki/index.cgi?action=browse&id=Seats

USAGE

As a game programmer, you need never create, modify, or destroy these objects yourself; that is all handled for you by the other objects that make up a Frivolity-run table, particularly the referee (see Volity::Referee). However, several methods of Volity::Game, the module you subclass to create your own Perl-based Volity game, will return objects of this class. Several crucial functions of communicating with a games players involve calling methods on these objects, including the all-important call_ui_function method (described below).

Your Volity::Game subclass must define some variables that assist the referee in seat creation, particularly the seat_ids and required_seat_ids class variables. If you wish to extend this class for your game, you can speficy a Volity::Seat subclass to use through Volity::Games seat_class method. All these are described in detail within Volity::Game.

OSGlobeLAN project is a Web portal for LAN parties, featuring a seat map system, registration, and more.
Enhancements:
- A lot of changes have been made, but this release is primarily to announce that work on the pre-1.0 codebase of OSGL has been stopped, and will no longer be maintained.
- Serious security-related issues might be fixed, but all focus is now on the 2.0 codebase.

MySQL Abstractor package contains PHP classes that implements a MySQL database abstraction layer.

It provides several classes. There is one for establishing connections and executing SQL queries, another for composing and executing SELECT, INSERT, UPDATE and DELETE queries from a list of parameters, and a wrapper class to simplify the usage of the other two classes.

SQL::Interpolate is a Perl module to interpolate Perl variables into SQL statements.

SYNOPSIS

use SQL::Interpolate qw(:all);

# Some sample data to interpolate:
my $s = blue; my @v = (5, 6);

# Variable references are transformed into bind parameters.
# The most basic usage involves scalarrefs (as well as arrayrefs
# preceeded by "IN").
my ($sql, @bind) = sql_interp
SELECT * FROM table WHERE x = , $s, AND y IN, @v;
# RESULT:
# $sql = SELECT * FROM mytable WHERE x = ? AND y IN (?, ?)
# @bind = ($s, @v);

# In certain contexts, an arrayref or hashref acts as a single tuple:
my ($sql, @bind) = sql_interp
INSERT INTO table, {x => $s, y => 1};
# RESULT:
# $sql = INSERT INTO mytable (x, y) VALUES(?, ?);
# @bind = ($s, 1);
my ($sql, @bind) = sql_interp
UPDATE table SET, {x => $s, y => 1}, WHERE y , 2;
# RESULT:
# $sql = UPDATE mytable SET x = ?, y = ? WHERE y ?;
# @bind = ($s, 1, 2);

# In general, a hashref provides a shortcut for specifying
# a logical-AND construction:
my ($sql, @bind) = sql_interp
SELECT * FROM table WHERE, {x => $s, y => @v};
# RESULT:
# $sql = SELECT * FROM mytable WHERE (x = ? AND y IN (?, ?));
# @bind = ($s, @v);

# In general, an arrayref acts as a result set or reference to
# a temporary table:
my ($sql, @bind) = sql_interp
[[1, 2], [4, 5]], UNION, [{x => 2, y => 3}, {x => 5, y => 6};
# RESULT:
# $sql = (SELECT ?, ? UNION ALL SELECT ?, ?) UNION
# (SELECT ? AS x, ? AS y UNION ALL SELECT ?, ?);
# @bind = (1,2,4,5, 2,3,5,6);
my ($sql, @bind) = sql_interp
SELECT * FROM, [[1, 2], [4, 5]]
# RESULT:
# $sql = SELECT * FROM (SELECT ?, ? UNION ALL SELECT ?, ?) AS tbl0;
# @bind = (1,2,4,5);

# Each result above is suitable for passing to DBI:
my $res = $dbh->selectall_arrayref($sql, undef, @bind);

# Besides these simple techniques shown, SQL-Interpolate includes
# various optional modules to further integrate SQL::Interpolate with
# DBI and streamline the syntax with source filtering and macros (see
# the L section):

use DBIx::Interpolate FILTER => 1;
...
my $rows = $dbx->selectall_arrayref(sql[
SELECT thid, date, title, subject
FROM threads
WHERE date > $x AND subject IN @subjects
]);