Free playing card software for linux

Nebula Cards project is a card game engine.
Nebula Cards is a networked, modular card game engine written in pure Java.
The game rules, user interfaces, and computer players all take the form of pluggable Java classes, and most four-player, trick-taking games can be implemented.
It currently includes Spades and Hearts, with a computer player for Spades.
Enhancements:
- last release before a major restructuring.
- added Game class in a backward-compatible way.
- added util.proc to house the new GameProcedure library.
- added util.ui.GraphicalCardSelector (untested).

Role Playing Tools extends the pen and paper role playing tabletop to the computer by providing a die rolling tool with a full expression language including Javascript functions, tabbed rolling bars, quick summation features, and the ability to save and restore sessions. There is also a client and server map sharing tool. Both are intended to be simple and powerful and enhance the game, not distract from it.

We found that we wanted to augment our pen-and-paper roleplaying (primarily 3.5ed D&D) with computer aids.

These tools extend and augment our traditional playing style. They are not a role playing game by themselves, nor are they meant to replace everything at the D&D table.

DiceToolis a simple but powerful expression parser that has built in functions for random number generation and can be further extended by JavaScript to do all sorts of calculations.
MapToolis an elegant graphical tool to share maps (images) and map data (drawings, markers, grid placement) in a client/server fashion between multiple players.
TokenToolis an accessory to MapTool. Drag any image onto the workspace and use the mouse to move and zoom the image in the reticle. Then drag from the preview pane directly onto MapTool -- or File->Save to save a png file.

Games::Bingo::Card is a helper class for Games::Bingo.

SYNOPSIS

use Games::Bingo::Card;

my $b = Games::Bingo-E new(90);
my $card = Games::Bingo::Card-E new($b);

my $bingo = Games::Bingo-E new(90);
$card-E validate($bingo);

use Games::Bingo::Print::Card;

my $p = Games::Bingo::Print::Card-E new();
$p-E populate();

The Games::Bingo::Card class suits the simple purpose of being able to generate bingo cards and validating whether they are valid in during a game where a player indicate victory.

It is also used by Games::Bingo::Print to hold the generated bingo cards before they are printed.

Online Cardgame System project is a client-server system for playing card games over the net.
OCS is a client-server cardgame system, similar to those found at Yahoo! Games and elsewhere. The server is portable and has been tested under Linux, Win32, and several unix systems. We currently have Win32 and Java clients available, and a Qt client for Linux is in development.
Games are implemented as plugin modules, so new games can be added without recompiling the server. In addition, the client is written to be unaware of the mechanics of gameplay, so it can theoretically play any games the server supports without having to know how to play them specifically.
We currently have Euchre and Spades implemented, with bot support for both games, meaning you dont need a full 4 people to play a game. We plan on implementing more games in the future.
On a side note, development of this project tends to wax and wane with our motivation and amount of schoolwork.
Enhancements:
- Massive restructure of code into more object orientated patterns
- Added daemon capability to server
- Got rid of checksumming in the protocol since TCP/IP does it internally
- Padded STRINGS in the protocol on DWORD boundaries
- Added support for loadable account managers
- Removed crypting of the password by ocsd (account managers may do it)
- Added ODBC (for windows) and mySQL (for unix) account managers (database connectivity!!)
- Modified packet classes to throw exceptions instead of returning true-false
- Created packet manager classes to queue client packets, reduces total send calls
- Implemented bots when there arent enough people to play games
- Added new command line processing capabilities as well as configuration file support
- Fixed bug that allowed a person to overwrite an account when creating that same account
- Win32 - Made server link with DLL runtime library to reduce executable size and ease DLL dependencies
- Updated messages to be sent in HTML since the main clients support it
- Created Java client which can be run as an application or as an applet
- After a client is booted from a game, they cannot join the game again until they receive an invitation
- Fixed libtidy bug which caused it to erroneously format HTML
- Euchre supports intelligent bots
- Spades supports moronic bots (the AI is horrible but allows for gameplay)
- Fixed Spades textual problem when a round was over.
- Fixed Spades score calculation that resulted in no loss of points
- Win32 client now supports HTML (IE4+ required)
- Win32 client can now join games by right-clicking on an empty game slot in the game view.
- Fixed major bug in Win32 client that would cause it to crash when sending private messages
- Win32 client can now use /msg to send private messages

