On 12/16/2015 12:01 AM, Sam Davis wrote:
because the user can disable them
That's kind to give the power to the user, but in the end, put yourself
into an Eclipse IDE user shoes: Are users aware that long startups can
be configured by them? Will they be able to find the right UI entry to
tweak the startup? If they manage to get to the list of startups, will
they easily identify which ones are necessary for them or not, or
time-consuming?
None of these operations is trivial enough for users to expect them to
take care of it.
It's a recurrent issue in Eclipse IDE, for many many operations and
options: how are users supposed to *discover* them? If there is nothing
driving user to them, it's more or less the same as not having them.
Why not scheduling a job inside the IStartup? So you get the best user
experience with faster startup, and still the possibility for advanced
users who actually tweak that kind of thing to enable/disable it?
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
