Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I find that right-clicking the project or file in the Package Explorer is the most time consuming part of this repetitive process.</p> <p>Mostly I make related changes in multiple files, then synchronize the whole project. The first step to making the whole process accelerated via hotkeys is to bind a key combination to "Synchronize with repository...". For Eclipse 3.5 on OSX, the hotkey can be bound by going to Eclipse->Preferences->General->Keys. Then search for "Synchronize" in the text filter. I bind control-s as synchronize.</p> <p>Once a hotkey is bound for Synchro... , hitting the hotkey will synchronize the file in your active editor, or the selected files in the project explorer, if the project explorer is active.</p> <p>To rapidly put focus in to the project explorer, hit, on OSX, command-F6 to cycle to the project explorer. Another way, if focus is in an editor view, is to hit cmd-alt-W (Show In...) and then select "Project Explorer" from the popup. Sorry for the OSX shortcuts. If you look in the Keys area mentioned earlier, you should be able to find the relevant hotkey for cycling views.</p> <p>So we've sped up part of the process, but it would still be nice to have a rapid way of selecting the whole project. The easiest way is a hack- just start typing the name of your project while in the project explorer. If the name isn't unique enough, prepend a 'Z' to it or something so that just they keystroke 'z' will select the whole project. Then hit your Synchro... hotkey to synch the whole project.</p> <p>Okay, so it takes quite a few hotkeys to synch the whole project, almost like playing a progression of guitar chords or doing a sweet combo in Tekken, but honestly the sequence of hotkeys can all be pushed in less than the time it takes to move your hand to the mouse. Perhaps binding a macro to the entire sequence would make it uber convenient.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload