Free web application development software for linux

Enveria IDE for Rapid Application Development is an intuitive platform for programming robust GUI (graphical user interface) software.

We have launched the Enveria RAD IDE as an open source application (https://sourceforge.net/projects/enveria). Previously, the Enveria IDE was utilized as an internal development tool at Kaizen Denki Inc. -- a Toronto-based software and web development house.

Enveria is free to use for non-commercial purposes under the GPL. Users who wish to use Envria in a commercial capacity should visit the Kaizen Denki home page at http://www.kaizendenki.com.

Major Features:

* An interface that maintains an look and feel that is intuitive for those familiar with IDE software, while user friendly enough for those who are not.

* Backed up by the power of the ubiquitous C programming language. We have chosen C because it is fast, stable, powerful, portable and has a long history of use in computing. An additional bonus for us was that the API for GTK+ (the widget set we use) uses C natively.

* Our use of GTK+ allows Enveria to tap into a well-supported widget set that is available for all major desktop operating systems. On its own, GTK+ is easy to use but with Enveria it is even easier. While Enveria RAD IDE can be an interface builder for GTK+/C programs (like Glade), its power is its capabilities as a complete development tool.

* Enveria can produce code without compiling for those who wish to enhance their applications manually prior to building. Enveria programs are optimized for Make/GCC, which is a widely used combination for C development on many platforms.

Programming languages, libraries, databases, and frameworks used to develop Enveria include:

* C
* MySQL
* SQLite
* GTK+ 2

Currently Linux is the main supported platform for Enveria RAD IDE.

At the same time, we are in the process of evaluating other target operating systems including: Mac OS X, Minix 3, BSD and others.

Echo is a framework for developing object-oriented, event-driven Web applications.
Echo removes the developer from having to think in terms of "page-based" applications and enables him/her to develop applications using the conventional object-oriented and event-driven paradigm for user interface development.
Knowledge of HTML, HTTP, and JavaScript is not required. Echo is open-source software distributed under the terms of the Mozilla Public License or the GNU LGPL License.
Enhancements:
- Version 1.1.4 adds support for specifying the order of tab-based navigation of components. The release also fixes bugs reported in previous versions, including the issues discovered with setting component focus.

php.MVC implements the Model-View-Controller design pattern, and encourages application design based on the Model 2 paradigm. This design model allows the Web page or other contents (View) to be mostly separated from the internal application code (Controller/Model), making it easier for designers and programmers to focus on their respective areas of expertise.
The framework provides a single entry point Controller. The Controller is responsible for allocating HTTP requests to the appropriate Action handler (Model) based on configuration mappings.
The Model contains the business logic for the application. The Controller then forwards the request to the appropriate View component, which is usually implemented using a combination of HTML with PHP tags in the form of templates. The resulting contents are returned to the client browser, or via another protocol such as SMTP.
php.MVC is a PHP port of Jakarta Struts. It currently supports many features of Struts, including declarative application configuration via the XML digester. For example, mappings from the various Action business logic components to appropriate results pages can be specified declaratively in the XML configuration file.
Main features:
- Free OpenSource software: This gives users full control of the software, and the able to modify the source code to suit specific needs.
- Security: php.MVC applications have only one entry point (per application). This makes it easy to protect sensitive application code and data.
- Flexible Installation: Individual php.MVC applications can be installed outside of the main php.MVC library directory tree.
- Multi-applications: There is no limit to the number of applications per php.MVC installation.
- Object Oriented design (OOD). The php.MVC framework is based on OOD principles, making it more extendable and maintainable.
- Database integration: The php.MVC framework ships with the Pear::DB Database Abstraction Layer, and a driver for the MySQL relational database manager (RDBM) is provided.
- Action Chaining: php.MVC allows for passing control to other Actions. This makes it easy to process a sequence of Actions (business logic classes) and static resources (pages).
- XML configuration: php.MVC uses declarative application configurations using Extensible Markup Language (XML) files. Each application has its own XML configuration file.
- MVC Model 2 design: php.MVC implements the Model-View-Controller (MVC) Model 2 design pattern. The Model 2 paradigm allows the separation of the application presentation from the business logic, making it easier for designers and programmers to focus on their respective areas of expertise.
- Form button mapping: php.MVC implements the LookupDispatchAction class to enable HTML form buttons to be mapped to particular business logic methods. For example, a form submit button called "Add to Cart" could be mapped to an Action class method called MyCartAction->addToCart(...).
- Message Resources: php.MVC provides a PropertyMessageResources class that handles messages in text string properties files with parametric replacement. This can provide Locale-sensitive messages for internationalized applications.
- The php.MVC framework is based on Jakarta Struts application framework design. Struts has proven to be reliable, extendable and well supported.
Enhancements:
- This development release adds bugfixes and enhancements to the framework, a compressed performance version for use in more demanding hosting environments, and an example application to demonstrate the use of both versions.

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

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.

Python Integrated Development Application (Pida) is an IDE based around the idea of reusing existing tools, rather than attempting to write a set of development tools of its own.

Python Integrated Development Application uses Vim as the editor, either with its traditional user interface or with a user interface that resembles more common text editors.

PIDA is different from other IDEs. Rather than attempting to write a set of development tools of its own, PIDA uses tools that the developer has available. In this regards PIDA is a framework for assembling a bespoke IDE. PIDA allows you to choose the editor you wish to use (yes, Vim out of the box works).

Although still a young application, PIDA can already boast a huge number of features because of the power of some of the tools it integrates. For example features such as code completion and syntax highlighting are well implemented in PIDAs integrated editors far better than any editor built for a commercial IDE.

Additionally PIDA insists on stealing excellent ideas from applications it cannot embed. For example the Rapid Application Development in the style of Microsofts development products is achieved by the combination of Gazpacho (a user interface designer) and Tepache (a code sketcher), via the text editor.