Free wedding cake toppers software for linux

Take Out The Mouse is a very entertaining puzzle game where you must help a mouse to find the exit.

This is the first game developed by Bertesh Studios, in 2001. Take Out The Mouse consist in a little mouse who has to find the exit of the different labyrinths by finding his delicious reward... the cheese.

The game has 2 difficulties. The first one is the "Easy" difficulty, where our only objective is to find the cheese before our time finishes. Once we have finish this difficulty, we will have access to the "Hard" difficulty, here besides of have to find the cheese before that our time ends, we must to eliminate all the bats that are inside the labyrinths with cakes first to be able to get access to the next level... but be careful, because this bats spit drops of blood that could damage the mouse and could cost him 1 live.

Take Out The Mouse counts with several labyrinths and funny music that we will listen during the whole game, getting a fun game for all the family.

SMSLink project implements a client/server gateway to the SMS protocol (short messages on the mobile phones).
It requires the use of dedicated hardware (a serial GSM module).
Both SMS emission and reception are supported, either in text-mode or in PDU-mode.
It also includes an SMS to eMail gateway module.
The server runs under Linux and FreeBSD and supports interactive mode via telnet.
The command-line client already exists for Linux, FreeBSD, Solaris, HP-UX, and Win32.
A basic Web interface is also provided.
Main features:
- The use of TCP/IP sockets for communication between client and server means that the application is network-aware from the start and that deploying it over a WAN (or across the internet) is a piece of cake. Expanding it as well, since writing additional clients for it is possible on any platform supporting sockets. Various ports of the client to Win32 are now available.
- The server process has a command-line interface connected to the socket, making it possible to use it interactively from a telnet session (only line mode telnet supported at the present time - see server/BUGS and server/TODO in the sources directory). This feature is of enormous help when troubleshooting or debugging.
- The command-line interface is backed by a parser written in lex and yacc (flex/bison, actually), which makes the language relatively easy to extend.
- The server was built from the start with the idea of multiple GSM modules in mind. Adding a line to two configuration files (and connecting the hardware, of course) is all there is to using two modules instead of one. The number of modules supported by the server is limited by the hardware only.
- The choice to use specific hardware (the serial GSM module), although limiting the general-purpose use of this application, allows for some very usefull features, the most prominant one being the ability to receive SMS messages as well as send them. This feature is now implemented (as of version 0.41b). Once downloaded from the GSM module, those messages can either be stored in an inbox file or fed through an external program or script, or both.
- By sitting straight on the GSM network, the use of the GSM module offers an advantage that far outweighs its cost : provider independance. The ability to send and receive SMS might be limited in some way or another by the level of your subscription, but all providers should offer a standard way of doing it. No "provider-specific driver" is required in this case. Whats more, all SMS routing aspects are being taken care of by the GSM network itself. Caution is advisable when choosing the provider though, as some of them might place some restrictions on routing to and/or from outside networks (e.g. Mobistar and Itineris*) or lack the implementation of some advanced features of the SMS protocol such as "point-to-point SMS" or "SMS-back" (e.g. Proximus through the UCP interface*).
- As of version 0.48b, initial support for PDU mode and the creation of a "driver-like" capability table for the GSM modules means that most module brands on the market could be supported with little effort. This "driver" approach also garanties that youll be able to mix and match different brands and models of modules on the same server with no problem. Support for PDU mode also opens up a new batch of options, like setting the validity period for a message, potential support for non-standard alphabet, binary content delivery to the mobile phone (logos, tunes, etc. ?) and more.
- A full-fledged access control mechanism allows you to specify precisely which client machine or subnet should be allowed to connect and which shouldnt. The access control is IP-based (as opposed to user-based) and defaults to "deny" for increased security. When the situation doesnt require any access control, the whole thing can be easily disabled by the administrator.

