On 13 Dec, [EMAIL PROTECTED] wrote:
> Midgard can do this, but offers "mechanism, not policy". You'll
> have to check for the approval state when you fetch the articles.
This is correct. Most of the workflow-related features
(locking, approving, etc.) in Midgard's content system
are just mechanisms that people writing their own
workflow applications can use. This gives much greater
flexibility for adapting the system to specific needs
than setting the policies in the actual application
server would.
We have written some content management systems ourself
that use these features, and will probably try to release
some of them as example code when Midgard starts handling
packaging properly.
> The roadmap (http://www.midgard-project.org/article/997.html)
> puts versioning in the core for 2.0
However, AFAIK, nobody is working on it currently. As
having good versioning is fairly important, it would be
nice if someone had the time to really focus on this
thing.
If someone is interested, looking at how Xanadu (which
is now Open Source) handles this thing could form a
good basis for research.
Before that, saving past versions as 'reply' articles
will pretty much be the only way to handle versioning.
> Emile
/Bergie
--
-- Henri Bergius -- +358 40 525 1334 -- [EMAIL PROTECTED] --
http://www.iki.fi/Henri.Bergius
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
