che_flush; } } } ?> Technical Diary :: Eclipse

Eclipse

Eclipse Tips From Hardcore Developer!

How come I have missed this one so long?

Things worth of trying are:

  • Working with different workspaces;
  • Using working sets;
  • Using larger font;
  • Using Fast view and in-place view to give all space to EDITOR;
  • Key bindings;

Eclipse

Comments (0)

Permalink

Eclipse: tips and tricks

eclipse -vmargs -Xmx512M

  • Configure Eclipse to Use a JDK, not a JRE. Via Ben Pryor.

Window -> Preference -> Java -> Installed JREs

and make sure that the default (checked) JRE points to your JDK installation

  • Use Multiple Workspaces Effectively. Via Ben Pryor.

eclipse -data c:\myworkspace -showlocation

The -data parameter directs Eclipse to use the “c:\myworkspace” directory on the local machine as the workspace directory. The -showlocation parameter shows the workspace location in the Eclipse title bar – very helpful when running multiple Eclipse instances at the same time.

One note – don’t waste time setting your preferences in each workspace you create. Simply use the Import and Export options under the file menu to export preference from one workspace you’ve already set up into new workspaces you create.

  • Avoid tab indentation when editing source code:

Windows -> Preferences -> Java -> Code Style -> Format

Click Edit… button in the right panel

Change the tab policy to “Spaces only” in the Indentation tab

After that you can do a re-format (Ctrl + Shift + Spaces) of all the source code to change all tabs to spaces

Eclipse

Comments (0)

Permalink

Eclipse: shortcuts (this will be an updated list)

  • Ctrl + Shift + L: lists all shortcuts. Cool.
  • Ctrl + 1: quick fix
  • Ctrl + Space: code assist
  • Ctrl + Shift + F: formats code
  • Ctrl + Shift + O: organizes the imports
  • Ctrl + Shift + M: adds import
  • Ctrl + Shift + Space: parameter hints for method arguments
  • Ctrl + F6: prompts a list of all opened files in the editor
  • Ctrl + F7: prompts a list of views to go to and then keep hitting F7 to choose the view
  • Ctrl + F8: prompts a list of perspective and then keep hitting F8 to choose the perspective
  • F12: always returns to editor
  • Ctrl + /: toggles commenting a single line
  • F3: goes to definition
  • F4: opens type hierarchy
  • Ctrl + O: quick outline
  • Ctrl + T: quick type hierarchy
  • Ctrl + Q: goes to the last edit location
  • Ctrl + Alt + H: opens method call hierarchy
  • Ctrl + M: toggles to maximize a view
  • Ctrl + E: lists all opened files (make sure to use regular expression to choose files from the list)
  • Ctrl + Shift + T: opens type..
  • Ctrl + Shift +W: closes all open editors
  • Ctrl + Shift + F4: closes all open editors

Eclipse

Comments (0)

Permalink

Eclipse: plugins I use (this will be an list updated from time to time)

Here is a list of Eclipse plugins that I use for Eclipse 3.2

  • viPlugin: brings the vi editing to Eclipse. A must.
  • Subclipse: integrates Subversion with Eclipse.
  • VSS Plugin for Eclipse: I keep this one since VSS is still in my toolbox.
  • JadClipse: allows you use Jad to decompile a java class in Eclipse.
  • Checkstyle plugin: integrates source code analyzer Checkstyle into Eclipse.
  • Log4E: helps you to use logger easily in Java projects.
  • KeepResident: increases Eclipse performance by encouraging Windows to keep more of the Eclipse Java process in physical RAM. It works for Windows only.
  • Easy Explore: adds a windows explorer to the context menu of a file or folder in the project.
  • Cmd Here: my clone of the Easy Explore to add Command Here to the context menu of a file or folder.

Eclipse

Comments (0)

Permalink

Eclipse: Better Manage the Plugins

I just downloaded and installed Eclipse 3.2. I read this blog in the fast and always wanted to try it but did not follow it. Well, that is no longer the situation any more.Since I like to try and use different plugins (tools matter, right?), it is time for me to manage the plugins in a more efficient way. So after the installation of version 3.2, the first thing I did is to follow the good practice to better manage the plugins.

Good practice should be followed at the earliest time.

Eclipse

Comments (0)

Permalink

GETS CALL */ ?> bar(); ?>