WML::Card is a Perl extension for builiding WML Cards according to the browser being used.

SYNOPSIS

use WML::Card;
my $options= [ [Option 1, http://...], [Option 2, http://...], ];
my $c = WML::Card->guess(index,Wap Site); $c->link_list(indice, undef, 0, $options, $options); $c->print;

This perl library simplifies the creation of WML cards on the fly. It produces the most suitable wml code for the browser requesting the card. In this way the one building the cards does not have to worry about the differences in how each wap browser displays the wml code. In combination wht WML::Deck it provides functionality to build WAP applications.

Methods

$card = WML::Card->guess( $id, $title, [$user_agent] );
This class method constructs a new WML::Card object. The first argument defines the WML cards id and the second argument its title. The if the third argument is not defined, the value is obtained from $ENV{HTTP_USER_AGENT}.

$c->buttons($label, $type, $task, $href)
$c->table ($data, $title, $offset, $pager, @headers)
$c->link_list($name, $listtitle, $offset, $pager, $data, $align)
$c->value_list($name, $listtitle, $offset,$pager,$data)

The variable $data is an array reference like: my $menu_items= [ [Option 1, http://...], [Option 2, http://...], ];

The variable $pager is the number of items wanted to be displayed in each card.

$c->print
$c->info($content)
$c->img($file, $alt)
$c->input($label, $text, $name, $format, $type, $size, $target, $arg);
$c->link($target, $text);
$c->br

Asterisk Live CF card is, clearly, a compact flash install of asterisk that will give you a complete, running system similar to that of the asterisk live CD.

Indeed most things are the same although there have been some additions and changes.

To install the CF you will need some way of getting the image onto the card. Generally this can be done with a USB CF card reader using

dd if=asterisk-cf-b01 of=/dev/sda bs=1k count=64000

Useful things to know

1. The cf install currently assumes its hda (1 2 and 3) so youll need to put it in as your primary master using your CF->IDE adaptor, this will be more automagical in the future

2. example configs are stored on hda3 along with a new feature script called remoteconfig. This will allow you to update the configuration/OS automatically on boot from a remote webserver. More detail on how to use this feature will appear at http://www.automated.it/asterisk be sure to read any notes there first.

3. At the minimum youll need a 64mb CF card but you can use a larger one if you wish and create futher partitions. Currenly when you create the CF from the image the following partitions exist

Disk /dev/hda: 8 heads, 32 sectors, 490 cylinders
Units = cylinders of 256 * 512 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 33 4208 83 Linux
/dev/hda2 34 354 41088 83 Linux
/dev/hda3 355 490 17408 83 Linux

4. Once booted you will need to make changes to the files in /dev/hda3/astlive-example, particularly networking and the zapata/zaptel configs. Note, if you rename the astlive-example directory to astlive then on the next boot the files will be copied and activated on the running system automatically. Using the example astlive directory includes a PASSWORD CHANGE for root from EPPING to epping (without quotes) as a demonstration. At the minimum you MUST change the networking to suit your environment, since they will change to what is in this directory too.

5. All partitions on the CF are unmounted after boot so if you need to work on them, you will need to specifically mount them.

6. Ive tested E100P, X100P and TDM40B cards using this install, and would be interested to hear of other cards proven to be working.

Games::Cards is a Perl module for writing and playing card games.

SYNOPSIS

use Games::Cards;
my $Rummy = new Games::Cards::Game;

# Create the correct deck for a game of Rummy.
my $Deck = new Games::Cards::Deck ($Rummy, "Deck");

# shuffle the deck and create the discard pile
$Deck->shuffle;
my $Discard = new Games::Cards::Queue "Discard Pile";

# Deal out the hands
foreach my $i (1 .. 3) {
my $hand = new Games::Cards::Hand "Player $i" ;
$Deck->give_cards($hand, 7);
$hand->sort_by_value;
push @Hands, $hand;
}

# print hands (e.g. "Player 1: AS 2C 3C 3H 10D QS KH")
foreach (@Hands) { print ($_->print("short"), "n") }

$Hands[1]->give_a_card ($Discard, "8D"); # discard 8 of diamonds

This module creates objects and methods to allow easier programming of card games in Perl. It allows you to do things like create decks of cards, have piles of cards, hands, and other sets of cards, turn cards face-up or face-down, and move cards from one set to another. Which is pretty much all you need for most card games.