-
ubervu
-
Apple iPhone
-
Nexus One
+ Add

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 ...
Showing 31 relevant reactions out of 43.
MindStalker 3 months, 1 week ago on Reddit
.NET?
Doing things behind your back for you is just stupid.
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
kopkaas2000 3 months, 1 week ago on Reddit
Too lazy to read the article. Is tip 1 "apt-get install vim"?
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
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
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
Ack! Need to proof this a little more next time.
Reply
Follow us
Twitter Facebook