Free bouncy house software for linux

The Legion of the Bouncy Castle Java Cryptography API provides a lightweight cryptography API in Java. A provider for the JCE and JCA, a clean-room implementation of the JCE 1.2.1, generators for Version 1 and Version 3 X.509 certificates, generators for Version 2 X.509 attribute certificates, PKCS12 support, and APIs for dealing with S/MIME, CMS, OCSP, TSP, and OpenPGP. Versions are provided for the J2ME, and JDK 1.0-1.5.
Main features:
- A lightweight cryptography API in Java.
- A provider for the JCE and JCA.
- A clean room implementation of the JCE 1.2.1.
- A library for reading and writing encoded ASN.1 objects.
- Generators for Version 1 and Version 3 X.509 certificates, Version 2 CRLs, and PKCS12 files.
- Generators for Version 2 X.509 attribute certificates.
- Generators/Processors for S/MIME and CMS (PKCS7).
- Generators/Processors for OCSP (RFC 2560).
- Generators/Processors for TSP (RFC 3161).
- Generators/Processors for OpenPGP (RFC 2440).
- A signed jar version suitable for JDK 1.4/1.5 and the Sun JCE.

Acme::OneHundredNotOut is a raise of the bat, a tip of the hat.

I have just released my 100th module to CPAN, the first time that anyone has reached that target. As some of you may know, I am getting ready to go back to college and reinvent myself from being a programmer into being a missionary. I dont forsee that many more Perl modules coming out of this.

Of course, this doesnt mean that Im going to abjure usage of Perl forever; any time theres a computer and something I need automated, out will come the Swiss Army Chainsaw and the job will get done. In fact, we recently needed to manipulate some text from a mission handbook to translate it into Japanese, and Perl was there handling and collating all that.

But 100 modules is a convenient place to stop and take stock, and I hope that those of you who have benefitted from my modules, programs or writing about Perl will forgive me a certain spot of self-indulgence as I look back over my CPAN career, especially since I feel that the diversity of modules that Ive produced is a good indication of the diversity of what can be done with Perl.

Lets begin, then, with some humble beginnings, and then catch up on recent history.
The Embarrassing Past

Contrary to popular belief, I was not always a CPAN author. I started writing modules in 1998, immediately after reading the first edition of the Perl Cookbook - yes, you can blame Nat and Tom for all this. The first module that I released was Tie::DiscoveryHash, since Id just learnt about tied hashes. As with many of my modules, it was an integral part of another software project which I actually never finished, and now cant find.

The first module that I ever wrote (but, by a curious quirk of fate, precisely the fiftieth module I released) was called String::Tokeniser, which is still a reasonably handy way of getting an iterator over tokenising a string. (Someone recently released String::Tokenizer, which makes me laugh.) This too was for an abortive project, webperl, an application of Don Knuths WEB system of structured documentation to Perl. However, given the code quality of these two modules, its perhaps just as well that the projects never saw the light of day.

There are a few other modules Id rather like to forget, too. Devel::Pointer was a sick joke that went badly wrong - it allowed people to use pointers in Perl. Some people failed to notice that referring to memory locations directly in an extremely high-level language was a dangerous and silly thing to do, and actually used the damned thing, and I started getting requests for support for it. Then at some point in 2001, when I should really have known better, I developed an interest in Microsofts .NET and the C# language, which I still think is pretty neat; but I decided it might be a good idea to translate the Mono projects tokenizer and parser into Perl, ending up with C::Sharp. I never got around to doing the parser part, or indeed anything else with it, and so it died a lonely death in a dark corner of CPAN. GTK::HandyClist was my foray into programming graphical applications, which started and ended there.

Bundle::SDK::SIMON was actually the slides from a talk on my top ten favourite CPAN modules - except that this changes so quickly over time, it doesnt really make much sense any more.

Finally, Array::FileReader was an attempt to optimize a file access process. Unfortunately, my "optimization" ended up introducing more overheads than the naive solution. It all goes to show. Since then, Mark-Jason Dominus, another huge influence in the development of my CPAN career, has written Tie::File, which not only has a better name but is actually efficient too.

The Internals Phase

1999-2000 were disastrous years for me personally but magnificent years Perl-sonally. Stuck in a boring job and a tiny flat in the middle of Tokyo, I had plenty of time to get stuck into more Perl development. I felt that getting involved with perl5-porters would be a good way of gettting to know more about Perl, and so I needed a hobby horse - an issue of Perls development that I cared about. Since I was in Japan and working a lot with non-Latin text, Unicode support seemed a good thing to work on, and so Unicode::Decompose appeared, while I fixed up a substantial part of the post-5.6 core Unicode support.

