Free greeting cards software for linux

PHP Greeting card class can be used to compose and send greeting cards by email.

PHP Greeting card class can compose and send an email message with a greeting either in text, in HTML with an image, or in HTML with Flash content.

The HTML version of the card may include a greeting picture.

Penguin Cards project is a card game.
PenguinCards is a two-player card game. The aim is to find the pairs of cards on the board. The one who finds out more card pairs is the winner.
PenguinCards is a java-based game.
If you are unhappy with images on the cards, then simply copy your cards into images/pictures/penguins directory. That is it!
Enhancements:
- Initial release

Penguin Greetings is a Perl Web-based greeting card application. Penguin Greetings is two products wrapped into one. Penguin Greetings is an engine for handling web "ecards." It is also a collection of 200 cards that can be quickly and easily installed into any server for an immediate ecards solution. In addition, another 24 card images are included separately in the Penguin Greetings - Four Seasons collection and another 16 note card images are now included in the Penguin Greetings - Savoring the sights of Seattle Collection. The cards are photo-based and are similar in style and taste to Apples iCards content. To see the complete Penguin Greetings solution, go to the demonstration page.
The Penguin Greetings (pgreet) engine is a web-based greeting cards for LINUX and other UNIX-based systems written in Perl. Penguin Greetings is template-based and shifts ecards to be more like email instead of web-only objects. For flexibility and security, a separate daemon works with the emails and stores data permanently on the server.
Main features:
- Supports any number of ecard sites running on the same server. Each site is independent with its own configuration, database files, and HTML content. Localization/Internationalization is supported so that secondary ecard sites can be used to support multiple languages and regions. User ecard sites are supported.
- Customizable HTML templates for both the ecards and creation screens so that the web content is completely independent of the Perl program. Perl content is embedded using Embperl or now HTML::Mason so that the full power of Perl is available to content developers and for server-side processing. Object-oriented ecard sites can be created using Embperl::Object or Mason. At the same time, creating templates does not require any specific knowledge of Perl. Using Embperl or Mason, it is possible to build complicated ecard sites as demonstrated by the Penguin Greetings - California Poppy Collection. or the Penguin Greetings - Savoring the sights of Seattle Collection
- Support for a persistent Perl interpreter via SpeedyCGI for robust performance under production loads. Configuration and state information is cached in memory for improved performance under SpeedyCGI. Retains support for standard CGI for portability.
- Greeting cards that function more like email. The announcement of the card includes the text of the card so that the recipient can reply to the message. The email of the author is included in the email reply-to field so that recipients can reply to the ecard using the reply feature of most email clients.
- Uses MIME multipart HTML formatted email to directly send complete ecards to recipients.
- Automated installation procedure, including: the installation of CPAN modules not included in Perl 5.8.0, localization of configuration files, and installation of applications, configuration files, and a default ecard website.
- Access to card creation can be limited to users stored in an htpasswd file on server for sites which want to have ecards available only to a particular group of people.
- A separate application daemon to handle such chores as: card scheduling for emailing on a particular date, purging of old cards after a certain date, and backup database files.
- A user agent separate from the user ID which the web server runs as for mailing and storing of data. If desired, ecards can be emailed under existing email accounts on server. Specific human users on the server can be given access to this feature via an access control list.
- Extensive configuration options. Including the location of configuration and data files, performance tuning, and content parameters.
- Based on standard Perl CPAN modules for portability and reliability.
- Extensive logging of daemon activities.
- Six secondary demonstrations sites included with the distribution, Five of which exist in both English and French as examples of internationalization. Four use Embperl::Object to demonstrate object-oriented website building techniques and one uses HTML::Mason.

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.

SVG-cards is a set of playing cards made from pure SVG with all kings, queens, jacks, numbers, jokers, and backs of cards.
You can use SVG-cards everywhere you like : Web pages, games, the GNOME desktop, the KDE desktop, and so on...
You can print them on your color printer and make real cards or T-shirts.
The kings, queens and jacks are based on the french representation, because I find them beautiful. You can access to each either by rendering the file into a pixmap and clipping each card or by using their name with a DOM interface. All cards are inside a SVG group.
Example :
the king of spade is inside this group :
< g id="king_spade" >
...
< /g >
Names are the following :
black_joker
red_joker
back
{king,queen,jack}_{club,diamond,heart,spade}
{1,2,3,4,5,6,7,8,9,10}_{club,diamond,heart,spade}
Examples :
- the ace of club is 1_club
- the queen of diamond is queen_diamond
Enhancements:
- A bug that prevented SVG cards from being displayed in Firefox and Adobe Illustrator was fixed.

Cardpics project is a set of free cards sets.

If you are programming a card game and are looking for free cards, Cardpics was made for you! Get a set of cards and include them in your project, as soon as your project is free.

Installing

1. `cd to the directory containing the packages source code and type
`./configure to configure the package for your system. If youre
using `csh on an old version of System V, you might need to type
`sh ./configure instead to prevent `csh from trying to execute
`configure itself.

Running `configure takes awhile. While running, it prints some
messages telling which features it is checking for.

2. Type `make to compile the package.

3. Optionally, type `make check to run any self-tests that come with
the package.

4. Type `make install to install the programs and any data files and
documentation.

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.