Aalib is a portable ascii art GFX library.I vote for simplicity. There are many problems of various kinds with video cards, low frequency monitors, crashing graphical apps@dots{} AA-lib IS the solution. It works on a terminal of any kind, it is fast and portable, it gives to you standard API. It makes your old hardware more powerfull.
AA-lib is a low level gfx library just as many other libraries are. The main difference is that AA-lib does not require graphics device. In fact, there is no graphical output possible. AA-lib replaces those old-fashioned output methods with powerful ascii-art renderer. Now my linux boots with a nice penguin logo at secondary display (yes! Like Win95 does:) AA-lib API is designed to be similar to other graphics libraries. Learning a new API would be a piece of cake!
Once upon a time weve (my friend Kamil and I) bought two old Herculeses as secondary monitors. We didnt know for that time that our Diamond Stealths 64 cards would become obsolete soon. The next day we downloaded the logo of Linux Texas Users Group - nice silly penguin looking like a cowboy! It was so exciting logo ... we decided that we couldnt live without it and we wanted to see it at boot time as a logo on our secondary monitors. There was a small problem - Hercules doesnt support color graphics. So we decided to convert the penguin image to ascii art using netpbm tools.
The output was very ugly because the converting algorithm was absolutly stupid. During the night I designed a new convertor that used a font bitmap to creat an aproximation table. The output wasnt very good since the algorithm wasnt tuned so well. Many months this small piece of code was waiting on my disc for the day "D". Meanwhile I started a new project XaoS (a fractal zoomer) with my friend Thomas. And then I got an idea: Ascii Art Mandelbrots! I was really impressed by the result! XaoS was faster, portable and looking much better than ever before. I found a new way to go @dots{}
Enhancements:
- Automake/libtools/autoconf updated.
- Package restructured
- Some bugfixes.
- New "raw" keyboard driver for linux console alowing to detect key releases.
- Fixed -malign-double gcc binarry compatibility problem
- Added const keywords to sources where possible.
- AAlib.h documented
- Lots of fixes from Debian maitainer Joey Hess installed
- c2man generated manual pages added
- Rest of changelog was lost in the disc crash....
- Fixed X driver handling of refresh
- Optimized X driver
- X driver now allows setting font using AAFont environment variable
- Added aalib-config

myGifts project enable you, your family and your friends to share your xmas wish-lists, your gift registry for your wedding or a newborn.
People can add gifts to their lists and claim other peoples gifts, and it supports user groups to control who can and cannot see lists.
Main features:
- add gifts to their lists,
- decide who can(cannot) see them,
- add ideas to other lists,
- claim other people gifts.

DL/SQL is declarative, turing-complete programming language based on top of SQL database. The main idea is to store both program and data in one SQL table and make all the computations in it.

The current version of interpreter written in PHP contains quasi-lazy evaluation and simple caching.

The syntax was inspired by LISP and bash. Sounds strange? For example,

(* (+ 2 4 (#FACT 4)) 3)


means (2 + 4 + fact(4)) * 3 where fact is user-defined function for factorial.

As youve probably noticed, DL/SQL has got prefix (polish) notation with compulsory bracketing. That means, in front any name of function there must be opening bracket and after last parameter of a function there must be closing bracket. With this rule its really easy to implement variable-length argument lists.

For real deployment its necessary to change the core according to your needs - some special constructions are always necessary. Fortunatelly the core is flexible and easily extendable. Right now DL/SQL uses MySQL as its backend. Therere only several calls to DB, changing them is work for few minutes so porting DL/SQL to lets say PostgreSQL is piece of cake.

Therere only two API calls:

rpn_init()

clears all the cached values (actually sets the counted bit to false).

rpn_eval($expression)

evaluates entered DL/SQL expression. For using DL/SQL interpreter its necessary to include file rpnparser.phtml in your project. For easy implementation I also advise you to include file include/setup.phtml which contains all the necassary stuff for connecting to database and setting the directories. Without this file, youll have to do all the things yourself!

XML::XQL is a perl module for querying XML tree structures with XQL.

SYNOPSIS

use XML::XQL;
use XML::XQL::DOM;

$parser = new XML::DOM::Parser;
$doc = $parser->parsefile ("file.xml");

# Return all elements with tagName=title under the root element book
$query = new XML::XQL::Query (Expr => "book/title");
@result = $query->solve ($doc);
$query->dispose; # Avoid memory leaks - Remove circular references

# Or (to save some typing)
@result = XML::XQL::solve ("book/title", $doc);

# Or (to save even more typing)
@result = $doc->xql ("book/title");

The XML::XQL module implements the XQL (XML Query Language) proposal submitted to the XSL Working Group in September 1998. The spec can be found at: http://www.w3.org/TandS/QL/QL98/pp/xql.html Most of the contents related to the XQL syntax can also be found in the XML::XQL::Tutorial that comes with this distribution. Note that XQL is not the same as XML-QL!

The current implementation only works with the XML::DOM module, but once the design is stable and the major bugs are flushed out, other extensions might follow, e.g. for XML::Grove.

XQL was designed to be extensible and this implementation tries to stick to that. Users can add their own functions, methods, comparison operators and data types. Plugging in a new XML tree structure (like XML::Grove) should be a piece of cake.
To use the XQL module, either

use XML::XQL;
or
use XML::XQL::Strict;

The Strict module only provides the core XQL functionality as found in the XQL spec. By default (i.e. by using XML::XQL) you get XQL+, which has some additional features.

See the section "Additional Features in XQL+" for the differences.
This module is still in development. See the To-do list in XQL.pm for what still needs to be done. Any suggestions are welcome, the sooner these implementation issues are resolved, the faster we can all use this module.

If you find a bug, you would do me great favor by sending it to me in the form of a test case. See the file t/xql_template.t that comes with this distribution.

If you have written a cool comparison operator, function, method or XQL data type that you would like to share, send it to tjmather@tjmather.com and I will add it to this module.