Free software for machinima software for linux

Bowzilla is a mini Game for 2 players. Leaned against the old QBasic Gorilla, you must fire at your opponent in real-time.

Particularly the realistic blood is to be considered with the lightning strike. You have to find a whole in the target range. However, you should not expect to much from it.

Sparklines are intense, simple, wordlike graphics.
Theres a PHP library for producing sparklines, and even a sparkline web service, but I wanted something I could use to generate sparklines in both Java and JSTL (and I thought it would be a fun project). (Its also worth checking out Whys minimalist python sparklines, which encode the image data directly in the HTML as a data: URI [this library allows you to encode the images as using either data: format or javascript: format (supported by IE) in JSTL])
JSTL examples
< %@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" % >
< %@ taglib prefix="spark" uri="http://www.representqueens.com/taglibs/spark" % >
< c:set var="test" value="5, 35, 22, 19, 16, 10, 4, 33, 9, 12, 27, 36, 22" / >
< img src="< spark:bar name="test" color="red" / >" / >
will produce:
(I think the default size might be a little large).
The "name" attribute specifies the key to find the data (Uses JspContext.findAttribute). It expects the value to be either a List , a Number[], or a String of comma separated int values. Its the only manditory attribute.
The other attributes are width, height, spacing, color, highColor, lastColor, output. You can replace "bar" with "line" to get a linegraph (note: highColor and lastColor are currently not supported for line graphs).
The color attributes can either be a color name (a field name from java.awt.Color), or a HTML hex color (e.g. #ff0000 for red).
Enhancements:
- This release properly URL encodes parameters for server generated sparklines.
- This fixes an issue when using hex specified image colors.
- The tag parameter "background" has been added as a workaround for IE6 PNG transparency.

Ivy is a simple protocol and a set of open-source libraries and programs that allows applications to broadcast information through text messages, with a subscription mechanism based on regular expressions.
Ivy libraries are available in C, C++, Java and Perl, on Windows and Unix boxes and on Macs. Several Ivy utilities and hardware drivers are available too.
Ivy is currently used in research projects in the air traffic control and human-computer interaction research communities as well as in commercial products. It is also taught to CS students.
Ivy is a CENA product.
Main features:
- Ivy is not based on a centralised server. Actually, Ivy is mostly a communication convention, implemented through a collection of libraries for various languages and platforms. The current version of the Ivy protocol is version 3, which has been stable for the last 3 years.
- Language bindings are available in C (Unix and Windows), C++ (Mac, Unix, Windows), Java and Perl. There have been successful uses through the C library
- Messages are formatted in text, and subscriptions are based on regular expressions. Plans to move to an XML-based subscription language are on their way.
- From the programmers point of view, Ivy is an information broadcasting channel. The main functions are:
- connecting to a bus. Example: IvyInit (b, "192.126:2011")
- sending a message. Example: IvySend (b, "HELLO %s", world)
- binding a message pattern to a callback function. Example: IvyBind (b, "HELLO (.*)", cb)
- the main loop. Example : IvyLoop ()
- Subscriptions are managed on the emitters side, which limits the actual network traffic.
- Direct point-to-point messages are also available.
- Ivy was designed by a research group in Human-Computer Interaction, with the goals of connecting applications written on different toolkits/languages/platforms (such as an OpenGL application on a SGI connected to a PerlTk application on a Linux box), while keeping it simple: no server to be lauched and supervised, a simplistic API, and a communication model compatible with classical event-based GUI progamming. We think we have somewhat reached our goal...
Enhancements:
- This release mostly contains bugfixes and code cleanup.

Software Engineering Environment (SEE) is frame for manufacturing information. It is implemented in sevlet and xml, and is used by the web-browser.
Software Engineering Environment (SEE) attempts to provide the information manufacturing platform for software development.
SEE is a free project, that is the author will provide all of its source code at the same time.
It runs in any servlet environment (The author merely verified in the Win and Linux environment), not using any special technique and needs no auxiliary program.
All of its data are saved in XML files, and need not database. (The future release will support the option of saving data, so that the user can select some free database, such as mysql, or commercial database to improve SEE speed.)
This means that the user can run SEE without any money. (Tomcat is a free servlet environment.)
User uses all SEE functions with the web-browser. So information sharing is very convenient.
SEE supports Simplified Chinese, Traditional Chinese, and English now.( It will support any language if someone will translate.) User can switch to interfaces in different language at any time when SEE is running. And user can add language translations which will work at once.
The main body of SEE is a frame for information manufacturing. All information included in it can be costumed dynamically and all changes will get into effect immediately. This means that the user can modify or add her/his own information structure as will at any time.
SEE provides various predefined selections for information attributes, which correspond various predefined information manufacturing patterns. The user can focus on the information description when costuming information definition, and the system will implement the functions automatically. This is the core of SEE. Most functions of SEE are in this model.
The default information definition of SEE is the result that the author understands what is the Software Engineering.
Although the target of SEE is helping for software development, actually, user can use it to design any type information, such as book registering, personnel lists, and financial reports etc.
The speed of SEE is not bad. Reading and writing 20000 records needs no more than 1 second. At present, the sorting speed is 9 seconds for 5000 records. (The testing platform is 1.8G CPU and 256M memory)
Enhancements:
- The data interface to prepare supporting databases.
- The databases are not supported in this release.
- A new interface style "Beautiful Flowers".
- These flowers are photoed in parks in this year by the author.
- The author likes the honeybee who holds a flower in its mouth very much. It is the first cartoon figure by the author. It will appear when you save wrong data. :)
- The function of "Personal Message".
- User can only query the messages sent by and sent to herself/himself. And user can only remove the messages sent to herself/himself.
- After a user read a message sent to her/him, SEE will mark it as "have_read" automatically.
- The number of new arrived messages will be shown in the interface.
- The data privileges management
- When user "Remove All" or "Modify All", the "base conditions" will be checked at first. That is user can only do what she/he can do.
- The Password fields values can not be visited, except when the user, who owns the "Import" privilege to current data, exports the data.
- All the data structures of ACL tables are changed! Their keywords become the "Title". This will permit user define better ACL.
- And the "condition" in the ACL tables are implemented completely. Now any "SEE conditions" is valid.
- Snapshot for image file
- When list the data, a snapshot will be shown for the image files type, which may end with jpg/jpeg/gif/png.
- Data sorting concerned with langauges.
- Thus when sorting data in Chinese, the result is Chinese result.
- General users can not visit the "User" table! Then they can not fill in many data!
- This is a fatal bug! This means all former releases can not be used actually!
- Now all ACL tables are redesigned.
- When a new user is added without password, SEE will add some password itself! Then this new user can never login!
- This is another fatal bug!
- In the last English release, which is 0.06, the ACL data are in Chinese!
- So the English users can not use SEE at all~~
- This is still a fatal bug!
- The "Risk Items" in the table "Deviation Handling" is wrong defined.
- This will cause an error information when user clicks the "Select" button.
- The values of Password fields can be visited when query or export.
- Although the values are meaningless encoded codes, they are still security thread.
- When some quota marks in the key values, pages will report errors and the function buttons, such as Modify and Remove, can not act!
- This is because quota is also an element of web page.
- When the interface language changes, the language in audit records changes too!
- This is not permitted. Language of all data is determined when SEE is installed and can not change with interface!

