Fair enough...try 2...how about having a single window hosting all currently active Wizards / Dialogs, each with their own tab (think of it as a specialized Detached Window) ? If neither of these approaches work then you're limited to the 'many windows' paradigm.
Eric
 Mickael Istria ---09/14/2016 09:57:16 AM---On 09/14/2016 03:51 PM, Eric Moffatt wrote: >
From: Mickael Istria <mistria@xxxxxxxxxx>
To: platform-ui-dev@xxxxxxxxxxx
Date: 09/14/2016 09:57 AM
Subject: Re: [platform-ui-dev] Blocking UI: Wizard Dialog modality
Sent by: platform-ui-dev-bounces@xxxxxxxxxxx
On 09/14/2016 03:51 PM, Eric Moffatt wrote:Why not just make non-modal Dialogs / Wizards 'Editors' (i.e. site them in the editor area with their own tabs...)
I don't think this would fit. One expects an editor to be a way to view and change a file. Dialogs have another purpose which is to "actively" interact with user without necessarily being related to a file or a modified artifact.
IMO, dialogs and editors are better being kept separated, or it will become more complex for users to figure out where to find the interaction they want and what kind of effect they can expect from the items shown in the usual editor stack.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev
|
