Free flexible application software for linux

Online Library Application (OLA) project is a Web-based library system for small/medium organizations (books, videos, etc.).
The software allows users to browse the library collection over the Internet, and allows authorized persons to manage sign in and sign out procedures, resource adds and updates, and data backups.
It was originally written for a non-profit organization to manage their resource library.
Main features:
- internet based
- highly graphical
- compatible with Netscape and Windows browsers
- suitable for tracking many types of resources (books, magazines, videos, music, etc.)
- can store a large amount of data about each resource
- borrowers do not have to set up an account
- stores minimal information about borrowers--just the bare essentials
- simple database export function
- template based for easy configuration/customization
- optional gzip compressed output to save on bandwidth
- although designed for small organizations, catalog should scale well to millions of entries

CGI::Application is a framework for building reusable web-applications.

SYNOPSIS

# In "WebApp.pm"...
package WebApp;
use base CGI::Application;

# ( setup() can even be skipped for common cases. See docs below. )
sub setup {
my $self = shift;
$self->start_mode(mode1);
$self->mode_param(rm);
$self->run_modes(
mode1 => do_stuff,
mode2 => do_more_stuff,
mode3 => do_something_else
);
}
sub do_stuff { ... }
sub do_more_stuff { ... }
sub do_something_else { ... }
1;


### In "webapp.cgi"...
use WebApp;
my $webapp = WebApp->new();
$webapp->run();

CGI::Application is intended to make it easier to create sophisticated, high-performance, 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.

CGI::Application judiciously avoids employing technologies and techniques which would bind a developer to any one set of tools, operating system or web server.

TiVo::HME::Application is a Perl implementation of TiVos HME protocol.

SYNOPSIS

use TiVo::HME::Application;
our @ISA(TiVo::HME::Application);

sub init {
my($self, $context) = @_;

$self->get_root_view->visible(1);
my $mpg = $T_RESOURCE->image_file(examples/myloop.jpg);
$self->get_root_view->set_resource($mpg,
$T_CONST->HALIGN_CENTER | $T_CONST->VALIGN_CENTER);
}

sub handle_event {
my($self, $resource, $key_action, $key_code, $key_rawcode) = @_;
print "You pressed the $key_code key on the remote!n";
}

Perl on your TiVo in 11 Steps!!

Step 1: Go to http://tivohme.sourceforge.net
Step 2: Go to Step 1
Step 3: Go to Step 2 (seriously)
Step 4: Congratulations on making it here!
Step 5: Really, go to http://tivohme.sourceforge.net, download the
SDK, read the PDF files (dont worry about the protocol PDF,
thats what this is for).
Step 6: Learn about Views & Resources
Step 7: Learn about the Application cycle (init then event loop)
Step 8: Learn about Events
Step 9: Learn how the Perl stuff differs from the Java stuff
(mainly only in naming)
Step 10: View & understand the perl examples - especially how they
related to the Java examples (they do the same thing!).
Step 11: Use your imagination to create a kick-arse Perl-based HME app!!

Prima::Application is root of widget objects hierarchy.

Prima::Application class serves as a hierarchy root for all objects with child-owner relationship. All toolkit objects, existing with non-null owner property, belong by their top-level parental relationship to Prima::Application object. There can be only one instance of Prima::Application class at a time.

SYNOPSIS

use Prima;
use Prima::Application;
or
use Prima qw(Application);

Prima::MainWindow-> create();

run Prima;

USAGE

Prima::Application class, and its only instance are treated specially throughout the toolkit. The object instance is contained in

$::application

scalar, defined in Prima.pm module. The application instance must be created whenever widget and window, or event loop functionality is desired. Usually

use Prima::Application;

code is enough, but $::application can also be assigned explicitly. The use syntax has advantage as more resistant to eventual changes in the toolkit design. It can also be used in conjunction with custom parameters hash, alike the general create() syntax:

use Prima::Application name => Test application, icon => $icon;

In addition to this functionality Prima::Application is also a wrapper to a set of system functions, not directly related to object classes. This functionality is generally explained in "API".

Simple dictionary application project allows users to use any plain text dictionary that is UTF-8 with one translation per line and words separated by tabulators.

Applications allow users to use free bilingual dictionaries offline. All dictionaries have to be UTF-8 files with one translation per line and words separated by tabulators. Hundreds of free bilingual dictionaries can be created and downloaded from the Universal dictionary system. Universal dictionary currently interconnects 33 languages (Afrikaans, Basque, Bulgarian, Croatian, Czech, Danish, Dutch, English, Esperanto, Estonian, Finnish, French, German, Greek, Hungarian, Icelandic, Indonesian, Italian, Japanese, Japanese Romaji, Latin, Lithuanian, Norwegian Bokmal, Polish, Portuguese, Romanian, Russian, Simplified Chinese, Slovak, Slovenian, Spanish, Swedish, Turkish)

Yet Another V4L Application (or yava for short) is lightweight v4l framegrabber with support for TrueType fonts and ftp-upload.
Yet Another V4L Application project is written in ANSI C.
It uses Andreas Schifflers excellent SDL_bgrab library for frame grabbing, SDL for internal image manipulation, SDL_ttf for TrueType font rendering, libcurl for ftp uploads and libpng for snapshot writing.
Main features:
- Lightweight, using pretty standard libraries
- Tuner support
- FTP-upload (active and passive modes)
- TrueType font rendering
- Text color (RGB) selection
- Vertical text positioning (top, center, bottom)
- Horisontal text positioning (left, center, right)
- Font selection and number of pts
- Snapshots in png
- Live viewer or console mode

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.

SOPE Application Server is an extensive set of frameworks (16 frameworks, ~1500 classes) which form a complete Web application server environment.
Besides the Apple WebObjects compatible appserver extended with Zope concepts, it contains a large set of reusable classes: XML processing (SAX2, DOM, XML-RPC), MIME/IMAP4 processing, LDAP connectivity, RDBMS connectivity, and iCalendar parsing.
The individual frameworks of the package can be used standalone (for example in Cocoa applications) and do not require the application server itself.
For MacOSX developers, the package includes SOPE:X, which contains special Xcode and Cocoa support for SOPE.
Enhancements:
- This release fixes a set of minor bugs.
- It improves the vCard parser, the IMAP4 client library, the MySQL adaptor, and BSD packaging.