12 Tips to make you more productive using Eclipse

Updated 3 months, 1 week ago

Source: http://www.turnleafdesign.com/

Integrated development environments make developing application fair easier. They highlight syntax, let you know if you have a compilation error, and allow you to step through your code among so many other things. Like all IDEs Eclipse has a bunch of little shortcuts and tools that can make your life a lot easier, I've compiled a list of several that I use on a daily basis:

1. Auto-complete – Eclipse has an auto-complete feature that can be accessed with ctrl + space. When clicked a small ...

  • 43 comments on this story
PRO

50% positive

Showing 31 relevant reactions out of 43.

dukthen 3 months, 1 week ago on Reddit

Here's my take on the list:

1. use vim

1. use vim

1. use vim

1. use vim

1. use vim

1. use vim

1. use vim

1. use vim

1. use vim

1. use vim

1. use vim

1. use vim

Reply

hectorwc 3 months, 1 week ago on Reddit

Yeah, I was looking for the tip on how to make it not freeze up for thirty seconds whenever I try to do anything.

Reply

pemboa 3 months, 1 week ago on Reddit

On what are you running Eclipse to see this?

Reply

b100dian 3 months, 1 week ago on Reddit

> Automatically generate getters and setters

No thanks, I use a modern language with built-in getters and setters.

Reply

MindStalker 3 months, 1 week ago on Reddit

.NET?

Doing things behind your back for you is just stupid.

Reply

b100dian 3 months, 1 week ago on Reddit

C#, Actionscript 3, JavaScript 1.5, Vala, Delphi to name just a few.

Reply

f3nd3r 3 months, 1 week ago on Reddit

Wow, they could have at least checked it for typos one time.

Reply

codecafe 3 months, 1 week ago on Reddit

> more productive

> eclipse

Did you mean to submit this to the /r/funny/...? Oh... you were being serious?

Reply

strelok 3 months, 1 week ago on Reddit

What a lame list. I was expecting to finally find the magic option how to make Eclipse auto detect static methods instead of going into Content Assist->Favourites, or something that will make Groovy usable in Eclipse. But, no, HOW TO RUN A FUCKING UNIT TEST! :) Tip No. 1 should be download IntelliJ. Oh IntelliJ I miss you!

Reply

masklinn 3 months, 1 week ago on Reddit

IntelliJ is not gone. IntelliJ will live forever… in our hearts.

Reply

masklinn 3 months, 1 week ago on Reddit

1. Use intellij

Reply

kopkaas2000 3 months, 1 week ago on Reddit

Too lazy to read the article. Is tip 1 "apt-get install vim"?

Reply

vonbladet 3 months, 1 week ago on Reddit

M-x eclipse-mode

Reply

pozorvlak 3 months, 1 week ago on Reddit

Meh. Knew all those already. OTOH, I do use them all more-or-less constantly, so I suppose they're worth collecting together :-)

Reply

rene_silva 3 months, 2 weeks ago on Twitter

leyendo: "12 tipos para ser más productivo en Eclipse" http://icio.us/wcfvj1

Reply

elliotrock 3 months, 2 weeks ago on Twitter

Hey bro @retrogamer4ever , have you seen this http://bit.ly/17nA49 : 12 Tips to make you more productive using Eclipse #flexbuilder

Reply

Anthon Yuan 3 months, 3 weeks ago on Wordpress

ALT-SHIFT-D is for debugging, ALT-SHIFT-X is for executing

Reply

Sinisa 3 months, 3 weeks ago on Wordpress

crtl-shift-L : all keyboard shortcuts.

Reply

wookashs 3 months, 3 weeks ago on Wordpress

Ad 5. ctrl + H on method or type (who uses mouse) ;]

Also ctrl + t to look for type hierarchy

Reply

uberVU - social comments 3 months, 3 weeks ago on Wordpress

Social comments and analytics for this post…

This post was mentioned on Twitter by TurnleafDesign: Rambling on: 12 Tips to make you more productive using Eclipse http://www.turnleafdesign.com/?p=240…

Reply

Trent 3 months, 3 weeks ago on Wordpress

ctrl-shift-t : Open Java Type

ctrl-shift-r : open resource (i.e. any file in project)

ctrl-alt-t: Refactor menu

…and you should probably memorise all the shortcuts in that menu.

Reply

nn14 3 months, 3 weeks ago on Wordpress

Very Helpful. Many thanks

Reply

6553321 3 months, 3 weeks ago on Reddit

For the quickly format your code point, I saw something on Proggit once where someone said that if you're going to make a checkin that fixes formatting for a large chunk of code, only fix formatting in that checkin. Otherwise it becomes hard to distinguish between real changs and indentation changes if you do an svn diff.

Reply

Scaryclouds 3 months, 3 weeks ago on Reddit

Your definitely right there, you do want to attempt to merge code or view code after it has been formatted (assuming there was a sizable amount of changes). It's one of the reasons once you get your code formatted you want to constantly be clicking ctrl+shift+f to ensure your code is properly formatted at all times.

Reply

Billy Korando 3 months, 3 weeks ago on Wordpress

Make a better one then and I’ll link to it.

Reply

AFN 3 months, 3 weeks ago on Wordpress

Pretty Lame List

Reply

Billy Korando 3 months, 3 weeks ago on Wordpress

Ack! Need to proof this a little more next time.

Reply

Chris Hurd 3 months, 3 weeks ago on Wordpress

item 7 shoud be alt-shift-r

Reply

fprintf 3 months, 3 weeks ago on Reddit

Very nice! I wasn't aware of the auto-complete feature and will try it next. Apparently at Stanford (I get to say that now, I guess, since I am taking the online course) we get to build a game of Hangman in CS106a, so I'll try it later! :-)

Reply

Billy Korando 3 months, 3 weeks ago on Wordpress

You’re right, thanks for catching the typo.

Reply

Brian 3 months, 3 weeks ago on Wordpress

Pretty sure that item 11 – Run a unit test is ALT-SHIFT-D (not T) followed by T. At least that’s how it is in my key bindings and I have no memory of customizing it.

Reply

© uberVU Ltd. 2010

Terms of use