Free job applications software for linux

WAG Applications provides a collection of WAG-hosted Web applications.
WAG Applications is a collection of Web applications that are capable of being hosted by the Web Application Gateway.
WAG provides core functionality such as user definition, authentication, and administration, for all hosted Web applications.
Enhancements:
- Added application specific handlers to the wagErrorHandler function.
- Added is_email() function to functions.php which checks if a a given e-mail address is valid. It checks for all top level domains including the new ones (.biz, .info, .museum etc.) and the special ones (.arpa, .int etc.) as well as with e-mail addresses based on IPs (e.g. webmaster@123.45.123.45). (Function derived from PHP user contributed notes.)
- Enhanced the error reporting for both WAG and application database errors to include the server name and user name/id. This will help admins target problems if they are responsible for multiple WAG installations.
- Added "Date Added" and "Date Last Login" information to Administration > Users screen.
- Made style sheet changes related to form field fonts.
- Bug Fixes
- Validation of user e-mail addresses was not performed correctly and causing any valid e-mail address to be flagged as invalid.
- When admin changes a users password, the e-mail password, if configured, is also changed. This allows the admin to "lockout" a user from both WAG and e-mail if needed.

REST::Application is a framework for building RESTful web-applications.

SYNOPSIS

# MyRESTApp L instance / mod_perl handler
package MyRESTApp;
use Apache;
use Apache::Constants qw(:common);

sub handler {
__PACKAGE__->new(request => $r)->run();
return OK;
}

sub getMatchText { return Apache->uri }

sub setup {
my $self = shift;
$self->resourceHooks(
qr{/rest/parts/(d+)} => get_part,
# ... other handlers here ...
);
}

sub get_part {
my ($self, $part_num) = @_;
# Business logic to retrieve part num
}

# Apache conf
< Location /rest >
perl-script .cgi
PerlHandler MyRESTApp
< /Location >

This module acts as a base class for applications which implement a RESTful interface. When an HTTP request is received some dispatching logic in REST::Application is invoked, calling different handlers based on what the kind of HTTP request it was (i.e. GET, PUT, etc) and what resource it was trying to access. This module wont ensure that your API is RESTful but hopefully it will aid in developing a REST API.

OpenPlugin::Application is a subclass of CGI::Application, meant to help you create reusable web applications.

SYNOPSIS

# Example from OpenThoughts Demo.pm

package Demo;
use base "OpenPlugin::Application";
sub setup {
my $self = shift;
$self->run_modes(
mode1 => init_demo,
mode2 => get_os_list,
mode3 => get_os_info,
);
$self->start_mode( mode1 );
$self->mode_param(run_mode);
}
sub init_demo { ... }
sub get_os_list { ... }
sub get_os_info { ... }
1;

# Example from OpenThoughts demo.pl

#!/usr/bin/perl -wT
use strict;
my $r = shift;
my $demo = Demo->new( PARAMS => {
config => { src => "/path/to/OpenPlugin.conf" },
request => { apache => $r },
});

$demo->run();

OpenPlugin::Application is built on Jesse Erlbaums popular CGI::Application module. OpenPlugin::Application is simply a subclass of CGI::Application. Jesse says the following about CGI::Application:

"CGI::Application is intended to make it easier to create sophisticated, reusable web-based applications. This module implements a methodology which, if followed, will make your web software easier to design, easier to document, easier to write, and easier to evolve."

How does it do this? Jesse goes on to say:

"The guiding philosophy behind CGI::Application is that a web-based application can be organized into a specific set of "Run-Modes." Each Run-Mode is roughly analogous to a single screen (a form, some output, etc.). All the Run-Modes are managed by a single "Application Module" which is a Perl module. In your web servers document space there is an "Instance Script" which is called by the web server"

The biggest difference between CGI::Application and OpenPlugin::Application is that query object they both use; one is designed to use CGI.pm, the other OpenPlugin. Generally speaking, everything in the still applies. Any differences will be noted in this document.
It is not necessary to use OpenPlugin::Application in order to build web applications using OpenPlugin. This plugin is meant to be for your convenience -- to help you structure your web applications in a manner which makes sense, and is reusable.

The Horde Application Framework is written in PHP, and provides the common tools a Web application requires: classes for dealing with preferences, compression, browser detection, connection tracking, MIME, and more.
The Horde Framework does not provide any significant end user functionality and it provides a base for other applications and tools for developers. You will probably want to install some of the available Horde applications, such as IMP (a webmail client), or Kronolith (a calendar).
Enhancements:
- This is a security release that fixes a cross site scripting vulnerability and improves protection against phishing attempts.

Arkhon Web Application Framework provides an extremely lightweight, modular and extensible framework for developing scaleable community-based groupware applications through the PHP language.
Arkhon takes care of the following:
- Quick and intuitive skinning of your web application through the use of themes.
- Authentication and role based Authorisation
- Support for multiple database backend.
- Modular design.
- Extremely lightweight.
so that you can concentrate on the functionality of you web application.
Enhancements:
- Lots of refactoring of code (especially the API) in this release.
- It is ready for work to begin on the next phase (database backends).

Keystone is a cross-platform, object oriented application framework which allows applications to be written to build on the target platforms of GNU/Linux and Win32 without modification of their source.
Keystone Application Framework implements several modern Web standards, including SVG graphics and the XUL user interface description language.
Enhancements:
- A significant development in this release is the optional use of the GDI+ (Win32) and CairoGraphics (Linux) rendering backends to render SVG content.
- In addition, support for SVG paths has been much improved with the ability to render bezier and elliptical segments.

Realtime Application Interface project allows applications with strict timing constraints to be run on Linux.
A real time system is able to guarantee the timing requirements of the processes under its control.
RTAI provides an API and the necessary kernel modifications to accommodate such requirements.
Enhancements:
- Improvements were made to netrpc.
- Context switching between hard and soft real-time, handling of TSC errors, and POSIX compatibility have been improved.
- There are numerous minor bugfixes.