Id recommend this way to anyone who wants to get more involved in the Perl community, although I was very lucky in terms of who else happened to be around at the time: Gurusamy Sarathy was extremely gracious in helping me turn my fledgling C code into something fit for the Perl core, and he also helped me understand the perl5-porters etiquette (yes, there was some at the time) and what makes a good patch, while Jarkko Hietaniemi was always good for suggestions of interesting things for keen people to work on. Seriously, get involved. If I can do it, anyone can.
Anyway, this fixation with understanding the Perl 5 internals, and especially the Perl 5 compiler, (due to yet another of my Perl influences, the great Malcolm Beattie) led to quite a torrent of modules, from ByteCache, an implementation of just-in-time compilation for Perl modules, through B::Flags and B::Tree to help visualising the Perl op tree, to uninit, B::Generate, optimizer and B::Utils for modifying it.

Perl About The House

Now we abandon chronological order somewhat and take a look at the various areas in which Ive used Perl. One of these areas has been the automation of everyday life: checking my bank balance with Finance::Bank::LloydsTSB (the first Perl module to interface to personal internet banking, no less) and my phone bill with a release of Tony Bowdens Data::BT::PhoneBill.

Finance::Bank::LloydsTSB was meant to go with Finance::QIF, my Quicken file parser, to produce another now-abandoned idea, a Perl finances manager. It seemed that Im only capable of producing modules, not full standalone applications - or at least, it seemed that way until I produced Bryar, my blogging software, based on the concepts from Rael Dornfests blosxom and beginning my adventures with Andy Wardleys Template Toolkit. Bryar also tuned me in to the Model-View-Controller framework idea, of which more later.

Another project I briefly played with was a personal robot, using the Sphinx/Festival speech handling and recognition modules from Cepstral and Kevin Lenzo. I didnt have X10, so I couldnt shout "lights" into the air in a wonderfully scifi way, but I could shout "mail" and have a summary of my inbox read to me, "news" to get the latest BBC news headlines, and "time" to hear the time. Of course, getting computers to tell the time nicely takes a little bit of work. I dont like "Its eleven oh-three pee em", since thats not what someone would say if you asked them the time. I wanted my robot to say "Its just after eleven", and thats what Time::Human does. Shame about the localisation.

Tornado project is a clone of the original C64 game.

The goal of the game is to destroy the opponents house with certain weather phenomena: rain, snow, hail, lightning, and the tornado.

The game can be played together (two players), against the computer (or two computer players against each other) or over a TCP connection.

