I am actually working on such an animal, but I have no idea when/if I will
be able to release the code. My request to the powers that be to be able
to release my code is moving very slowly.
In the meantime you can use it with a minimalist
portal_actions/types/workflow triad with a little
Stephan Richter wrote:
I am actually working on such an animal, but I have no idea when/if I
will be able to release the code. My request to the powers that be to
be able to release my code is moving very slowly.
In the meantime you can use it with a minimalist
PLEASE, look at OpenFlow (a Zope Product). It is based on years of research
and covers all aspects. It works very well too!
Correct me if I'm mistaken, but from what I saw OpenFlow is very low
level. You'd need an entire additional layer to attain what DCWorkflow
does.
Not that it's bad to
Lennart Regebro writes:
...
Here are some things that I feel should be introduced into Zope:
- Workflow support. (Because everybody needs it)
You know DCWorkflow?
- Versioning. (Because it's hard to do as a product)
CVSFolder is quite near: I see currently two remaining issues:
*
Hello Lennart,
On Monday 03 December 2001 05:06, Lennart Regebro wrote:
After the discussion here I'm slowly starting to form a picture in my mind
of how to solve the problems.
First some basic facts of life:
- Zope corp needs to do what Zope corp thinks it can make money on.
- We (that
From: Dieter Maurer [EMAIL PROTECTED]
Here are some things that I feel should be introduced into Zope:
- Workflow support. (Because everybody needs it)
You know DCWorkflow?
Yes. I think it should be moved off CMF and into Zope proper.
- Versioning. (Because it's hard to do as a
On Monday 03 December 2001 10:09, Danny William Adair wrote:
Introduced to us as the Portal Toolkit, later labeled as probably
evolving into a commercial product (couldn't find it in the archives when
I tried a minute ago, but I know I wasn't dreaming when I read it), then
renamed to Content