Software::Packager::Svr4 is the Software::Packager extension for System VR4 packages.

SYNOPSIS

use Software::Packager;
my $packager = new Software::Packager(svr4);

This module is used to create software packages in a format suitable for installation with pkgadd.

FUNCTIONS

new()

This method creates and returns a new Software::Packager::SVR4 object.

add_item()

$packager->add_item(%object_data);

Adds a new object (file, link, etc) to the package.

package()

$packager->package();

Create the package.

info

This method returns a hash that is filled with the necessary information for a pkginfo file that conforms to the SYSV format.

package_name()

Define the package name.

program_name()

This is used to specify the full package name.

The program name must be less that 256 charaters.

For more details see the pkginfo(4) man page.

architecture()

The architecture must be a comma seperated list of alphanumeric tokens that indicate the architecture associated with the package.

The maximum length of a token is 16 charaters.

A token should be in the format "instruction set"."platform group" where:

instruction set is in the format of `uname -p`

platform group is in the format of `uname -m`

If the architecture is not set then the current instruction set is used.

For more details see the pkginfo(4) man page.

version()

This method is used to check the format of the version and return it in the format required for SVR4.

The version must be 256 charaters or less.

The first charater cannot be a left parenthesis.

The recommended format is an arbitrary string of numbers in Dewey-decimal format. For more datails see the pkginfo(4) man page.

