[Zope-PTK] Tabular object workflows

[Kent Polk]

Tres Seaver wrote:
> Kent Polk wrote:
> > 
> > One thing I am thinking about implementing that might be generally
> > useful to us and possibly to someone else would be to workflow a
> > tabular object, such as a spreadsheet.  This tabular object could
> > use the current workflow concepts for now.  As mentioned below,

> I owe you a longer response on this, but am a bit bandwidth-
> constrained at the moment :)

With all the changes to the CMS lately, I can imagine, and don't
want to slow you down. I brought it up again because you are dropping
charges all around the topic, with the discussions on portal skins
and the ZTopics-type heirarchies, which I suspect are both essential
concepts in implementing subworkflows.

> The short answer is:  not quite yet.  We will ship CMF 1.0
> without the highly-configurable, state-machine-driven workflow
> tool which I have described in the past.  We are planning on
> an iterative release process (likely with 4-6 week iterations)
> following "1.0", and haven't yet decided how to roll that
> tool out.

Understood. 

> In the meantime, please have a look at the 'portal_workflow'
> interface (in PTKBase/interfaces), and see if you think it
> could serve as a wrapper around the kinds of workflows which
> would scratch your itch.

Not there yet, which is partly why I'm probably going to try to
implement a tabular workflow object using the current workflow,
mainly so I can proceed with moving my workflow object classes over
to Zope. I have no idea if a tabular workflow object would be
generally useful except as a basis for other objects, but maybe
I'm missing the boat. It's interesting to me that almost every
workflow I'm developing requires tabular objects at their core.
It it this way with just me? :^)

Thanks