[jdt-dev] Is completion cycling a good usability pattern?

[Mickael Istria <mistria@xxxxxxxxxx>]

Hi all,

I'd like to debate a UI pattern that's in JDT and that I believe is far from being the most user-friendly one: completion cycling.
It might be interesting in some cases, but in general, I guess users just want completion to work at first try. Providers is not an immediate user concept, it's more an implementation choice, so cycling through providers doesn't seem to provide value to most users.
So my suggestion would be that, by default, all providers take part of a unique completion proposal, and that cycling gets disabled. Of course, we should and can easily keep the ability to configure cycling, but just not use it as default.
WDYT?

PS: here is a related issue to fix before removing cycling https://bugs.eclipse.org/bugs/show_bug.cgi?id=464143

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets