Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ui-best-practices-working-group] Modal dialogs

The conclusion seems to be that it's not.

Sorry, I guess I didn't give a direct enough answer. I think it is. Flipping the modal flag would take a couple hours. Fixing the shell parenting code on GTK would take a day or two, tops. Both are easy tasks.

If we want to experiment with my edilog metaphor, it took me about a month to write the original library and I could probably reproduce it in less time than that, particularly if I could build on top of the E4 DI code (I asked a question about this on the UI mailing list).

If we want to create a notification framework for Eclipse (to replace dialogs opened by background threads), there's a bug open for evaluating and porting the Mylyn notification framework to the Eclipse platform. A couple developers could probably finish this up in about a week.

All of these are tasks that would go a long way to eliminating both dialog boxes and modes, and they're all things a single developer could tackle in a reasonable amount of time.

On Tue, Sep 20, 2016 at 8:03 AM Mickael Istria <mistria@xxxxxxxxxx> wrote:
On 09/20/2016 05:00 PM, Stefan Xenos wrote:

However, just flipping the modal flag won't really address the more serious UX issues caused by the presence of dialog boxes. If I were to write my own patch here I'd be inclined to spend my time replacing the dialogs rather than simply making them nonmodal.
Just to be clear: I don't plan to work on it soon. It was just asking to evaluate whether this discussion is easily actionable. The conclusion seems to be that it's not.

Mickael Istria
Eclipse developer for Red Hat Developers
My blog - My Tweets
ui-best-practices-working-group mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top