Free groupware application software for linux

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.

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".

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.

Horde Groupware Webmail Edition is a free, enterprise ready, browser based communication suite. Users can read, send and organize email messages and manage and share calendars, contacts, tasks and notes with the standards compliant components from the Horde Project.
Horde Groupware Webmail Edition bundles the separately available applications IMP, Ingo, Kronolith, Turba, Nag and Mnemo.
The project can be extended with any of the released Horde applications or the Horde modules that are still in development, like a file manager, a bookmark manager, a forum or a wiki.
Main features:
- IMAP and POP3 webmail client
- Message filtering
- Message searching
- HTML message composition with WYSIWIG editor
- Spell checking
- Built in attachment viewers
- Encrypting and signing of messages (S/MIME and PGP)
- Quota support
- Keyboard navigation
- Full character set support for folders names and email messages
- Conversation view of all messages in a thread
- Folder tree in left menu pane
- Message previews in mailbox view
- Downloading of message attachments in a ZIP file
- Fetching of messages from external email accounts
- Flexible, individual alias addresses
- IMAP folder subscriptions
- Shared IMAP folders
- Graphical emoticons
- Support for mailing list headers
- Forwarding of multiple messages at once
- Attachments sent as links
Enhancements:
- A local arbitrary file deletion vulnerability and XSS vulnerabilities in the Webmail search screen and thread view have been fixed.
- Displaying of PGP messages has been improved.
- mailto: links in HTML email messages are turned into IMP compose links.
- The Oracle session handler has been rewritten.
- Validation of some email distribution lists has been fixed.
- Compatibility with Internet Explorer 7 has been improved.
- Blacklists and whitelists when using the IMAP driver have been fixed.
- Many small bugfixes and improvements have been made.

eGroupWare is a multi-user, web-based groupware suite developed on a custom set of PHP-based APIs.
Main features:
- email
- addressbook
- calendar
- infolog (notes, to-dos, phone calls)
- content management
- forum
- bookmarks
- wiki
Version restrictions:
- EGW does not need to be compiled. EGW is composed only of PHP, HTML and image files
- EGW needs a Database server. MySQL or PostgreSQL or MSSQL preferred. Can be local or remote.
- EGW needs a php4 enabled web server. Apache1.3.x with PHP4.3.x preferred.
- EGW may need an e-mail server. Can be local or remote and IMAP or POP.
- Please read the requirements and install-how-to in the download area.
Enhancements:
- addressbook completly rewritten (Group-addressbooks, Organisation-views, improved LDAP support)
- new fully integrated tracker application used by the project itself since some time
- new imap backend and many improvments for FMail
- Gallery2 port for eGroupWare
- many improvments in nearly all applicatons

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!!

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)