Free fourth of july software for linux

Realms of Rivalry is an online tactical rpg. Play short skirmishes in random-generated game worlds.
The game can be summarized as an online graphical turn-based strategy/rpg game where you can play short tactical skirmishes with 2-4 players in small random-generated game worlds. The game is free and can be played either as an applet or downloadable client.
The time-limited turns (30-90 secs) give the game a semi-realtime feel, and the game has sometimes been characterized as "chess on steroids".
Main features:
- Community friendly game lobby where you can chat with others and join realms.
- Up to 4 players simultaneously battling on the same realm.
- Players control teams of 3 characters: Warrior, Archer and Mage.
- Time-limited turn-based gameplay.
- Random-generated game worlds (realms).
- CPU controlled monsters.
- Several weapons, armor, traps and other items.
- Occlusion calculation used in combat situations.
- Interrupts.
- Different types of terrain.
- Buy & sell items at vendors.
- Monster respawning.
- Ingame chat.
- Detailed end-of-game summary panel.
Explore the map and kill creatures to obtain weapons, potions, runes, traps and more to aid you in your quest for domination!
The game development has been very "test-driven" in the sense that the game quickly was made playable and that features and changes were added and removed continuously during development. This hopefully improves gameplay, but of course at the expense of dramatically increased development time.
Realms of rivalry was never intended to "soothe the masses", but were made entirely to match the game that we ourselves would like to play - something we have done for many, many hours :-) But of course, some of you might enjoy this game aswell, and that is why we decided to share it with you!.

Secret of Eternia project is a 2D RPG using ClanLib.
The eaisest way to get started is to use an example map from the game itself. Open up (File-Open) the first map in the maps/ folder (maps/1.fmp). You will notice that the map looks exactly like the first screen of the game demo!
You will notice the screen is divided into 2 main sections. The larger section is the preview of the map you are working on. The left side menu is a listing of all avaliable blocks that you currently have in the map. You can click on a block to set it as your current brush. This is similar to choosing a paint color in a paint program. Once you select a block, you can then edit the map by clicking in the map area. This is the generic way to edit the map.
Play around with this map to create some different landscapes and such using many blocks. You can even save the map and start up SoE to see your changes! (Make sure you have a backup of the original map, or you will have to download the game again).
Enhancements:
- Bug fixes! See the forum for detailed information.
- Lua support is added in. (see docs/ for how to use this)
- Lighting effects are here!
- Fully Working Windows Support

SKForum project is a forum application with a Wiki, comic system, guestbook, and address book.
SKForum is an open source (see licensing) web-based J2EE forum application. But its so much more, its a comic system, an addressbook, a wiki, a timetracking system, a todo list, a poll system, a guestbook system and a few other small nuts and bolts.
SKForum was first taken into use in september of 2000. By july of 2001 it had grown to 6 464 lines of code, and at october 2003 it is at 49 067 lines total. Of these 37 596 are java source file lines.
Internationalization
SKForum has i18n support and supports the following languages:
- English (US)
- Swedish (SE)
- French (FR)
Installation howto
1. Install mysql.
2. Create a database in mysql called "forum".
3. Install Java 2 SDK
4. Install a J2EE servlet container, I recommend Resin 2.x (it is also a webserver and can be integrated with IIS or Apache if you want)
5. Get the SKForum WAR file.
6. Make sure theres no caching done on the forum, resin for example has a default caching setting, remove the part of the config.
7. Install the forum as a toplevel app. It will currently not work unless "/" leads to its own top level.
8. Set up the data sources. If needed install the JDBC driver in the servlet container (get the mysql driver here).
Setup data source in Resin 2.x
Setup data source in Resin 3.x
Setup data source in Orion
9. This step only if you do not use Resin: If you use tomcat, remove web.xml and rename tomcat-web.xml to web.xml. Otherwise comment out the parts of web.xml that is marked "resin specific" that your server does not support.
10. Get the mysql jdbc driver and put it in your app servers lib directory.
11. Login with the username and password you want for the admin account. The first person who logs into the forum will get full rights and be set up as admin by default.
Enhancements:
- features:
- tasks system added
- description field for areas
- add/remove areas to/from hotlist inside the area
- invitation support for user groups
- planning warns for close events in the hotlist
- custom area type: quotes
- custom area type: pictures
- custom area type: links
- wiki URL rewriting for good wiki URLs
- editing and posting redirects instead of forwards, no more issues with reposting
- added login success/failure logging to database
- bugs:
- checkbox bug in IE fixed
- user addition delay fixed
- fixed address book VCS export for OS X
- planning info box at the bottom displayed at the top
- subscribe broken for comics
- shows deleted status for single-line messages in dynamic collapsing mode
- access rights to areas were ignored
- issue with hotlist resolved
- cant write in empty area
- editing of planning events sometimes fail
- sorting in archive is by unicode, not by character
- improvements:
- switched all maps and arrays to use fastutil
- zip download for archive give a good filename

ipsort script sorts a STDIN of IP addresses to STDOUT. It sorts by the first octet, then by the second, the third and the fourth.

