"workflow" module is committed

I committed a new "workflow" module to bitkeeper. It's basically
re-using TikiWiki's Galaxia Workflow Engine with a port of the
corresponding interface scripts and templates to Xaraya.

<for people who know Galaxia>
The internal Galaxia library hasn't been changed much other then
adding a GALAXIA_DIR prefix to all places where the lib/Galaxia
directory is used. There's a diff.txt in modules/workflow/lib with
the exact changes compared to the current CVS versions of
Galaxia.

One important change is that automatic routing no longer tries
to call the next activity via an external web call, but simply via
an internal API function call. That should allow us to trigger
start activities from e.g. within hook calls in the future, so
that the creation/modification of module items might start
a workflow process in some next release.

The interface scripts and templates were "converted" to
Xaraya thanks to a fake tiki-setup file and some quick
& dirty translations from Tiki/Smarty to Xaraya/BL.
</for people who know Galaxia>

Volunteers willing to clean those up are certainly welcome :)

I'm going to concentrate on seeing how we can re-use the
workflow engine in other places of Xaraya, so as long as
you maintain (at least) the current functionality, feel free to
expand/improve the GUI functions/templates etc.

What can you do with it ? Well, you can load CDs from a
CD collection for instance :)

If you want to create your own processes, you really should
read the Galaxia introduction and the user manual at
http://tikiwiki.org/tiki-index.php?page=GalaxiaWorkflow
They're not large at all and read quite nicely - props to the
authors.

And feel free to contribute any interesting processes you might
create as well - there's a nice Save Process to XML feature too :)

Have fun,

Mike.