|[ui-best-practices-working-group] Make WizardDialog.run(...) a bad practice as it block all UI ?|
I'm trying to find a decent solution to https://bugs.eclipse.org/bugs/show_bug.cgi?id=495007 . I'd like to discuss the cause of this issue, and most likely of some other similar issues - or workarounds such as requiring to hit "Enter", reducing "fluidity" of the interface- in Eclipse IDE:
WizardDialog.run(...) blocks the whole UI when processing a long operation. However, in most cases, some interaction is still possible and relevant with some parts of the wizard. I believe if we want to encourage writing better workflows, we need Plugin Developers to consider exactly which interactions they need to block when running an operation rather than greedily making nothing possible and blocking user.
Should I report it in some bugzilla? Against which component?
Platform UI/UI Guidelines?