Free perl application module software for linux

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.

MyCMS perl module provides the MN::CMS Perl module used by the MyCMS.

MyCMS perl module contains Perl object classes to manage the data of MyCMS (such as articles, links, and images).

MN::CMS is a perl module that allows you to manage an Internet
publishing system.#

MyCMS is an extension module of MyNews.

MyCMS introduces the concept of article, author and moderator.

Alien Perl module package contains external libraries wrapped up for your viewing pleasure!

SYNOPSIS

perldoc Alien;

Alien is a package that exists just to hold together an idea, the idea of Alien:: packages, so there is no code here, just motivation for Alien.

Why

James and I ended up doing a build system for Fotango, lots of people have done a build system, it is a pretty boring task. The boring task is really all the mindlessly stupid things you need to do to build C libraries that Perl modules require, these C modules usually have unusual installation systems or require vastly different options. So CPAN modules install easy, 3rd party stuff is nasty.
So, suddenly an idea struck me, Alien packages! Imagine a CPAN module that has as its only task to make sure a certain library is installed! That means that you can write all the voodoo in your Build.PL file and then just make sure the module requires the correct Alien module! Then anything that install Perl modules will deal with it automatically!

How

So, what should an Alien module do? It should make sure that the target is installed and it should provide the caller with enough information to use it.
The idea is that you use it to make sure it is there, and you call class methods to find out what to use. These class methods will be individually specified by the stand alone Alien modules.

No Framework!

The reason this is so loosely worded is because we have no idea what common functionality will be needed, so we will let evolution work for us and see what individual Alien packages need and then eventually factor it out into this packages. I would like to avoid a topdown design approach.

Responsibilities of a Alien module.

On installation, make sure the required package is there, otherwise install it.
On usage, make sure the required package is there, else croak.

Bundle the source with the module, or download it.

Allow module authors to access information it gathers.

Document itself well.

Preferably use Module::Build.

Be sane.

OpenGeDB Perl module is a module to access the OpenGeoDB database and calculate all ZIP codes in a certain radius.

CGI::Application::Generator is a Perl module with dynamically build CGI::Application modules.

SYNOPSIS

use CGI::Application::Generator;

# Required methods
my $cat = CGI::Application::Generator->new();
$cat->package_name(My::Widget::Browser);
$cat->start_mode(list_widgets);
$cat->run_modes(qw/
list_widgets
add_widget
insert_widget
edit_widget
update_widget
delete_widget
/);


# Optional methods
$cat->base_module(My::CGI::Application);
$cat->use_modules(qw/My::DBICreds My::Utilities/);
$cat->new_dbh_method(My::DBICreds->new_dbh());
$cat->tmpl_path(Path/To/My/Templates/);


# Output-related methods
$cat->app_module_tmpl(my_standard_cgiapp.tmpl);
$cat->output_app_module();

CGI::Application::Generator provides a means by which a CGI::Application module can be created from code, as opposed to being written by hand. The goal of this module is two-fold:

1. To ease the creation of new CGI::Application modules.
2. To allow standardization of CGI::Application coding
styles to be more uniformly applied.

It is also the hope of this module that Computer Assisted Software Engineering (CASE) tools will eventually emerge which will allow the development process for web-based applications to be greatly improved. These CASE tools could more easily convert visual notation (such as UML state-transition diagrams) into method calls to this module, thereby creating actual code.

Jeta SSH Module provides a Horde SSH module.

Jeta is the Horde Application Frameworks wrapper module for the SSHTools Java SSH Applet.

Jeta is based on a java SSH client. It allows shell access to your web server, or to another machine if used with a port relay daemon (not provided).

ASNMTAP::Asnmtap::Applications is a Perl module that provides a nice object oriented interface for ASNMTAP Applications.

ASNMTAP::Asnmtap::Applications Subclass of ASNMTAP::Asnmtap

This version is still the old ASNMTAP Applications v3.000.001 addapted for using with the new ASNMTAP::Asnmtap, ASNMTAP::Asnmtap::Plugins and ASNMTAP::Asnmtap::Plugins::Nagios plugins.

We are working onto an new Object Oriented version for the ASNMTAP Applications

The metric implemented in the Image::Density Perl Module estimates the density of data where there is data, and has a reasonable correlation with goodness as judged by humans.

That is, if you let a human look at a set of images and judge quality, the density values for those images as calculated here tend to correlate well with the human judgement (densities that are too high or too low represent "bad images).

This project is intended for use on bitonal TIFF images, such as those from scanning paper documents.