Free create standalone applications software for linux

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.

GRIA (Grid Resources for Industrial Applications) is Grid middleware that enables use of the Grid in a secure, interoperable and flexible manner.
Security
GRIA uses off-the-shelf Web Services technology and Public Key Infrastructure (PKI) security.
Trust
GRIA supports well established B2B processes & trust models.
Ease of use
GRIA is designed to support leading-edge and legacy application codes, and client-side applications can be easily written using the GRIA API.
Quality of Service
GRIA resource models allow service levels to be matched to clients needs.
Support
GRIA is supported through an open source community and on a commercial basis.
Enhancements:
- This release provides significant new features and usability enhancements to both the management packages and the client.
- The core infrastructure stack has been further aligned with key Web Service security and policy specifications.
- New services include a Membership Service, Registry Service, and an improved SLA service.

1060 NetKernel is a resource oriented microkernel and application server that provides a coherent execution abstraction that radically reduces software complexity. Its self-consistent design is based on the convergence and unification of powerful fundamental concepts found in the World Wide Web and Unix.
Resource Oriented Microkernel
The heart of NetKernel is a high-performance, carefully designed, and tightly crafted microkernel. Services and resources within NetKernel are located by URI addresses, just as resources are located on the World Wide Web. NetKernel implements and extends REST 1 into a general-purpose processing abstraction and allows it to be applied to the finest granularity of software systems to achieve phenominal performance; just as the REST Web-architecture achieves global scaling and high performance.
Coherent Abstraction
NetKernel unifies code execution and resource identification into a single addressing and processing abstraction. With this, software development becomes a process of construction (coding services), composition (linking and issuing service and resource requests), and constraint (restricting data values and honoring boundaries).
The simplicity of URI identified resources means that the results of service calls can be cached just as other resources, resulting in self-optimizing software where computation cost is a guaranteed minima.
Reduce Software Complexity
The unification of resources and services with URI addressing radically reduces sofware complexity. Because resources are addressed by URI and each request is a Web-like REST request dispatched to the microkernel, binding between clients and services occurs dynamically for each request. This late binding and the indirection of logical URI addressing results in a loosely coupled system which may be easily adapted. In fact, NetKernel supports dynamic upgrading of software and can support multiple versions of the same components simultaneously.
Complexity brought about by system growth is also managed through the URI address space which may be remodelled and extended indefinitely. A complex aggregation of services may always be abstracted into one or more higher-level services surfaced through URI interfaces.
Main features:
Manage Complexity
- NetKernels unification of resource and service addressing through the active URI scheme combined with late binding and loose typing means that complex systems can be partitioned not just into smaller coorperating systems, you can now create micro-services that hide complexity.
- With NetKernel, design and build larger and more ambitious systems while maintaining control of complexity.
Process XML with ease!
- Processing XML is often just too difficult. But the potential of XML is communication with almost no limit. How to harness and leverage the potential of XML? NetKernel provides hundreds of XML technologies as simple services (no APIs). Simply compose XML services into powerful message processes...
Integrate diverse technologies, apply business logic
- NetKernels uniform URI addressing of resources and service allow you to encapsulate and hide the complexities of any technology, whether it is a Java API, legacy code, or remote corporate systems. Once encapsulated, develop new coordination logic in one of NetKernels scripting languages.
Transport technology independence
- Write a service or application and deploy it to service requests from multiple transports concurrently. NetKernel makes it easy to utilize SOAP 1.1, SOAP 1.2, HTTP, JMS, Email, and Cron.
Extreme performance from intra-application caching
- NetKernels fine-grained dependency cache transparently and opportunistically caches the results of all micro-service requests. NetKernel processes are self-optimizing with guaranteed minimal processing required for a given transaction.
Team Player
- NetKernel has several deployment options that allow it to play well with other technologies and systems. Deploy NetKernel as an advanced standalone application server, as an embedded "co-processor" within existing J2EE applications, as a JMS message processor, as a SOAP client or server, or as an embedded component within any application.
Enhancements:
- New features include support for Berkeley DBXML and PiNKY, a community developed module providing Yahoo! Pipes features.
- Updates include Groovy language support at release 1.0, Ruby (JRuby) support at 0.9.9, and XML library updates.
- There are also documentation updates and UI refinements.

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.

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.

Create a short URLs is a Firefox extension that allows you to create a short URL from any website.

Are you annoyed with really long URLs like: http://www.succor.co.uk/index.cfm/2006/4/7/wapurlcouk-beta-launch

Then this tag is for you. Just right click on the page and click wapURL and you will be presented with a short URL. This is great if you need to send text messages or emails.

When you use the short URL the key passed is looked up against our database and the user in then redirected to your requested URL.

Recursively create M3U playlists is a service menu which can create a file called playlist.m3u in each directories and sub directories.
You can edit recursively_create_M3U_playlist.py to change the name of playlist.m3u
To install, simply put recursively_create_M3U_playlist.py and recursively_create_M3U_playlist.desktop in ~/.kde/share/apps/konqueror/servicemenus
You need the package fapg installed.
Dont hesitate giving feedbacks or improvements.
Enhancements:
NEW FEATURES :
- 001 ==> Ask the name of the m3u playlist file
- 002 ==> Tell when its finished
BUGS FIXES :
- 001 ==> Much faster