Re: [Openflow-dev] Quick start

[<jm...@so...>]

> Let's see an example, imagine that I want to add moderation to a weblog.
> The weblog has a Zope meta type named "Article". I would like to have
> this:
>
>   1. An anonymous user posts a new article;
>
>   2. A reviewer sees the new article in his list of articles pending of
>       review;
>
>   3. The reviewer can accept or reject the article.
>
>
> I know how to do this with DCWorkflow. An article is an object that can
> be in two states, "pending" and "public". The "Anonymous" role only has
> the permission "View" if it's in the "public" state. This is a simple way=
 to
> filter the articles that are shown in the weblog, users only show the
> articles
> they're allowed to see.
>
> How to do this with Openflow?


In Openflow you define the process this way:

1) An anonymous POST an article  =3D First activity

2) A reviewer REVIEW the article =3D Second activity


If the reviewer accepts the acticle there is 3 things to do:

  a) The secretary must phone to my mother, and say "Your soon will arrive
late tonight, we have an important article".
  b) The article must me put on the web, automatically
  c) A remote methods must be called automatically, via xml-rpc, to send
     a hash of this article to a copyright database, in New York.


You see, this this activity bases. Activities =3D Actions to do

This can be related to the main object (b), but this can also be a call to
a method (c), or an action than an human must do (phone to my mother).

It is the classic definition of an algoritm. The diagram process, things
to do... It is the way you draw something on a paper when you define a
process.


The difference is that the diagram is not related to any object. Generally
it will, but this is not mandatory.



--=20

      __o
    _ \<_
   (_)/(_)

Saludos de Juli=E1n
EA4ACL
-.-

Foro Wireless Madrid
http://opennetworks.rg3.net