install_dir()

$packager->install_dir(/usr/local);
my $base_dir = $packager->install_dir;

This method sets the base directory for the software to be installed. The installation directory must start with a "/".

compatible_version()

$packager->compatible_version(/some/path/file);
or
$packager->compatible_version($compver_stored_in_string);

my $compatible_version = $packager->compatible_version();

This method sets the compatible versions file for the software to be installed.

space()

$packager->space(/some/path/file);
or
$packager->space($space_data_stored_in_string);

my $space = $packager->space();

This method sets the space file for the software to be installed.
request_script()

$packager->request_script(/some/path/file);
or
$packager->request_script($request_script_stored_in_string);
my $request_script = $packager->request_script();

This method sets the space file for the software to be installed.

Software::Packager::Rpm is a suite of Perl modules providing a common interface for
the creation of platform specific software installation packagers.

add_item()
my %object_data = (
SOURCE => /source/file1,
TYPE => file,
KIND => doc,
DESTINATION => /usr/local/file1,
USER => joe,
GROUP => staff,
MODE => 0750,
);
$packager->add_item(%object_data);

This method overrides the add_item method in Software::Packager. It adds the ability to add extra features used by RPM for each object in the package.

For more details see the documentation in: Software::Packager Software::Packager::Object::Rpm

program_name()
$packager->program_name(SoftwarePackager);
my $program_name = $packager->program_name();

This method is used to set the name of the program that the package is installing. This may in should be the same as the package name but that is not required. It must not contain spaces or a dash "-" and must be all on one line.

version()
$packager->version(1.2.3.4.5.6);
my $version = $packager->version();

This method sets the version for the package to the passed value. The version passed cannot contain a dash "-" or spaces and must be on one line.

release()

This method sets the release version for the package. The release is the number of times the package has been recreated. If the release is not set then a default of 1 is used. It cannot contain spaces, a dash or new lines.

copyright()

This method sets the copyright type for the package. This should be the name of the copyright

source()

This method sets the source location for the package. This should be the URL for the source package used to create this package.

architecture()
$packager->architecture("sparc");
my $arch = $packager->architecture();

This method sets the architecture for the package to the passed value. If no argument is passed then the current architecture is returned. This is the output "from uname -p"

package_name()
my $name = $packager->package_name();

This method returns the name of the package that will be created.

short_description()

$packager->short_description("This is a short description.");
my $description = $packager->short_description();

The short description is just that a short description of the program. It must be all on one line.

description()
$packager->description("This is the description.");
my $description = $packager->description();

The description method sets the package description to the passed value. If no arguments are passed the package description is returned.

The discription can be of any length. It will be formatted by RPM in the following way:
If a line starts with a space it will be printed verbatim.

A blank line signifies a new paragraph.

All other lines will be assumed to be part of a paragraph and will be formatted by RPM.

package()

This method creates the package and returns true if it is successful else it returns undef

Software::Packager::Perl is used to package perl modules ready for installation and or distribution.

SYNOPSIS

use Software::Packager;
my $packager = new Software::Packager(perl);

It creates packages in the same format used to install all Perl modules.

FUNCTIONS

new()

This method creates and returns a new class object.

package()

This method overrides the base API and implements the required functionality to create Perl software packages.