The real problem is that the version of wiki we currently use doesn't support any concept of workflow. That is fine for the company now but as it matures in its processes, a more mature solution will become more and more compelling. Various solutions include...
1. The current wiki implementation is open source, modify the freely available and unencumbered code to support workflow. 2. Convert the wiki files to plone documents that are already workflow enabled. 3. Write a new app that uses the current wiki docs but with the desired features. My inquiry to comp.lang.python is part of this investigation. I'm guessing that writing a zope application would be mandatory for option 2 and a desireable possibility for option 3. I'm also just curious as to the viability of zope from a developer's perspective. On Sun, 26 Jun 2005 23:14:48 -0500, Terry Hancock wrote: > However, I'm not sure why you want this information. If you are > trying to import data into Zope, you are more likely going to be > using Zope, not accessing ZODB directly. > > Without more specifics about what you are looking for, it would be > hard to reply further than this. > > Cheers, > Terry > > -- > Terry Hancock ( hancock at anansispaceworks.com ) > Anansi Spaceworks http://www.anansispaceworks.com -- http://mail.python.org/mailman/listinfo/python-list