50 slides of IDE — Eclipse Con France 2015

Don’t worry: slides with each tip will be provided

CTRL-S (Yay!)

This one is very useful. And alternatively you can also click (with the mouse) on the small icon that you will generally find on the left (because this is actually customisable, I’ve been told). I like it because it prevents you from going into the File/Save Menu. It took me years to find this one. I hope you will enjoy it too!

I hope you will like it as much as I did. I hope.

Let’s now get a bit more serious, only 34 minutes left…​

In Java/Appearance/abbreviate package names :

Example:

Ctrl-O displays all the methods of the current class

Or Inherited

Ctrl-O-O methods of the current class + parent

Or more selectively

Use space or < to stop matching

Alt-Shift-x will display a contextual menu.

Example: you’re in a JUnit class, just type Alt-Shift-X then T to run the tests.

Be explicit. Changing the code it’s natural to just run Ctrl-F11 or F11 to re-execute the previously ran test

Run/Debug/Launching/Launch Operation/Always launch the previously launched application

Type Ctrl-Shift-1 (or click on the lightbulb on the left of the line) to see what the possible actions are on the current focus

Select text, right click and extract the whole code block into a new method easily.

Inverse: see (11/51) Inline Method

Easily inline the code of a method.

Inverse: see (10/51) Extract Method

Replace your ternary expression with an if-else (more often than not!)

Before :

After :

Select the if/else to invert, and call the Quick Fix

Just type the collection/array, and call the Quick Fix

If putting your cursor next to the curly brace isn’t enough to find the associated closing/opening one:

Use Ctrl-Shift-P

Accessible through Clean Up & Quick Fix

Not enabled by default. In Java/Editor/Typing.

Use Ctrl-Shift-3 on a selected item, then start typing to filter the possible actions in the Quick access menu.

Useful: be able to automatically format only the code just modified when saving the file.

See in Java/Editor/Save Actions/Format source code/Format edited lines

Select the text you want to format, and hit ctrl-shift-f as usual.

Typing Ctrl-Space many times shows different proposals.

Those are actually configurable (list and order of proposals).

See Java/Editor/Content Assist/Advanced.

Autocomplete static imports!

In Java/Editor/Content Assist/Favorites

Lets you add more typesafe-ness in your codebase (at least way more than Javadoc does!).

Beware: it’s not enforcing anything at all at runtime. This is only hints for the developer.

To go even further:

Advice: annotate the package itself to define the default value for a whole package

⇒ package-info.java

Java/Editor/Content Assist : toggle "Completion overwrites" instead of "Completion Inserts"

Can be live toggled using Ctrl key.

Inside an instanceof block, analyzes the type of the given instanceof and autocompletes with its methods:

In Java/Appearance/Type Filters

To filter out java.awt.* for example…​

Filter out method coming from Object! (who wants to call notify()…​)

Categorize Filtering/choosing which methods to display in the Outline using javadoc’s @category tags

Be able to filter out stack when debugging:

Alt-Shift-A or the icon, as if Sublime Text invented it all ;-)

Present complex/weird physical data structure in a logical way in the debugger

For reference see the official documentation or that forum discussion.

Ctrl-M

Ctrl-D

Useful to categorize projects, or packages.

https://recoveringprogrammer.wordpress.com/2013/04/06/using-eclipse-scrapbook-to-quickly-test-your-code/

You can easily add any code block for future reuse.

Difference with snippets: can be variabilized.

Cf. Java/Editor/Templates

Thanks Vincent!

Example: formatter on/off (cf. (21/51) Formatter: don’t touch that part (using begin/end tags))

Many conditions, not always well-known

Use it to debug :

Gotcha: in external jars (like rt.jar) without local variable table, use the arg0, arg1…​ placeholders for parameters, instead of the original parameter names.

When debugging, you don’t have to put a breakpoint on some line to take the debugger up to it.

Just put the cursor on the line you want, then Ctrl-R (or right click/Run to line)

http://eclipsesource.com/blogs/2013/01/08/effective-java-debugging-with-eclipse/

Many quick fixes are actually available, but not always through cleanup

Possible since Luna SR2

Complementary to (25/51) JSR305 annotations to help null analysis

New in Eclipse Mars, released yesterday! (24/03/2015).

See JSR305 externally annotated classes (Eclipse Mars)

Useful if you often switch between workspaces.

Under General/Workspace, you can set the workspace name field.