Free to run this application you need to install macromedia flash player first software for linux

CGI::Application::Plugin::ValidateRM is a Perl module to help validate CGI::Application run modes using Data::FormValidator.

SYNOPSIS

use CGI::Application::Plugin::ValidateRM;

my $results = $self->check_rm(form_display,_form_profile) || return $self->check_rm_error_page;


# Optionally, you can pass additional options to HTML::FillInForm->fill()

my $results = $self->check_rm(form_display,_form_profile, { fill_password => 0 })
|| return $self->check_rm_error_page;

CGI::Application::Plugin::ValidateRM helps to validate web forms when using the CGI::Application framework and the Data::FormValidator module.
check_rm()

Validates a form displayed in a run mode with a Data::FormValidator profile, returning the results and possibly an a version of the form page with errors marked on the page.

In scalar context, it returns simply the Data::FormValidator::Results object which conveniently evaluates to false in a boolean context if there were any missing or invalide fields. This is the recommended calling convention.

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

Simple Flash Menu allows fast constructing nested menus for html pages (like on left side of this page), simply by editing xml file. No, dont afraid, xml knowledge isnt required, look on example and make similar.
This done with macromedia flash, you must place on server flash script which will analyze xml file and draw menus depending on its contest (about 10KB) and xml file or multiple xml files describing your menus. Nothing more must be done.
Now available two versions: one - very small without any decorations, and a bit larger with simple menu decorations. You can choose depending on your needs.
Requirements: any browser with Macromedia Flash Player 5 or Macromdia Flash Player 6 (MX) plugin. Wouldnt work with Flash Player 4 and earliers.
Tested in Internet Explorer 6.0, 6.0 SP1; Mozilla 0.9.8 - 1.2b (aka Netscape 6-7); Netscape 4.78; Opera 6.0 - 6.0.4, 7.0b1 in Linux and Windows enviroments.
Options:
- menu_file xml file load menu from
- html_width horizontal space on html page conducted for menu
- html_height vertical space on html page conducted for menu
- window open all links in specified window
- jscript instead of opening window call specified javascript function with parameters: href,jattr,state. Only one window or jscript can be selected
- jattr optional javascript function argument
- state specifies current menu state (i.e. which submenus open and which closed)
- font_size labels font size for all menu items (default: 36)
- left_margin menu left margin (default: 5)
- up_margin menu upper margin (default: 5)
- submenu_indention indention of all submenu items in pixels (default: 20)
- menuitems_overlap specifies distance between menu items, positive numbers defines overlapping menu items (default: 0.2)
- decor enable decorations (only 1.1.x)
- decor_width decoration width
- decor_spacing white space between decoration and menu label
- send_state Boolean, specifies if state parameter (information which submenus open, which closed) by default must be sent to all pages, opened from menu, or not (default is to send).
- fg Specifies foreground color for inactive item (fg="#0000FF")
- afg Specifies foreground color for active item (afg="#FF0000")
- bg Specifies background color for inactive item (bg="255,128,0,100" - here 255 - red component, 128 - green component, 0 - blue component, 100 - alpha; "255,255,255,100" is visble white, "0,0,0,0" - invisible black)
- abg Specifies background color for active item (some as bg)
- dfg Specifies decoration color inactive item (some as bg)
- adfg Specifies decoration color for active item (some as bg)

Module::Install::Deprecated are warnings and help for deprecated commands.

One of the nicest features of Module::Install is that as it improves, there is no need to take into account user compatibility, because users do not need to install Module::Install itself.

As a result, the Module::Install API changes at a faster rate than usual, and this results in deprecated commands.

Module::Install::Deprecated provides implementations of the deprecated commands, so that when an author is upgrading their Module::Install and they are using a deprecated command they will be told that the command has been deprecated, and what the author should use instead.

This extension should NEVER end up bundled into the distribution tarball.

Bio::Tools::Run::PiseWorkflow is a class to create a Pise workflow using Pise application objects as methods. A workflow is defined by a set of methods which all instanciate the class PiseApplication.

SYNOPSIS

