[Zope-CMF] Re: [dev] enhancing Actions: a rough proposal

[Florent Guillaume]

> I try it again with other words, referring to this part of your previous 
> mail:
> 
> > Completely removing the ability to be an action provider means that
> > for each workflow transition you have, you have to also create an
> > action, in a completely different part of the site, which "sho me"
> > expression must match the "is possible" expression of the
> > transition.
>[...]
> Actions and transactions don't have to be unrelated if they are stored 
> in different places. The ActionsTool could query the available workflow 
> transitions and return the corresponding Actions. This way we don't 
> have to define redundant permissions / guards / expressions.

Another way would be to have workflow actions defined with the other
actions, but use a special tales expression like:
  python: context.portal_workflow.wf_foo.publish.isGuardAllowedFor(object)
or add a new function to the namespace so that we can shorten that to
  python: workflow(object, 'publish', 'wf_foo')
the last argument being optional if the object belongs to only one workflow.

Just throwing ideas around...

Florent

-- 
Florent Guillaume, Nuxeo (Paris, France)   CTO, Director of R&D
+33 1 40 33 71 59   http://nuxeo.com   fg at nuxeo.com