Free kicking software for linux

Ice Hockey Manager is a hockey simulator which has the ultimate goal of creating a game that offers the most realistic simulation experience possible. Our focus is more on substance than style.
While we want the game to be intuitive, we arent looking to compete with the flashy 3D graphics you might see in games from EA or Sega. Theyve pretty much cornered the market when it comes to pretty graphics.
Were more interested in games that challenge your mind and not your hand-eye coordination. We plan to take hockey simulators (and perhaps sports simulators in general) to places theyve never gone before, The way we see it, the possibilities are limitless, much like real life hockey.
While IHM may not have photorealistic facial features for every player model in the NHL we do strive to create a game that really does make you feel like you are at the helm of your own hockey franchise.
We first started developing IHM in late 2001 and the development team consisted of two members, Bernhard von Gunten and Arik Dasen. The first real release of the game was version 0.1.1 in January of 2002. The game was playable but still very basic, more intended as a framework for future development. In July of 2002, version 0.1.2 was released with many updates to the game but after this release the project essentially went on hiatus until September/October of 2004.
Up until that time the project hadnt garnered much interest from the open source community, either the project was too localized to Swiss-style hockey or it perhaps just didnt get the exposure needed to get people to jump onboard, whatever the reason, IHM seemed to be more of a labor of love than a project that perpetuated itself. Fortunately, in October 2004, development kicked back into gear and all sorts of new and exciting features started to take shape. Some of these features include computer AI, multiplayer-support, trading/transfers, sponsoring/finances, full season/playoffs simulation, etc.
And the IHM team is currently working towards version 0.3, which has been dubbed a "Preview Release" to demonstrate a fully-operational playable game. Will this Preview Release set any kind of standard as far as hockey simulators are concerned? No, not yet. In fact, many elements within the game are still rather simplified, such as in-game simulation (which will begin development post-0.2), but we hope the Preview Release will compel other open source developers to help out with the project as there is still a lot to be done before IHM can be considered a complete game.
This website is intended to both introduce you to the game as well as to encourage you to participate and/or contribute to this project in some way. Whether you are a Java developer, a graphic artist, a beta tester, or something else entirely, we want to hear from you. IHM cant build itself, and while we have invested many hours into the games development we still have our limitations as to what we can achieve, both in time and resources. So if you think you can help out in some way, please let us know. Ideally, you should be a fan of hockey, but thats about the only prerequisite.
Main features:
- Game controller, based on a game calendar.
- Multiuser framework
- League framework (Swiss style leagues implemented, including playoffs and relegations).
- Teams, with statistics and informations.
- Players with attributes, statistics, contracts and informations.
- Simulated matches with generated plays and "radio" output.
- Training
- Injuries
- Contracts framework
- Sponsoring framework, based on contracts
- Financial framework
- Real Impacts (on teams & players)
- Transfers (Swiss style)
- Infrastructure framework (Arena implemented)
- Prospects
- Assistants
- and more ...
Technical stuff:
- Written in 100% pure Java
- Running under Linux and Windows and every other Java 1.5 platform
- Swing GUI
- More than 200 java classes
- More than 30000 lines of code

JACK Timemachine is a tool that can record occasional bursts of interesting noise from jack apps.

I used to always keep a minidisc recorder in my studio running in a mode where when you pressed record it wrote the last 10 seconds of audio to the disk and then caught up to realtime and kept recording.

The recorder died and havent been able to replace it, so this is a simple jack app to do the same job. It has the advantage that it never clips and can be wired to any part of the jack graph.

The idea is that I doodle away with whatever is kicking around in my studio and when I heard an interesting noise, Id press record and capture it, without having to try and recreate it.

It seems to be stable for me, but there could be threading issues and race condidtions if run without SCHED_FIFO (ie. without jackd -R).