Usage: Takes Standard in or a file or list of files. So ipsort < file1 > < file2 > or cat < file > | ipsort
Its quite clever and looks for an IP address on each line, rejecting if it doesnt find one

Options:

-c or --commas Separate the list by space-separated commas, rather than one IP per line.
-u or --unique Uniquely sort the list as well, to avoid duplicate IPs.
-s or --string Use this string to separate the IPs. Eg. -s :
-m or --multiple Search for multiple IP addresses per line.
-h or --help Display this usage message.

Tk::Month is a calendar widget which shows one month at a time.

SYNOPSIS

use Tk;
use Tk::Month;

$m = $parent->Month(
-month => July,
-year => 1997,
-title => %b %y,
-command => &press,
-printformat => %e,
-navigation => [0|1],
-includeall => [0|1],
-showall => [0|1],
-first => [0|1|2|3|4|5|6],
)->pack();

$m->configure(
-month => July,
-year => 1997,
-command => &press,
-printformat => %e %B %Y %A,
-navigation => [0|1],
-includeall => [0|1],
-showall => [0|1],
-first => [0|1|2|3|4|5|6],
);

$m->separator();
$m->command(
-label => Label,
-command => &callback,
);

Apache Portals is a collaborative software development project dedicated to providing robust, full-featured, commercial-quality, and freely available Portal related software on a wide variety of platforms and programming languages.

This project is managed in cooperation with various individuals worldwide (both independent and company-affiliated experts), who use the Internet to communicate, plan, and develop Portal software and related documentation.

Modern software is complex and expensive, which has motivated many companies to invest in enterprise portals as a mechanism by which they can manage information in a cohesive and structured fashion.

Portals offer many advantages over other software applications. First, they provide a single point of entry for employees, partners, and customers. Second, portals can access Web services transparently from any device in virtually any location. Third, portals are highly flexible; they can exist in the form of B2E intra-nets, B2B extra-nets, or B2C inter-nets. Fourth, portals can be combined to form a portal network that can span a companys entire enterprise system, allowing for access both inside and outside the firewall.

Portals have many advantages, which is why they have become the de facto standard for Web application delivery. In fact, analysts have predicted that portals will become the next generation for the desktop environment.

Portals distinguish themselves from other software systems because they provide the ability to integrate disparate systems and leverage the functionality provided by those systems. As such, they are not mutually exclusive, and do not force you into an either-or decision vis-a-vis existing software systems. This point is of paramount importance, particularly when you consider the fact that Web services are destined to fuel the explosion of Web applications. Since portals can access any Web services, the conclusion is inescapable: portals provide a unique opportunity to leverage the functionality of nascent technologies as well as mature, well-established software systems.

