Thorsten Scherler wrote:
El vie, 27-01-2006 a las 11:42 +0100, Andreas Hartmann escribió:
Jörn Nettingsmeier wrote:
[...]
how about the following workflow menu draft?
* submit page
* submit subtree
I'm a little hesitant about "submit subtree". If I imagine myself
working with the system, I think I will submit a page when I'm
ready with editing it. Is submitting a whole subtree really a
reasonable usecase?
i must confess i added it just for the sake of completeness. but
thorsten's argument seems right to me:
Yes it is. Imagine the use case on apache forrest. We store the
documentation in versioned trees e.g.
http://forrest.apache.org/docs_0_80/index.html
http://forrest.apache.org/docs_0_70/index.html
Now assuming forrest is using lenya (like we plan over there) as cms
then before a release we copy the whole 0.8 tree to 0.9. The documents
are all reviewed so I actually *want* to submit the whole tree. Further
if I am reviewer I want to publish without review (like stated the docs
*are* already reviewed).
the moment you get the content from somewhere else than the classic
"edit-one-page-at-a-time" (for example, by importing), the option
becomes interesting.
i'm playing with the code atm. the menu entries are already there.
(/me bursts with pride...)
now for the logic: should i rather split up the .jx files so that one
file corresponds to one menu option, or use a workflow parameter and
stick with the four .jx files we currently have? my preference would be
the latter.
--
"Open source takes the bullshit out of software."
- Charles Ferguson on TechnologyReview.com
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: [EMAIL PROTECTED], Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
