Free getting started software for linux

Battle Just Started project is a 3D arcade tank battle.

Rendering is done using OpenGL, and direct rendering is recommended. The game is focused on multiplayer over LAN.

An AI is also present, but is not very strong.

World simulation is done via ODE, and sound is done using OpenAL and SDL_mixer.

The game has currently 3 maps, 5 tanks, and 4 weapons.

RocketSled is a object-oriented, full featured, Web-based application development framework for PHP 5.
Its packages include Active Record and Object Relational Mapping, an advanced XML-based templating language, and a multi-user management suite.
Main features:
- Completely Object Orientated
- Flexible program structure
- Package-centric applications for easy re-deployment
- Integrated XML based templating language (RSML)
- XML based form validation engine (FormML)
- Does not require database for basic install
- Extra packages (currently 2 available) for ActiveRecord and user management
- ActiveRecord package with automated data tainting and universal pagination
- MIT License
Enhancements:
- All packages are now included in the same CVS repository for more basic version numbering, and the system has increased in stability and is more mature.
- It has also had numerous bugfixes and feature enhancements.
- Although the documentation is still very lacking, there is a Getting Started tutorial that will hopefully allow people to start looking at the framework more seriously.

App::quickstart is App::Context Developers Quick-Start Guide.

This is the Developers Quickstart Guide to the App::Context Framework. Its focus is to give a minimum amount of theoretical or explanatory background and get right into learning by example.

That having been said, it is also important to let you know what documentation exists and what state it is in.

I got started building the App::Context framework a while ago. The documentation is very limited. This is an effort to bring it all together. This list shows how all of the documentation fits together and in what state it is.

The following documentation is in good shape. To get started, read them more or less in the order shown.

App::quickstart - This quick start guide.

App::installguide::hosted - Installing the App::Context Framework on a non-root web hosting account

The following documentation also is in good shape. It is background reference material.

App::datetime - Guidance on date, time, and datetime types in perl.

App::exceptions - Guidance on exceptions in perl.

The following documentation is in a state that needs review, modification, or completion.

App::perlstyle - A perl style guide that builds minimally on perlstyle.

App::faq - Questions about P5EE.

App::installguide - Installing the App::Context Framework on Unix.

App::installguide::win32 - Installing the App::Context Framework on Windows.

App::devguide - Developers Guide.

App::devguide - Developers Guide.

App::adminguide - Administrators Guide.

App::adminguide::cvs - Admin Guide, setting up CVS source control.

CLASS/MODULE DOCUMENTATION (indented entries are subclasses)

Most of this documentation needs review, modification, and completion.

App - The module that bootstraps the use of the App::Context Framework.

App::Context - Abstract class representing the the runtime context of the program.

+-- App::Context::Cmd - A program running in a command-line context.

+-- App::Context::HTTP - A program running in a CGI/mod_perl context.

+-- App::Context::Server - A program running in a multi-process server context.

=====+-- App::Context::ClusterController - Running in a multi-node cluster context.

=====+-- App::Context::ClusterNode - Running on a single node of a cluster.

+-- App::Context::NetServer - Another flavor of server context (not yet implemented).

App::Exceptions - Defines the exceptions used in the framework.

App::UserAgent

App::Request

+-- App::Request::CGI

App::Response

App::Session

+-- App::Session::HTMLHidden

+-- App::Session::Cookie

App::Reference

+-- App::Conf

=====+-- App::Conf::File

App::Service

+-- App::Serializer

=====+-- App::Serializer::Properties

=====+-- App::Serializer::Ini

=====+-- App::Serializer::Perl

=====+-- App::Serializer::Xml

=====+-- App::Serializer::Yaml

=====+-- App::Serializer::OneLine

=====+-- App::Serializer::TextArray

=====+-- App::Serializer::Storable

+-- App::SessionObject

+-- App::Authentication

+-- App::Authorization

+-- App::ValueDomain

+-- App::SharedDatastore

+-- App::MessageDispatcher

+-- App::CallDispatcher

=====+-- App::CallDispatcher::HTTPSimple

+-- App::ResourceLocker

=====+-- App::ResourceLocker::IPCSemaphore

=====+-- App::ResourceLocker::IPCLocker

Apache::Framework::App

INSTALLATION

You can go through one of the installation guides. Installing the App::Context Framework generally involves several distributions and should just work when installed from CPAN.

perl -MCPAN -e shell
cpan> install App::Options
cpan> install App::Context
cpan> install App::Repository
cpan> install App::Widget
cpan> exit

If its not this easy, I need to work on making it easier.

Skeleton Pro is a Swing demo application that can help you get started with Swing. Skeleton Pro project incorporates user interface and architectural patterns that scale well up to medium sized applications.
Skeleton Pro comes with, utilizes and demos the JGoodies Swing Suite.
Main features:
- Better application startup process:
- brings up a splash with progress indicator; configures and restores the UI; configures and uses logging; configures preferences; finally launches and prepares Swing.
- Better integration with the Mac OS X:
- hooks into the application menu; avoids duplicate menu items; better toolbar buttons; better dock icon when minimized.
- Stores and restores state via user preferences:
- Window position and size, panel layout, look&feel and theme
- More default dialogs: Welcome, License, Preferences, Tip of the day, About
- Uses the global (static) help system
- Provides a dynamic help system
- Can switch look&feel at runtime
- Logs runtime errors to a logfile
- Uses anti-aliased components
- Provides consistent dialog layout and design
Users Guide:
The application is about editing propeller shaft data. It has been extracted from a real-world application that helps ship inspectors check and verify whether a propeller shaft complies with a set of building rules for ship and machinery.
You can either create a new project, or load an existing. In both cases, this demo will create a sample project. You can browse the project components in the navigator, in the left. If you select a node in the navigator, an appropriate viewer shows up on the right side.

