[Chandler-dev] Re: Last Alpha 3 bug needs a question answered: What commands are active when a modeless dialog is active?

[Reid Ellis]

+1 for modeless dialogs. This also allows lengthy operations to use a  
localized progress bar.

However, the cases Morgen mentioned (duplicate operations, deleting a  
collection that is being used) do have to be attended to.

Reid

On Jul 11, 2006, at 16:41, John Anderson wrote:
> Users prefer modeless dialogs to modal dialogs, so I'd prefer to  
> keep them modeless unless we run into a problem -- which we don't  
> currently have.
>
> John
>
> Morgen Sagen wrote:
>> On Jul 11, 2006, at 12:03 PM, Mimi Yin wrote:
>>
>>> 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.
>>
>> Bummer, and after all the work we did to make them asynchronous...
>>
>>> 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.
>>>
>>
>> A pulldown listing all collections in the sidebar wouldn't be  
>> difficult.  Having the "New collection" option doesn't make sense  
>> to me though, because the user won't have an opportunity to name  
>> this new collection unless we add another field to the dialog (or  
>> pop up a second dialog), and therefore the subscribers will just  
>> get an "Untitled" collection.  I suppose publishing an empty  
>> collection could make sense in some situations, but then again I  
>> can't think of one at the moment.  Do you have an example?
>>
>> ~morgen