Free application bootstrap software for linux

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.

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.

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

Curses::Application provides the Curses Application Framework.

Curses::Application attempts to relieve the programmer of having to deal directly with Curses at all. Based upon Curses::Widgets and Curses::Forms, all one should have to do is define the application forms and contents in the DATA block of a script. Curses::Application will take care of the rest.

This module follows many of the conventions established by the Curses::Widgets and Curses::Forms modules, being built upon that framework. One area of special note, however, is the declaration of forms used within the application.

Curses::Application differentiates between forms and form definitions. A form is an instance of any particular form definition. Keeping that line of separation simplifies the development of MDI (Multiple Document Interface) applications.
Form definitions can be provided in two ways: as a list of definitions in the main::DATA block, or individually by using the addFormDef method. The former would normally be the simplest way to do so.

At the end of your script, declare a DATA block using Perls __DATA__ token. In that DATA block place a hash declaration (%forms) which contains a key/value pair for each form definition. The key being the name of the definition, and the value being a hash reference to the form declarations (see the Curses::Forms pod for directives available to that module). The only extra key that should be in each forms hash reference should be a TYPE directive, which would point to a module name relative to the base Curses::Forms class. If you omit this key, then it will be assumed that the form is a Curses::Forms object, or some custom derivative as specified in ALTPATH.

SME Web Application Framework provides a Web application framework for small and medium-sized organizations.

SMEWebApp is a framework for constructing Web applications for SMEs (small and medium-sized enterprises, companies, institutions, and organizations). It is built on phpWebApp, and it is higher-level and more specific than phpWebApp.

It has some components that can be reused in any application (perhaps with small modifications), like hierarchical menus, user authentication, and user administration.

The aim of the project is to make Web application construction for SMEs easier than using VB.

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

Application::Pipeline is a module designed to map methods ( referred to in this role as handlers ) to different phases of an applications life cycle. By assigning methods to different phases of this pipeline, the author can concentrate on the logic for each phase and let the framework manage the application flow. Adopting the same idea as CGI::Application, writing an application with Application::Pipeline is a matter of creating a module that is a subclass of Application::Pipeline.

To build a pipeline application, it is necessary to register methods to run during each phase. This can be done one at a time, with the addHandler method. But Application::Pipeline also looks in the subclass package for the package variable %plan. This hashs keys are the names of the phases of the pipeline. Each key points to an array reference which is a list of the methods to run for that phase. The methods are either the names of the methods to run, or references to the actual methods.

This is not the be-all end-all definition of the pipeline. It is still possible to use addHandler to modify the pipeline, and as explained later, it is possible to take into account %plans defined in superclasses.

objc-bootstrap software is a bootstrap for objc package.

Objective-C Compiler Commands

Whats the file suffix for Objective-C source ?

Its .m for implementation files, and .h for header files. Objective-C compilers usually also accept .c as a suffix, but compile those files in plain C mode.

How do I compile .m files with the Stepstone compiler ?

objcc -c class.m
objcc -o class class.o

See http://www.stepstn.com for more information.

How do I compile .m files with the Apple compiler ?

cc -c class.m
cc -o class class.o

See http://www.apple.com for more information.

How do I compile .m files with the GNU C compiler ?

gcc -c class.m
gcc -o class class.o -lobjc -lpthread

See http://www.gnu.org for more information.

How do I compile .m files with the POC ?

objc -c class.m
objc -o class class.o

See http://metalab.unc.edu/pub/Linux/devel/lang/objc/ for more information.