ferrisfuse is a FUSE module for mounting libferris filesystems through the Linux kernel.
About libferris
In non technical terms libferris makes the file system and other hierarchical storage systems easier to use. For the geeks out there, libferris is a virtual file system (VFS) that runs in the user address space. The FAQ contains entries related to installation, configuration and the usage of libferris.
As of July 2005 libferris can mount many interesting things ranging from a filesystem from your local Linux kernel through to LDAP, Evolution, PostgreSQL, dbXML, and RDF. To get an impression of the current capabilities of libferris mounting see the plugins/context directory of the lastest release. New things to mount are always being added.
Other than mounting things as a filesystem, the other core concept of libferris is extraction of interesting metadata from your libferris filesystems. This means that simple things like width and height of an image file become first class metadata citizens along with a files size and modification time. The limits on what metadata is available extend far beyond image metadata to include XMP, EXIF, music ID tags, geospatial tags, rpm metadata, SELinux integration, partially ordered emblem categories and arbitrary personal RDF stores of metadata.
Though some consider the last point of purely academic interest the end result is that you can add metadata to *all* libferris objects even those you only have read access too, for example, you can attach emblems to this website just as you would a normal file. The metadata interface gives all metadata from file size to digital signature status information equal standing. As such you can sort a directory by any metadata just as easily as you would ls -Sh to sort by file size. Sorting on multiple metadata values is also supported in libferris, you can easily sort your files by mimetype, then image width, then modification time with all three pieces of metadata contributing to the final directory ordering.
Late in 2004 extensive support for both fulltext and metadata indexing was added to libferris. This means you can supply queries against the contents or metadata of any libferris accessable object and have the results returned as a virtual filesystem. With the above mentioned metadata available for searching, finding your files can be done in many different ways instead of being forced to generate fixed directory trees using part of a file collections semantics as directory names. The metadata and virtual filesystem play together here allowing you to geospatially tag both your digital pictures, trip plans, and relevent websites and recall these objects in a single virtual directory no matter what their path or URL may be.
There is also a Samba VFS module which allows you to expose a libferris filesystem as a Samba share. Kfsmd uses the inotify kernel interface to allow libferris to watch changes made to your kernel filesystem by non libferris applications and update its indexes appropriately. Ferriscreate provides a command line and GTK+2 application for creating "new files" with libferris. With this you can create a new db4 database, dbXML database or fulltext index just as easily as you can make a regular file.
The ego filemanager is a GTK+2 interface built on top of libferris. It provides GTK treeview , gevas/edje and gecko based interfaces and makes extensive use of libferris clients to provide its functionality.
If you have a project you wish to use libferris with and want extensions made dont hesitate to contact one of the developers to arrange consulting.
For the geeks out there, libferris is a virtual file system (VFS) that runs in the user address space. At the moment libferris is a shared object that each application can dynamically link to in order to see the file system through a nicer abstraction.
New additions to the XML module allow for data to be converted from one format to another by the VFS for you. To copy data to an XML file:
fcreate --create-type=xml --rdn=2.xml root-element=fred /tmp
gfcp -av Makefile.am --dst-is-dir /tmp/2.xml/fred
To copy data to a db4 file
fcreate --create-type=db4 --rdn=2.db /tmp
gfcp -av Makefile.am --dst-is-dir /tmp/2.db
Ferris presents a C++ interface that makes heavy use of the STL and IOStreams. Currently ferris has two main internal abstractions: Context and Attribute. A context is much like a traditional file or directory in a file system, the major differences being that a context can have both byte content (like a file) and subcontexts (like a directory). An attribute is a chunk of metadata about a context. Contexts can have many attributes.
Some attributes may be large, for example a base 64 encoded version of the contexts content (133% context size). On the other hand an attribute can be small, for example the file size is exposed as an attribute.
Access to all contexts and attributes is performed by first requesting either an IStream or IOStream for that context or attribute. In this way the same context/attribute can be open many times at the same time, just like normal kernel based IO.
Ferris uses Loki from "Modern C++ Design" by Alexandrescu. Most objects use automatic garbage collection based on the SmartPtr template class from Loki. Where possible objects in ferris use a FerrisRefCounted policy to provide COM like intrusive reference counting. This style is used for Context, Attribute and special wrappers of IOStreams that are provided. IOStreams are wrapped to provide a more flexible API than could be offered using references to IOStreams.
There are also new stream classes provided, for example NullStream and LimitingStream. Templates are provided to make SmartPtrs to standard IOStreams act just like the underlying stream would, for example, one can have SmartPtr ss; ss >> stringObj; and does not have to dereference the SmartPtr to use standard IOStreams extractors or inserters.
Ferris uses GModule from glib2 to dynamically load both context and attribute classes at run-time. This way resources are conserved until they are needed. The native file system context is statically linked to ferris at present. When loading either contexts or attribute classes ferris uses a double dispatch factory method. Put simply this means that for each plugin there are two libraries, one that tells ferris if the main one really needs to be loaded or not. Using this scheme ferris can load all the meta factory classes at any time and use these very small meta factories to check if the main factory can create objects that are going to be useful.
This scheme is of great use for attribute classes. Attribute classes take a context and can "generate" attributes from the context. An example of this sort of class would be a MD5 or Base64 attribute. Both can be generated from the base context. More interesting attributes are PCM audio and RGBA-32bpp image data. By using the double dispatch factory ferris can handle a great deal of attribute generators and load them on demand.
Ferris currently can decode mp3, read id3 tags, decode many image formats and break some animation formats into frames. This makes ferris a solid starting point for multimedia applications.
Ferris will automatically mount sub file systems for you. Examples of a sub file system include a Berkeley database or XML file. For example it is possible to read a context such as /tmp/myxml.xml/mynode. Using this automatic mounting the differences between storage formats effectively disappear. To a ferris enabled application loading data from a native disk file, a Berkeley database, and XML file, or mbox file appear to be the same. This allows the user of the application to choose the correct storage for the data at hand.
It is planned to move to a microkernel architecture in Version 2.1 of ferris. I choose 2.1 so that ferris does not fall into version 2 syndrome.
Enhancements:
- Many changes were made to better support rsync(1).
- Extended Attribute support was greatly improved.
- write() now also updates mtime.

PythonCAD is a CAD package written, surprisingly enough, in Python. PythonCAD project aims to produce a scriptable, open-source, easy to use CAD package for Linux, the various flavors of BSD Unix, commercial Unix, and other platforms to which someone who is interested ports the program. Work began on PythonCAD in July, 2002, and the first public release was on December 21, 2002.

The twenty-fifth release of PythonCAD was made available May 26, 2005. This release fixes several compatibility issues found when running PythonCAD on PyGTK releseses prior than 2.4. Also, numerous changes to the event handling code have been applied to make the code better conform to GTK+/PyGTK conventions. Additionally a number of bug fixes and code improvements appear in this release as well.

Between the sixteenth and seventeenth releases of the program, the code was moved around internally to better cooperate with other Python programs. Unfortunately the Cocoa front-end code has suffered since then due to lack of maintainence and is currently not functional. Releases after the seventeenth release have attempted to improve the situation, but to no avail. A developer or team of developers running Mac OS X is needed to bring the Cocoa code into a usable state.