Charles Overbeck

Moving from JBuilder 2006 to JBuilder 2007

JBuilder 2007 has almost all of the functionality that JBuilder 2006 has, plus a lot more. One of the difficult things is finding where that functionality is, because the UI is definitely different.

So I have come with a table listing the most common actions I use in my day-to-day Java programming. I personally mainly use the keyboard, so I’ve listed the keyboard shortcuts. For the more mouse-oriented of you, I’ve also listed the menu access. This is not intended to be a complete list, just the actions I commonly do. Hopefully it can help JBuilder 2006 users easily migrate to using JBuilder 2007.

Feature JBuilder 2007 JBuilder 2006, CUA Keymap Comments
Find any class in your workspace/project
  • Ctrl+Shift+T
  • Navigate | Open Type
  • Ctrl+Minus
  • Search | Find Classes…
Probably my most commonly used keystroke
Quick Fix/Error Insight
  • Ctrl+1
  • Edit | Quick Fix
  • Alt+Enter
  • Edit | CodeInsight | ErrorInsight
Now that I think about, I might use this as much as or more than the previous item.
Go to a method/field in a class
  • Ctrl+O
  • Navigate | Quick Outline
  • Ctrl+Shift+G
  • Search | Go to Class Member…
In JBuilder 2007, you can also press Ctrl+O a second time to show inherited class members. This is a neat feature not in JB2006
Open Declaration / Find Definition
  • F3
  • Open Declaration (on context menu)
  • Ctrl+Enter
  • Find Definition (on context menu)
 
Refactoring
  • Alt+Shift+T
  • Refactor
  • Ctrl+Shift+R
  • Refactor
This one invokes the context menu with all the possible refactorings.
Rename Refactoring
  • Alt+Shift+R
  • Refactor | Rename
  • Ctrl+Shift+R | Rename
  • Refactor | Rename (Field | Variable | Method | Class)
I like how you can directly go to a specific refactoring in JB2007. I also use Alt+Shift+C (change signature), Alt+Shift+I (inline), Alt+Shift+M (extract method) a lot, as well as some others.
Show JavaDoc for method/class
  • F2
  • Edit | Show Tooltip Description
  • Ctrl+Q
  • Edit | CodeInsight | Javadoc QuickHelp
 
Find References
  • Ctrl+Shift+G
  • Search | References | (Workspace | Project), or via the context menu
  • Ctrl+Shift+Enter
  • Search | Find References, or via the context menu
This does not seem as reliable in JB2007 as it was in JB2006. In JB2007 it seems to sometimes to do a text-search, and seems to turn up false matches for Java fields/methods. I haven’t quite figured out what is going on here.
Find References in file
  • Ctrl+Shift+U | I(dentifier)
  • ???
  • <none>
  • Context Menu | Find Local References
 
Run
  • Ctrl-F11
  • Run | Run…
  • F9
  • Run | Run Project
In JB2007, this runs your most recently run/debugged configuration. In JB2006, this runs your default run configuration.
Debug
  • F11
  • Run | Debug…
  • Shift+F9
  • Run | Debug Project
In JB2007, this debugs your most recently run/debugged configuration. In JB2006, this debugs your default run configuration.
Step Over (Debugger)
  • F6
  • Run | Step Over
  • F8
  • Run | Step Over
When I first started using JB2007, this and Step Into were the hardest keystrokes to learn. I kept wanting to press the JB2006 keystrokes.
Step Into (Debugger)
  • F5
  • Run | Step Into
  • F7
  • Run | Step Over
 
Quick Step Into (Debugger) (N/A)
  • Shift-F7
  • Run | Quick Step Into
I miss this one a lot from JB2006. If you are in the debugger positioned on this line:

	someMethod(param1, methodForParam2());

With Quick Step Into, you can go directly to the first line of someMethod(). With regular Step Into, you first go into methodForParam2(), then only after you return from that method, do you go to the first line of someMethod(). Of course, sometimes you want to go into methodForParam2(), but often you don’t.

Optimize Imports
  • Ctrl+Shift+O
  • Source | Organize Imports
  • Ctrl+I
  • Refactor | Optimize Imports
 
Who Changed this Line?
  1. Context Menu | Team | Show Annotation
  2. Answer yes to "Do you wish to view annotations using quick diff?".

You can then hover the mouse over the gutter to view who changed each line. Note that this is how you do it for Subversion. I don’t know how and if this functionality can be invoked for other Version Control implementations.

  • Ctrl+Shift+/
  • (Context Menu) | Who Changed this Line?
I prefer the JBuilder 2006 way of doing this a lot more — it’s just a keystroke away. Although once you have done it in JB2007, it does present a better overview.
Incremental Search
  • Ctrl+J
  • Edit | Incremental Find Next
  • Ctrl+E
  • Search | Search Incremental
I prefer the JB2006 implementation of this — the text you type in is more visible, on top of the editor. In JB2007, it is on the status bar.
Find / Replace
  • Ctrl+F
  • Edit | Find/Replace
  • Ctrl+F
  • Search | Find
Well, at least one shortcut is the same!

Charles

Posted by Charles Overbeck on December 5th, 2006 under JBuilder |



One Response to “Moving from JBuilder 2006 to JBuilder 2007”

  1. Chee Wee Chua Says:

    Nicely done Charles!

    Can we get more of these? ;o)



Server Response from: blog2.codegear.com