I finally caught up with that thread, which
- like so often - heavily diverged from the initial and well-focused suggestion
from Mickael :-)
> So an easy
way to improve Eclipse IDE would be to add to the Ctrl+1 the operations
that users likes in this very narrow context.
This suggestion in Mickael's initial
e-mail is a very good one, and we can discuss which things to add via bug
480131. Please add your comments
The other mentionable topics I saw in
- XML Editor
Packages can decide to include this.
Even CDT can do so. Hence, I do not consider this a big issue - maybe it
should just be part of all packages these days. There is no need to restructure
any projects or move code around.
- Install hell for our users
I totally agree with this. Even with
EPP it is hard for a user to pick the right package, e.g. the 'Eclipse
IDE for Java Developers' package contains the XML Editor but 'Eclipse IDE
for Eclipse Committers ' does not. In our Eclipse Vision meetings from
last year our hope was that Oomph (the new Eclipse installer) would help
to fix this. So, maybe we need to push more on this. Another idea that
we discussed in those meetings and was also mentioned in this thread is
a hook, so that when a user opens a certain file and no editor is available,
we suggest to install the corresponding (small) feature(s). I think the
latter is definitely worth working on and could qualify for FEEP.
- Hard to know all our cool features
I like the idea of more aggressively
advertising our IDE features on the web pages and especially on a combined
IDE page. JDT is definitely willing to participate here, but only to provide
the content and not the design. Like Doug and Ian, I don't think FEEP money
would be good spent here.
Mickael Istria <mistria@xxxxxxxxxx>
about the IDE'" <ide-dev@xxxxxxxxxxx>, jdt-dev@xxxxxxxxxxx
I've spent some times asking former Eclipse RCP developers now converted
to the 300$/year IDE on what they thing are the best things that are missing
in Eclipse IDE.
What they tell first is the quality of the "quick-fixes" in IntelliJ.
But when you get into details, what makes the difference isn't really that
IJ has editing/refactoring operations that Eclipse IDE doesn't have, but
more that IJ shows the useful ones (and only the useful ones) on their
In Eclipse, a lot of operations are available under Source and Refactor
context menu, but it's a lot of menus to browse, it takes a lot of time,
mostly requires to use mouse, requires to read a lot of entries that are
contextual to the editor but not to the active selection... It's complicated.
Eclipse has the very good Ctrl+1 menu, which is basically meant to host
such small operations that are in the context of the selection in an editor.
Eclipse IDE (precisely JDT UI) already shows a few relevant ones, but some
other good ones are missing.
So an easy way to improve Eclipse IDE would be to add to the Ctrl+1 the
operations that users likes in this very narrow context. If you get such
an idea, please report it to JDT/UI and share it. I believe fixing that
isn't a too difficult task, with no risk at all, and that it would provide
much user satisfaction. It could even be a great topic for a hackathon.
I plan to make a more direct comparison of these quick-fixes one day (cannot
be more precise, so don't wait for me if you're faster) and to come up
with a list of the ones that are missing in Eclipse IDE to make this Ctrl+1
so efficent that user won't have to dig in the context-menu and will always
get their favorite operation in a few keystrokes.