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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

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

From: Mickael Istria <mistria@xxxxxxxxxx>
Date: Thu, 09 Apr 2015 13:59:17 +0200
Delivered-to: jdt-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/jdt-dev>
List-help: <mailto:jdt-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/jdt-dev>, <mailto:jdt-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/jdt-dev>, <mailto:jdt-dev-request@eclipse.org?subject=unsubscribe>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0

On 04/09/2015 01:44 PM, Aaron Digulla wrote:

I don't especially mind since it's easy enough to disable/uncheck all providers in the preferences page.
That way, people can balance their needs to see everything at once (with less speed) or cycle.

Everything is possible with Eclipse IDE, everyone knows that. But the most frequent complaint is that Eclipse IDE is complicated and requires many tweaks before fitting the most common use-cases perfectly.
All that discussion is indeed a matter of discussing what are the best default for the average Java developer.

Do we have a good way to conduct surveys to IDE users? That could be one of the questions to ask.

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

References:
- Re: [jdt-dev] Is completion cycling a good usability pattern?
  - From: Aaron Digulla

Prev by Date: Re: [jdt-dev] Is completion cycling a good usability pattern?
Next by Date: [jdt-dev] Performance issues using IType interface
Previous by thread: Re: [jdt-dev] Is completion cycling a good usability pattern?
Next by thread: [jdt-dev] Performance issues using IType interface
Index(es):
- Date
- Thread

Breadcrumbs