Andreas Hartmann wrote:
while we are talking ui: why are the confirmation dialogs for workflow
transitions new pages rather than small javascript popups? it's annoying
to lose the "visual context" of the page, especially when doing a number
of workflow tasks in a row.
i guess those confirmation pages probably trigger some checks in the
server, but those could be done after a simple javascript confirm dialog
and would only result in a new page if there was an error.
That sounds good, but IMO it should be configurable.
as others in this thread stated, the main reasons for the confirmation
pages are the "notify" option and the "publish complete subtree" option.
these would have to be moved before the confirmation pages can go for good.
how about making "notify submitters" a toggle in the "workflow" menu
(i.e. when you click on it, it gets ticked, when you click again, the
tick is removed)? i don't see why a user would want to change this
behaviour manually during every publish, so a global option seems ok.
to get rid of the other issue, why not have separate workflow items
"publish" and "publish subtree"? this would also get us around the UI
ambiguity that i mentioned in another thread ("workflow buglet in 1.4?"):
if i have both editor and reviewer rights, i see both "submit" and
"publish" in the workflow menu for a page that's in "authoring" state.
however, if i click on publish, the page does not become live. i need to
first click on submit (to myself, basically), then publish my own
submission. is this intentional? if so, the visibility of the menu
options needs to be changed. but i would prefer to be able to publish
things in one step if i have appropriate rights.
andreas explains:
If a document is in "authoring" state, you're still allow to publish
the subtree. Imagine the following situation:
- foo (authoring)
- bar (review)
- baz (review)
- foobar (review)
- foobarbaz (review)
In this case, you go to "foo" and publish the subtree. This may be
a little confusing, because "foo" won't be live after this operation.
iiuc, this issue would vanish if we split the publish action into
"publish page" and "publish subtree".
Maybe you'd like to file an enhancement bug?
let's wait for some more feedback first.
Speaking of this, AJAX comes in my mind again - but I guess we should
defer that to 1.6 unless someone has a patch on hand.
i thought about that too, but i have only started to learn about the
concept, so i was reluctant to throw it into the discussion.
regards,
jörn
--
"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]
