Free workflow software for linux

DwWorkflow is a datawarehouse process workflow server and generator of datawarehouse mappings.
It allows the user to define dependencies between tables or files and processes and it runs processes in parallel according to these metadata.
DwWorkflow can run with or without an SQL database server. A process can be any program, not just a database statement.
Enhancements:
- This release includes a graphical plugin for the Eclipse platform for the dwworkflow server, and also includes needed changes in the server for the plugin to work.

Workflow::Factory is a Perl module that generates new workflow and supporting objects.

SYNOPSIS

# Import the singleton for easy access
use Workflow::Factory qw( FACTORY );

# Add XML configurations to the factory
FACTORY->add_config_from_file( workflow => workflow.xml,
action => [ myactions.xml, otheractions.xml ],
validator => [ validator.xml, myvalidators.xml ],
condition => condition.xml,
persister => persister.xml );

# Create a new workflow of type MyWorkflow
my $wf = FACTORY->create_workflow( MyWorkflow );

# Fetch an existing workflow with ID 25
my $wf = FACTORY->fetch_workflow( MyWorkflow, 25 );

Public

The Workflow Factory is your primary interface to the workflow system. You give it the configuration files and/or data structures for the Workflow, Workflow::Action, Workflow::Condition, Workflow::Persister, and Workflow::Validator objects and then you ask it for new and existing Workflow objects.

Internal

Developers using the workflow system should be familiar with how the factory processes configurations and how it makes the various components of the system are instantiated and stored in the factory.

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();

JawFlow is a Workflow Engine partially conformal to WfMC (www.wfmc.org) directives, completely written in Java using JMX technology. It understands XML Process Definition Language (XPDL) and can be customized using activities written in Java or in any scripting language supported by BSF.

JawFlow is composed by many interacting modules. Many of these modules are JMX Mbeans and so they need a JMX Agent to run. To develop, test and run JawFlow we used Jboss AS but since there are no strict dependencies in the code related to Jboss it should be installed in any application server supporting the JMX technology.

ExiFlow is a set of tools (command line and GUI) to provide a complete digital photo workflow for Unixes.

EXIF headers are used as the central information repository, so users may change their software at any time without loosing their data.

Which tools are provided by ExiFlow?

exigui

This is the GTK frontend for all other tools but exiimport. If the mouse is your best friend you will like this one.

exiimport

Import files from given directories to your photo folder. Optionally unmounts source media after successfull import.

exirename

Rename a bunch of image files according to our holy file naming schema.

exiperson

Personalize images by setting EXIF fields to values spezified in exif.cfg or on command line. Any arbitrary field name may be configured or given. This is normally used for artist and copyright information.

exiassign

Find groups of derived images and exchange EXIF information between them. That way, a freshly edited derivate can automatically inherit its mothers EXIF information.

exigate

Automatically gate information between gthumb metadata and the images EXIF information. This lets you describe and tag your photos whith gthumb and transfer everything to the according EXIF tags afterwards. The other direction is also possible, so you are never bound to using one specific piece of software.

Fact Or Fiction is a deck editor for the popular trading card game "Magic: The Gathering".
Fact Or Fiction project can be useful for organizing and keeping track of your cards.
It supports card filtering, automatic image loading, deck sorting, and quick entry.
Images:
Card images are automatically downloaded from internet sites. Take a look at the screenshot to see the settings necessary to access Gatherer for the images.
Be aware that Oracle text files do not provide the set of the cards. Therefore a given lists of subdirectories is searched for the card image. To allow rapid deck entry this is done in a background process.
This dialog will also allow you to set your proxy settings to download the images.
Enhancements:
- This release is in sync with the "Dissension" edition of Magic: the Gathering.
- Unglued and Unhinged cards have strange names, and some issues with picture download were fixed.
- The homepage was updated with the correct workflow to build a working (UTF8 encoded) Oracle.
- The size of the edition list control was decreased.
- Dissension mana symbols were added.
- Dissension was added to the initial download list.
- Image scaling was reworked to use bilinear filtering.

UICollection is a rich set of Java Swing widgets, solutions for common and not so common Swing projects, and a workflow using a graphics designer to merge all solutions into one project.
UICollection is a project that can be used in any application, commercial or otherwise. Despite being free UICollection has advanced user-interface features allowing you to create more professionial looking GUIs, faster.
There are various products which are part of this project, each brings a completely seperate component, or framework which enhances your user interfaces. All of them add to the synergy of the whole by being complementary in nature. Each can be used seperately, allowing an easy learning curve.
The core component is the designer, this is the one that binds all other components transparantly into one product. The designer is a GUI Builder with a twist; it allows you to build your user interfaces by point and click in such a way that the traditional disadvantages of code generators is taken away. Additionaly the designer itself is so easy to use that your graphics designer can use it to make drafts, or fine tune your finished products. The designer should actually be called a component of a highly-optimized, but very flexible workflow.
What binds all components is a next-generation Swing Look and Feel, the UICTheme is build for cross-platform look and feel in such a way that the feel part can be considered native. This is because of the huge amount of attention it spents on usability features that are common on the various operating systems Java supports, but still have not found their way into the core Swing distribution. All screenshots on this website will be based on the UICTheme, unless otherwise specified. Use the webstart demo if you want to get an instant feel for it.
Enhancements:
- The spinbox is no longer allowed to get higher than its textfields preferred height.
- The GroupBox is repainted after calling setEnabled (which is needed to update the ghosted state).
- Double number values were made to work.
- UICCalender was made to work with Java 5 and 6.

Cosmo is a calendar server. With your favorite calendar program (Chandler, Apple iCal, Mozilla Sunbird, or any other WebDAV or CalDAV enabled client), you can share your calendar with other people by publishing it to Cosmo. Once your calendar is stored on the server, you can give permission for others to subscribe to it, and even modify it if their calendar client allows.
Cosmo is a file server. You can store arbitrary files in your home directory in Cosmo with any WebDAV client (including the Windows XP, Linux and Apple OS X file managers), and you can share them with others in the same way as your calendar.
Cosmo is not a web-based personal information manager. The Scooby project aims to provide an innovative web interface for calendaring and will be tightly integrated with Cosmo.
Cosmo is not a content management system. There is no support for common CMS features such as versioning, content editing or workflow. Cosmo very simply allows calendar and file management applications to publish and subscribe to a content repository.
Enhancements:
- This release can share editable calendars without requiring Cosmo account signup.
- It has better interoperability with other calendar applications, display of time zones on calendar events, email notification of an updated event on a shared calendar, and improvements to the administrator user interface.