Re: [Nuxeo-localizer] Workflow

[Juan David Ibáñez Palomar]

Hi Robert,

A LocalContent instance can have different language versions
of the same information, for example in english, spanish and
french.

Use case. The author adds a new document in english, then it's
sent to the "english to spanish" translator and to the "english
to french" translator. Now the document is in the state "pending
to be translated" for both spanish and french. Then the french
translator does his job. Now the document is in the state "pending
to be translated" for spanish and "translated" for french.

So you have a single object in two states. In DCWorkflow objects
only can be in one state. This is just an example, there're other
use cases that show the well known limits of DCWorkflow. Maybe
it would be possible to find a workaround to addres it, but I
don't want a workaround, I want a simple and elegant solution.

And the solution is.. If I continue I would write be Flux docs,
and now I've other things to do. In the CVS the code is in the
file "flux.py", the file "test.py" shows how to use it.


Regards,


Robert Rottermann wrote:

> Hi Juan,
>
> would you care to explain what ther roblem/solution for multilingual
> documents is?
> thanks
> Robert
> ----- Original Message -----
> From: "Juan David Ibáñez Palomar" <address@hidden>
> To: <address@hidden>
> Sent: Monday, September 23, 2002 12:32 AM
> Subject: [Nuxeo-localizer] Workflow
>
>
>  
>
> > Hi all,
> >
> > Workflow is one of the big things for a multilingual content
> > management system. The first step has been done.
> >
> > None of the available Zope solutions satisfies my requirements.
> > DCWorkflow is simply unable to manage multilingual content as
> > the relation between objects and states is one to one. OpenFlow
> > is too much complex, more than it needs to be. MetaFlow is the
> > best one, but not mature enough, and repeats some mistakes of
> > the other two solutions.
> >
> > In the CVS of the lleu project you'll find the module "flux":
> >
> >  http://sourceforge.net/projects/lleu
> >  http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/lleu/flux/
> >
> > Flux is a Python module. So it can be used not only with Zope,
> > but also with any other Python based application. In the other
> > hand, it can't be used from the management screens; but it's
> > possible to develop a Zope product that lets to do it, maybe
> > providing a web interface similar to DCWorkflow, for example.
> >
> > Flux is simple, around 100 lines of code, don't has restrictions
> > because it lacks any specific application semantics.
> >
> > Flux is in early stage of development, no documentation is
> > available yet. I'm going to use it for a project, this will
> > let to reach alpha stage and release 0.1 to the [Python] world.
> >
> > This first application is not multilingual. Later I'll combine
> > Flux with Localizer to make a multilingual content management
> > application, maybe to manage my web site as a first try.
> >
> >
> > Best regards,
> >    


--
J. David Ibáñez, http://www.j-david.net
Software Engineer / Ingénieur Logiciel / Ingeniero de Software