yeaGTD is an acronym for "yaml encoded approach to getting things done". The project is a python script which extracts information from simple text files, one for each project, and then produces nicely formatted summary reports.
Flexible rules can be used to specify repeated projects. Context, project and date views are supported and output can be filtered in a variety of ways. Output can optionally be printed or sent to standard output in several formats.
Commands are provided for marking tasks complete, opening files for editing and backing up project files.
YAML, a recursive acronym for "YAML Aint Markup Language", is a human readable and writable data serialization format. YAMLs contribution to yeaGTD is to make the format of the project files extremely simple both to create and to read.
Getting Things Done, commonly abbreviated as GTD, is an action management method, and the title of a extremely popular book by David Allen. GTD rests on the common sense notion that with a complete and current inventory of all commitments, organized and reviewed in a systematic way, the mind is freed from the job of remembering everything that needs to be done, and can focus on actually performing those tasks.
Suppose, for example, that the halogen bulb in the study lamp needs to be replaced. Getting this done requires first removing the old bulb, taking it with you to the hardware store to buy a similar replacement bulb and finally installing the new bulb. Though simple, this example illustrates several aspects of GTD.
1. Projects usually involve a series of steps, some of which must be carried out sequentially, e.g., the old bulb must be removed before it can be taken to the hardware store and the replacement must be purchased before it can be installed.
2. The steps of a project are carried out in a context which may vary from step to step, e.g., removing the old bulb and installing the new one both take place in the context "Home" but buying the required bulb takes place in the context "Errands".
3. While focusing on projects is great for planning, for actually doing things it would be more convenient to focus on context so that, for example, you could see all actions from all projects with context "Errands" before you drive away to run errands. To focus on what needs to be done, it would also be useful to be able to hide actions that are not yet available so that, for example, "Install new bulb" would not be displayed until "Buy required bulb" had been completed.
Enhancements:
- Unicode support has been added. encoding is set in ~/.yeagtdrc, and defaults to utf-8.
- Example project and configuration files are now included in the distribution.
- Installation instructions now include steps for getting started.
- A bug has been fixed in the file selection routine in which the last file was not listed.

E-Gantt is an open source gantt chart library in Java and Swing which is intended for usage in logistics and scheduling applications.
E-Gantt has been in-active for over a year, but has recently seen a lot of work done which includes a simplified interface and documentation in the form or tutorials to make the project easier to use.
Despite this E-Gantt has been succesfully implemented in many large open source projects and commercial projects with-in the following industries.
- Scheduling Research
- Medical Research
- US Military Defense Projects
- Network Administration tools
How E-Gantt works
Rather than develop a brand-new table component for Swing or extend the table component making it propreitry and difficult to work with. E-Gantt heavily utlilizes the existing JTable framework with modifying it, which serves to allow companies using E-Gantt the ability to use there own JTable extensions with E-Gantt with no futher work.
E-Gantt does this by mapping the DefaultCellRender, DefaultCellEditor of the table for its own column class. The Gantt chart will be rendered with-in each column of the table.
The value returned by the getValueAt of the table model is required to be of a DrawingState which is the value for each column.
Drawing State
The DrawingState is a value which is used for the rendering the gantt drawing which is returned by the methd call tableModel.getValueAt(row, column).
The DrawingState contains a lot of information about the actual drawing including:
- Location of the Top and Bottom of the Entry
- A reference key to indicate how the Entry should be drawn
- A reference key to indicate how the Entry should be coloured
For getting started this has been made easier by a helper class GanttEntryHelper. GanttEntryHelper can be called with as little information as a start time and a finish time this can be done as static data or called dynamically with-in the actual table model.
Enhancements:
- The drawing tool was fixed to determine the width of an entry.
- The GlassPane / Acetate layer for tools was introduced.
- A new demo for modifiying drawing context was included.
- A new example of text on diagrams (a layering example) was added.
- A new example of multi-entry was added to the examples.

Persistent::Base is an Abstract Persistent Base Class.

SYNOPSIS

### we are a subclass of ... ###
use Persistent::Base;
@ISA = qw(Persistent::Base);

ABSTRACT

This is an abstract class used by the Persistent framework of classes to implement persistence with various types of data stores. This class provides the methods and interface for implementing Persistent classes. Refer to the Persistent documentation for a very thorough introduction to using the Persistent framework of classes.

This class is part of the Persistent base package which is available from:

http://www.bigsnow.org/persistent
ftp://ftp.bigsnow.org/pub/persistent

Before we get started describing the methods in detail, it should be noted that all error handling in this class is done with exceptions. So you should wrap an eval block around all of your code. Please see the Persistent documentation for more information on exception handling in Perl.

ABSTRACT METHODS THAT NEED TO BE OVERRIDDEN IN THE SUBCLASS

datastore -- Sets/Returns the Data Store Parameters

eval {
### set the data store ###
$person->datastore(@args);

### get the data store ###
$href = $person->datastore();
};
croak "Exception caught: $@" if $@;

Returns (and optionally sets) the data store of the object. This method throws Perl execeptions so use it with an eval block.

Setting the data store can involve anything from initializing a connection to opening a file. Getting a data store usually means returning information pertaining to the data store in a useful form, such as a connection to a database or a location of a file.