Free 1.02 wildfire software for linux

ummf Perl module contains a driver for UMMF.

SYNOPSIS

ummf [-I dir] [-M MetaModel] [-m Main::Module] [-o {dir|-}] [-e exporter] input ...

This is a driver for the UMMF toolkit. It translates UML input documents into the export targets specified by the -e option. If -o - is specified the output is generated to STDOUT, otherwise the output is multiplexed into files underneath the directory specified by the -o option, using files2dirs.

If input is UML-1.5, then the internal UML 1.5 meta-model (from UMMF::UML::MetaModel) is used as input.

Input files can be .zargo (ArgoUML and Poseidon for UML 1.x), .zuml (Poseidon for UML 2.x) or XMI 1.0 or 1.2 documents.

USAGE

ummf -e java -e perl -o gen test/test1.xmi

Generates Java and Perl code in directory gen from test/test1.xmi.

ummf -e perl::hibernate -o gen test/test2.zargo

Generates Java Hibernate hbn.xml file in directory gen from test/test2.zargo.

ummf -e XMI -o - UML-1.5

Generates XMI for the UML 1.5 meta-model on the standard output stream.

ummf --perl5lib

Print the PERL5LIB path needed for Perl code generated by UMMF.

ummf -L Some::Package

Loads Some::Package.

ummf -m Some::Package @args ...

Loads Some::Package and executes >.

ummf -I dir/with/perl/modules

Executes use lib dir/with/perl/modules; including modules from the specified directory in the search path.

ummf -M UMMF::Boot::MetaModel

Uses UMMF::Boot::MetaModel for the meta-model, defaults to UMMF::UML_1_5.

ummf -profile MyMagicProfile -e Perl UML-1.5

Applies MyMagicProfile during export of Perl code on the UML 1.5 meta-model. This overides the default lib/ummf/profile/UML-1.5.ummfprofile file.

xDash is a framework for application integration (EAI). xDash is using XMPP/jabber as the communication protocol and a set of agents. All the needed stuff is automatically generated from a CSV file, which can be comfortably edited in a spreadsheet editor.
xDash can be classified in marketing terms as:
- an Enterprise Application Integration (EAI) solution or
- an Enterprise Service Bus (ESB).
xDash is based on the concept of convergence between backend asynchronous messaging (like IBM MQSeries or JMS) and instant messaging (like IRC or Jabber).
Main features:
- You have to manage a fast integration project with little time and low budget;
- You are convinced, that integration has so many faces, that agile approach and flexible design are better than buying a "silver bullet" from big names;
- You are convinced, that integration is rather a continuous, never-ending process than a single act of some software implementation;
- You would like to concentrate on writing the integration logic in a well known environment and have no time to learn myriads of new options and APIs with little reuse;
- You need an open human readable communication protocol (XML), where you can see what is going on under the hood;
- You need a free open source multiplatform information bus for publish/subscribe integration;
- You are interested in a ground-breaking project dealing with the convergence of instant and backend asynchronous messaging.
What is the core of the xDash?
xDash is at basis every sort of an integration project, which sticks to the following rules:
- Communication over Jabber protocol;
- The extension of the message type to type=job for all relevant messages;
- The message sending schema, in which always participate a message sender, a message receiver and a message archivist ("integration chain").
- For each sort of event, triggering a Sender, there is only one integration chain defined on the server by a set of Jabber IDs and forwarding rules ("Who knows whom" schema).
- The client software of Sender and Receiver knows nobody but the Archivist.
- The jabber server forwards Senders messages sent to the Archivist, additionally to the Receivers.

Rocket project is a game where you try to land a rocket on a moving platform.

Running Rocket:

- Unzip the archive into its own directory.
- cd to the directory.
# perl rocket.pl

You fly the rocket with the left, right, and down keys.

Other keys:

- pause
- exit
- new game
- God mode?

NVTCom is a library to access using java RFC2217 devices, the class hide all the overhead of the telnet protocol and the special options for setting the serial port.
In java is very difficult to access serial device with this library is possible connect serial device to one terminal server and access the device from the network. NVTCom package contains both binary and source code.
NVTCom as been tested with the following hardware/software terminal server :
- Kermit sredir 2.2.0
- Simet cross
- web51
- Jts
- ser2net
But I think work with any compatible RFC2217 terminal server because I use this class in one my project from many years.

cnslock is a dock application (dockapp) which provides a visual indication of the states of the three "lock" buttons (caps, num, and scroll).

cnslock was written so that I could see the state of those keys as I have a wireless keyboard with no leds on it.

Usage:

Simply launch:

cnslock

If you have problems running it under a different window manager, such as fvwm or enlightenment, there is a command line argument that may help:

cnslock -w

libwacky provides a C library which supports the WACKY protocol.

WHAT IS IT?

libwacky is a C programming library which implements the WACKY/1.0 protocol. It allows you to send blinking commands to a wackyd. The distribution includes wackyp, a program that links to libwacky and allows you to issue commands to a wackyd from the command line.

libwacky was built with GNU autoconf. So if you are familiar with GNU
software, then you should be comfortable installing wackyd. Please
consult the file INSTALL for more details.

Pod::Hlp is a Perl module that can convert POD data to formatted VMS HLP Help module text.

SYNOPSIS

use Pod::Hlp;

pod2hlp("perlfunc.pod",$top_help_level,*Filehandle);

Also:

pod2hlp < input.pod

Also:

perl pod2hlb

Pod::Hlp is a module that can convert documentation in the POD format (such as can be found throughout the Perl distribution) into formatted VMS *.HLP files. Such files can be inserted into an .HLB library through the LIBRARY/HELP/REPLACE system call, or via the use of the pod2hlb script supplied with the kit. A separate pod2hlp program is included that is primarily a wrapper for Pod::Hlp.

The single function pod2hlp() can take one, two, or three arguments. The first should be the name of a file to read the pod from, or "