It seems like unless we think there are workflow reasons to keep all
commands active, we should keep things simple and make the
'Subscribe' and 'Share' dialogs modal.
The one workflow issue that might arise is that users may launch the
'Share' dialog 1st BEFORE creating and selecting a new collection in
the sidebar to publish.
We may want to add a pull-down to the publish dialog so that users
can select: New collection or any other collection from the sidebar
AFTER launching the 'Share' dialog. The collection selected by
default should still be whatever was selected in the sidebar when the
user launched the 'Share' dialog.
Morgen? Is this simple to do?
Mimi
On Jul 10, 2006, at 5:52 PM, John Anderson wrote:
Hi:
It seems like I have the last Alpha 3 bug to fix. Fortunately, it's
pretty easy, but it does raise and interesting question that I need
to answer before fixing the bug:
Suppose you have a modeless dialog frontmost, i.e. on top of the
Chandler window. Should commands other than those for the dialog be
active, e.g. all the usual Chandler commands, or should only the
commands appropriate for that dialog, e.g. cut/copy/paste be active.
My personal opinion is that it's probably most convenient for the
user to make all the commands active. However, that may lead to a
situation where a modeless dialog might need to reflect changes
from some Chandler command that happens while it's frontmost.
John
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