UMLSpeed project is a compiler for a simple, C-style language that allows declaration of UML entities and diagrams. Diagrams can be compiled into SVG and the entities to XMI for use with other tools.
Why?
- Graphical UML tools in general suck - why should we, as programmers have to drag and drop stupid graphical things and use a mouse when we could express what we want 10 times faster with a text editor and a simple notation? - More importantly, why should we have to lay everything out when the computer could do it for us?
- Graphical UML tools are bloated, huge, memory and disk-hogging monsters.
- Graphical UML tools use either a binary data format or XML, which is not particularly friendly to source code control systems.
Main features:
- Written in GCJ-portable java and compiled natively. Its extremely fast even when dealing with thousands of entities and diagrams.
- Purely command-line driven and takes miniscule resources.
- Flexible enough with file imports that large UML projects can be broken up into separate files and only individual bits built at a time as required.
- C-style syntax means that the source language integrates well with source code control and diff tools.
- Standards compliant - produces interoperable SVG and XMI, as well as clean source code.
- Can integrate with automated build tools for regular diagram/xmi compilation.
Status
This is still alpha software. Dont hold me responsible if it kills your pets and blows your house up.
Implemented so far:
- Compiler/parser
- Namespaces, Class diagrams and related entities
- Use case diagrams and related entities
- Auto-link pathfinding
- XMI 1.3 output
- VIM syntax highlighting
- Code generation (Java and Python)
Still to do:
- Documentation output
- Code generation (Ruby, PHP, Perl, C++, C#)
- Diagram packages
- Diagram notes
- Alternative diagram layout managers
- Deployment diagrams
- Sequence diagrams
- Activity diagrams
Enhancements:
- Added facilities to store HTML of reports in a buffer for use by plugins and turn off file generation. Maven plugin now uses this when using Doxia for generation.
- Added $PROJECTNAME and $PROJECTVERSION HTML tokens, with CLI parameters to set them. Maven plugin will automatically set them.
- Added $PUBLISHDATE token
- Added $TOC key for generating links to bookmarks on the same page.

Penrose project is a virtual directory server. A Virtual Directory technology is a fairly new approach for centralizing and reducing the amount of directories needed without the problems of physical data migration.
Instead of creating new identity repositories, virtual directory handles identity queries on a case-by-case basis, drawing the required, authorized data (and only the required data) in real time from its native repositories around a network and presenting it to an enterprise application as needed.
Virtual Directory eases deployments of Identity management solution, reduces political fights over data ownership and changes how corporate data is being managed.
Main features:
- Namespace conversion, attribute value modifications, schema adaptations
- Adapters to Active Directory, LDAP and JDBC back-end.
- Join-engine allows attribute transformation via beanShell scripting (JSR 274).
- GUI-based administration and mapping Tool based on eclipse RCP 3.1 platform
- Direct browsing of LDAP and RDBMS-based information to provide easy-to-use mapping.
- Live preview of your virtual directory.
- Remote management via JMX (JSR 160)
- Open-source.
- 100% Java.
- Run stand-alone as a backend for ApacheDS and OpenLDAP.
- Run embedded in your application
- Flexible Access Control
- Conversion and manipulation of Attribute values
- High performance join and cache engine
- Data encryption using Bouncy Castle
- Supports resource connectors for JDBC/SQL, JNDI/LDAP, Active Directory.
- Remote management via JMX.
- Extensible via plug-ins.

Cross-LFS stands for Cross Linux From Scratch (CLFS) and is a project that provides you with step-by-step instructions for building your own customized Linux system entirely from source.

Why would I want a CLFS system?

Many wonder why they should go through the hassle of building a Linux system from scratch when they could just download an existing Linux distribution. However, there are several benefits of building CLFS. Consider the following:

CLFS teaches people how to build a cross compiler

Building CLFS teaches you how to make a cross-compiler and the necessary tools, to build a basic system on a different architecture. For example you would be able to build a Sparc toolchain on an x86 machine, and utilize that toolchain to build a Linux system from source code.

CLFS teaches people how to utilize a multilib system

CLFS takes advantage of the target systems capability, by utilizing a multilib capable build system.

CLFS teaches people how a Linux system works internally

Building CLFS teaches you about all that makes Linux tick, how things work together and depend on each other. And most importantly, how to customize it to your own tastes and needs.

Building CLFS produces a very compact Linux system

When you install a regular distribution, you often end up installing a lot of programs that you would probably never use. Theyre just sitting there taking up (precious) disk space.

CLFS can be built from most Unix Style Operating Systems

You can build CLFS even if you dont have Linux running. Our build instructions have been tested to build from Solaris and the BSDs.

CLFS is extremely flexible

Building CLFS could be compared to a finished house. CLFS will give you the skeleton of a house, but its up to you to install plumbing, electrical outlets, kitchen, bath, wallpaper, etc. You have the ability to turn it into whatever type of system you need it to be, customized completely for you.

CLFS offers you added security

You will compile the entire system from source, thus allowing you to audit everything, if you wish to do so, and apply all the security patches you want or need to apply. You dont have to wait for someone else to provide a new binary package that (hopefully) fixes a security hole. Often, you never truly know whether a security hole is fixed or not unless you do it yourself.

What can I do with my CLFS system?

A by-the-book CLFS system is fairly minimal, but is designed to provide a strong base on which you can add any packages you want. See the BLFS project for a selection of commonly used packages.

php-residence is designed to manage weekly or daily rental of house apartments or small hotel rooms. php-residence uses a MySQL or PostgreSQL database as a backend. Reservations can be assigned to an apartment automatically with user-defined rules.
Main features:
- Software released under GPL licence (free and modifiable).
- Automatic assignment of the apartments with user defined rules. Details -->
- Configurable in number and characteristics of the apartments, periods, rates...
- Possibility to add weekly-daily or percentage extra costs to the rates. Details -->
- Visualization of contracts with inserted data for printing.
- Creation of templates to check availability from an internet site.
- Multi-user with privileges system. Details -->
- Backup all your data on a single text file.
- In english, italian and spanish.
Enhancements:
- Support was added for the sqlite database, recording of guests data, and assignment of reservations in close apartments.