Eicq is an ICQ client written in Emacs Lisp.
It runs in SXEmacs & XEmacs.
Eicq will not run in GNU/Emacs and we have no immediate plans for porting. Were all (S)XEmacs geeks here.
Main features:
- Eicq is written entirely in elisp
- Eicq uses version 8 of the ICQ protocol.
- Send/receive messages
- Send/receive URL type messagse
- Receive authorisation request messages
- Query ICQ users meta info
- Search for ICQ users
- Dynamically add new users to your contact list
- Play sounds for different events.
- Auto online after a auto away/na.
- Auto response away/na/dnd/occ messages.
- Different auto response messages if Eicq has idled away/na
- Auto reconnect if you are kicked off ICQ.
- Gnus style smileys
- Gnus style text emphasis (underline, bold, italic, etc)
- "Clickable" hyperlinks for URLs, email addresses, and Unix manual page titles
- mICQ style per contact history logs
- ERC/Riece style modeline activity indicator
- Works in both a GUI environment and on a console/TTY
- A dockable frame that tracks the number of unread messages.
- Interactive customisation through XEmacs Custom widgets.
- Key binding, "scripting" in elisp.
- Allow other users/contacts to psycho-analyse themselves
- Display X-Face/Colour Face header images in buddy buffer.
- An "oops" function
- Customisable semi-automation
Eicq cannot yet transfer files, chat, or anything that needs a direct peer to peer connection. This isnt a limitation of Eicq, but rather a limitation of (S)XEmacs. It requires server sockets and (S)XEmacs does not (yet) support this.

TiVo::HME::Application is a Perl implementation of TiVos HME protocol.

SYNOPSIS

use TiVo::HME::Application;
our @ISA(TiVo::HME::Application);

sub init {
my($self, $context) = @_;

$self->get_root_view->visible(1);
my $mpg = $T_RESOURCE->image_file(examples/myloop.jpg);
$self->get_root_view->set_resource($mpg,
$T_CONST->HALIGN_CENTER | $T_CONST->VALIGN_CENTER);
}

sub handle_event {
my($self, $resource, $key_action, $key_code, $key_rawcode) = @_;
print "You pressed the $key_code key on the remote!n";
}

Perl on your TiVo in 11 Steps!!

Step 1: Go to http://tivohme.sourceforge.net
Step 2: Go to Step 1
Step 3: Go to Step 2 (seriously)
Step 4: Congratulations on making it here!
Step 5: Really, go to http://tivohme.sourceforge.net, download the
SDK, read the PDF files (dont worry about the protocol PDF,
thats what this is for).
Step 6: Learn about Views & Resources
Step 7: Learn about the Application cycle (init then event loop)
Step 8: Learn about Events
Step 9: Learn how the Perl stuff differs from the Java stuff
(mainly only in naming)
Step 10: View & understand the perl examples - especially how they
related to the Java examples (they do the same thing!).
Step 11: Use your imagination to create a kick-arse Perl-based HME app!!

