<span class="gmail_quote">On 6/11/07, <b class="gmail_sendername">Earnie Boyd</b> <<a href="mailto:earnie@users.sourceforge.net">earnie@users.sourceforge.net</a>> wrote:</span><br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
But in the later scenario I might not be ready for the editor to<br>publish it. I would always want a [preview] without saving to the DB.<br>I would want [draft] to save a working copy for later revision by me<br>and only me. And I would then want a [ready] for an editor to publish.
<br> If I was editor then I would get the [publish] button instead of the<br>[ready] button.<br></blockquote></div><br>That's actually an improvement that I thought about adding to the workflow module. <br>Instead of having a radio-button allowing to set the workflow status, having buttons for every available workflow status would be clearer (from a user prospective, you'd expect a change of the status setting to be reversible, whereas buttons clearly indicate an action being performed).
<br><br>I haven't heard anything about integrating the workflow module in core (maybe something to consider at some point?) but we could already have this enabled for the basic core workflow.<br><br>Florian<br>