[Zope-PTK] CMF Dogbowl: workflow Proposal

[Shane Hathaway]

Kent Polk wrote:
> 
> On 16 Mar 2001 23:10:02 -0600, Shane Hathaway wrote:
> >Kent Polk wrote:
> >> However, it appears to me that review-* actions are pretty hard-coded
> >> into the CMF at this point.
> >
> >Think about it this way: if the new DefaultWorkflow.py weren't there,
> >how many references to "review*" would there be?  Unless we've missed
> >some, there would be none at all.  That means DefaultWorkflow.py fully
> >encapsulates the CMF default workflow.
> 
> It's also in the dtml in :
> CMFDefault/skins/content
> CMFDefault/skins/generic

They don't count. :-)  I think that with a new workflow, you're *very*
likely to need updated skins as well.

> Which would be pretty easy to change. It might be nice for the
> Actions box to automatically be able to iterate over other workflows
> also, but expect that is why you intend to make WorkflowTool
> folderish instead of just adding a mechanism to specify what
> 'default' workflow each object needs to use. Would make it easier
> to iterate over the workflows in dtml, no?

The actions box already iterates over the workflows.  It weaves all
available workflow actions from all workflows.  There are more
generalizations that could be made but I think they might be overkill.

> >So, if the default workflow doesn't quite fit, the intention is that you
> >replace or subclass DefaultWorkflow.  That doesn't mean you need to
> >change CMFCore, but until the WorkflowTool is folderish, it does mean
> >you need to make your own WorkflowTool.
> 
> I'm working on it. :^)

I'm glad to hear you're getting into it.  

Shane