JavaDesktopEngines aim is to produce a piece of software that is at the same time:
Shared virtual machine
It allows to launch different java programs inside the same VM. The VM will always be alive, so no more startup overhead and less memory used.
It uses our JDSVM(Java Desktop Shared Virtual Machine), which in turn is based on Javagroups great Echidna Project
Xml Rpc local server
This way it is possible for programs, even written in languages different from java, to access "services" exposed by the engine.
Plugin host
It has been built with a pluggable architecture in mind, so that it is possible to develop new "services" for the engine.
Linux/Windows service (next release)
It is run as a service, so that its "services" will always be available for other programs.
For those of us who make heavy use of java tools its always been quite frustrating to have to open lots of resource eager VMs just to launch very useful but simple programs. Moreover, VM starting for simple utilities is a real waste of time.
Weve all appreciated the difference when launching a compilation from inside an IDE. In this case javac is launched as a process inside an already active VM, and the difference is evident.
JDE in the beginning was born to try to address these problems. Having an always active VM where it is possible to launch processes in, means faster process start and less resources used. A lot of time is saved by from not loading again and again the VM.
Theres nothing new in this. Some very good related projects are alive and kicking on the net, some of them focusing on a complete Java desktop enviroment, some on just a shared VM. JDE positions itself a bit differently, as it can be seen as a java engine exposing pluggable services (shared VM being just one of these).
There are several approaches to implementing a shared VM, all of them with pros and cons. Weve chosen to use the great code from the Echidna Project for now.
The entrypoint of JDE is an XML-RPC server accepting calls for services. Everything needed from JDE can be obtained by making a call to it.
The main service exposed by JDE is obviously the java process launching one. By making a call, it is possible to launch a java process insisde the VM. Having an XML-RPC server allows us to use any language with xmlrpc capabilities to launch java programs. The package includes a simple python script, that can be easily used as launcher (see our simple tutorial for details).
Included is also a "Manager", a simple swing application with active process listing and process launching capabilities.
Hopefully, this one will evolve as far as there will be more services in JDE to be the reference manager for the engine.
Included plugins:
1) Java process Launcher. The one this project was started for. You can launch java processes inside the living VM.
2) Scripting engine. Via a simple xmlrpc call you can launch a script on the engine and get back results. The nice thing, as usual, is that being xmlrpc based, you can use it as a service called by anything written in any language. Currently supported scripting language is BeanShell. More will be available soon via BSF.
3) Fast editor Based on jEdit Syntax Package 2.2.1, a simple, fast and useful editor with only some of the nice features jEdit has got us used to.
Enhancements:
- This release should be a bit more robust when killing processes that make use of System.exit(0) without "dispose()".
- An icon for the GUI manager has been added, as well as a bat file for Windows systems.

F-IRC provides a console IRC client.
F-IRC is an IRC client for the console. It supports multiple servers, scrollback, and all the basic features one can expect from an IRC client.
When F-IRC is started, youll see a list of channels and servers on the right.
The box around these is inverted. That means that if you use the left- and the
right cursor, they will work on the channels etc. If you press ^n, the box will
no longer be inverted and you can use the cursor keys for editting what youre typing.
If the channel-box is selected, press key right on a channel to get a list of
people in that channel. Press key left to exit this (and return to the list of
channels) or press key right on a name to get a menu via which you can kick
and ban people as well as get information on them. Press left on a server to
hide all the channels for that server, press right to unhide all channels.
Press cursor right on a channel to enter that channel. If theres a star in
front of channelname, someone wrote something in that channel. Press ^w to
jump directly to the next channel in which someone wrote something.
Enhancements:
- The cursor is finally visible in the edit-line.
- The program now runs on 64-bit platforms as well.

firefix is an extension which learns and corrects mistyped web addresses typed in the address bar.

Learns and corrects mistyped web addresses typed in the address bar.
e.g. http://www.dell.con becomes http://www.dell.com
http://www.mozillao.rg becomes http://www.mozilla.org

It only ever kicks in if the address cant be found in the first place.

Tibco::Rv are Perl bindings and Object-Oriented library for TIBCOs TIB/Rendezvous.

SYNOPSIS

use Tibco::Rv;

my ( $rv ) = new Tibco::Rv;

my ( $listener ) =
$rv->createListener( subject => ABC, callback => sub
{
my ( $msg ) = @_;
print "Listener got a message: $msgn";
} );

my ( $timer ) = $rv->createTimer( timeout => 2, callback => sub
{
my ( $msg ) = $rv->createMsg;
$msg->addString( field1 => myvalue );
$msg->addString( field2 => myothervalue );
$msg->sendSubject( ABC );
print "Timer kicking out a message: $msgn";
$rv->send( $msg );
} );

my ( $killTimer ) =
$rv->createTimer( timeout => 7, callback => sub { $rv->stop } );

$rv->start;
print "finishedn"

Tibco::Rv provides bindings and Object-Oriented classes for TIBCOs TIB/Rendezvous message passing C API.

All methods die with a Tibco::Rv::Status message if there are any TIB/Rendezvous errors.