# First, create a Bio::Tools::Run::AnalysisFactory::Pise object:
my $factory = new Bio::Tools::Run::AnalysisFactory::Pise();
# Then create the application objects (Pise::Run::Tools::PiseApplication):
my $clustalw = $factory->program(clustalw);
$clustalw->infile($my_alignment_file);
my $protpars = $factory->program(protpars);

# You can specify different servers for different applications :
my $protdist = $factory->program(protpars
-remote => http://kun.homelinux.com/cgi-bin/Pise/5.a//protpars.pl,
-email => your_email);

# Create a new workflow object :
my $workflow = Bio::Tools::Run::PiseWorkflow->new();

# Define the workflows methods using the application objects:
# the application method $protpars will receive the output of
# type readseq_ok_alig from the application method $clustalw.
$workflow->addpipe(-method => $clustalw,
-tomethod => $protpars,
-pipetype => readseq_ok_alig);

# The application method $clustalw will be piped to a second
# application method ($protdist) using the output of type readseq_ok_alig.
$workflow->addpipe(-method => $clustalw,
-tomethod => $protdist,
-pipetype => readseq_ok_alig);

# The application method $protpars will be piped to the application
# method $consense using the output of type phylip_tree.
my $consense = $factory->program(consense);
$workflow->addpipe(-method => $protpars,
-tomethod => $consense,
-pipetype => phylip_tree);

# Run the workflow.
$workflow->run();

The Zero Install system makes software installation not merely easy, but unnecessary. Users run their applications directly from the Internet from the software authors pages.
Caching makes this as fast as running a normal application after the first time, and allows off-line use.
Main features:
- Software is only ever cached, not installed. Anyone can run any software, and nothing is run as root.
- Running a program is done in the same way whether its cached or not.
- Running cached software is as fast as running traditionally-installed software.
- Zero Install is both simpler and more secure than traditional packaging systems.
- Software can be removed from the cache to free space without affecting the behaviour of the system (it will be re-cached on demand).
- You can still run a program you cached last week, without using the net again.

Adobe Flex is the complete solution for building cross-platform Rich Internet Applications within the enterprise and across the web.
Flex 2.0 delivers an integrated set of tools and technology enabling developers to build and deploy scalable Rich Internet Applications.
Flex provides a modern, standards-based language supporting common design patterns and includes a client runtime, programming model, development environment, and advanced data
Main features:
- Flex Framework 2.0
- Flex Builder 2.0
- Flex Enterprise Services 2.0
- Flex Charting Components 2.0
- ActionScript 3.0
- Flash Player 8.5.
Enhancements:
- The Flex 2.0 product line enables developers to build rich, engaging web-based applications based on the ubiquitous Macromedia Flash runtime from Adobe and includes a complete solution for building Rich Internet Applications. Macromedia (now Adobe) originally coined the phrase Rich Internet Application (RIA) to describe a trend in the web development community toward building more engaging web experiences using Flash and HTML.
- The first generation of RIAs combined graphic-rich user interface controls that reduced or eliminated page refreshes. They have since evolved into sophisticated desktop-like applications that integrate rich data visualization components, such as data grids and graphical charts, multimedia audio and video, collaborative features like whiteboards and cobrowsing experiences, and real-time data push. As the complexity of such applications increased, so too did the cost of building and maintaining RIAs. Adobe responded to this need with Flex, which has become the industry-leading RIA development solution.
- Developers are a major focus of the Flex 2.0 release. To ensure that we take the product in a direction that meets your needs, the Flex team is excited to announce the public beta release of the Flex 2.0 product line. If youre not already familiar with Flex 2.0, you can find a complete overview in the David Wadhwanis article, Flex 2.0: Enabling the Next Generation of Rich Internet Applications. Read on to learn more about changes since the release of Flex 2.0 alpha 1.
- The beta 1 release includes updated installers for Flex Builder 2.0, Flex Charting 2.0, Flex Framework 2.0, and Flash Player 8.5. In addition, Flex Enterprise Services 2.0 is now available for the first time. The following outlines what is new in the Flex 2.0 beta 1 release.