Hi all, Flux 0.1.0 has been released. It's yet another tool to solve your workflow problems. What makes it different of the other alternatives (MetaFlow, OpenFlow and DCWorkflow)? First, it's not a Zope product, it's a Python module, packaged and distributed with distutils. This means that it can be used without Zope; when used with Zope, it has to be used from a Python product; it don't provides a web interface to define the workflow. This is a tool for developers. With less than 200 lines of code it's the simplest workflow solution. The workflow is defined as a graph (like MetaFlow and DCWorkflow do), so it's easy to understand. However, it don't has the constrains of DCWorkflow because Flux don't provides any application semantics (it don't tries to guess what you need, you tell it what you need). MetaFlow, until now the product with the best approach to the problem for my taste has inspired Flux. MetaFlow is a Zope product that includes a Python package (MetaFlow.Workflow) which is as simple as DCWorkflow and as powerful as OpenFlow (at least it has the potential to be). It also provides a web interface through the management screens, unfortunately this interface repeats the mistakes of DCWorkflow (probably this has stopped many users to use it). Unfortunately I couldn't take MetaFlow.Workflow because it also makes some mistakes, like to copy the DCWorkflow API, which is not very good. So here is Flux, the best available tool for developers (if you aren't a developer forget it). Download Flux from: http://sf.net/projects/lleu Regards, -- J. David Ibáñez, http://www.j-david.net Software Engineer / Ingénieur Logiciel / Ingeniero de Software