FastSilver is the new QuickSilver for Eclipse

Being inspiered by QuickSilver (totaly awesome software, basically a Mac without it is pretty much useless), I wrote a small plugin for Eclipse providing similiar functionality. For those who don’t know QuickSilver, it allows you to start applications or trigger commands using nothing but your keyboard. So why would I want this within my Eclipse, you may ask. Simply to save the time it would take you to grab your mouse and use the menu. FastSilver basically takes all the commands available within Eclipse and makes them available using one single keystroke which is Cmd-6 per default. This binding can be changed in the settings.

Again the code is available thru SVN, or if you’re solely interested in the binaries, here is the update site. For both (Update Site and SVN) the username and password are guest. Screenshots and eye-candy will follow as soon as my WordPress installation works fine again.
Update: my upload works again, so here are the screenshots. The first one shows FastSilver in action:


The second one below shows the preferences dialog where you can change the keybindings to trigger FastSilver:

Today Eclipse RAP blew me away

Ok, I know the killer argument for Eclipse RAP is that using this framework one can achieve up to like 95% code reuse (yep, 95%). These days I’m developing an Eclipse RAP based application, which I tried to convert to an Eclipse RCP based one. All in all it took me 7 minutes to do so. I mean, hello, 7 minutes … that’s like no time. Transforming a full blown web application into a rich client in a glimpse of a second is just awsome.
Alright, I already hear the naysayers: “That surely wasn’t a pretty sophisticated application”. And indeed it wasn’t, BUT the steps necessary to do this transformation were pretty straight forward:

  1. Checkout the application plugins from SCM
  2. Resolve unresolved dependencies (basically remove the RAP dependencies and add those of plain Eclipse)
  3. Change the SessionSingleton to a “normal” singleton
  4. Replace the EntryPoint with a default RCP application implementation

That’s basically it. All in all this was a pretty amazing experience which let’s me almost forgett the minor hassles I had with RAP (like text boxes doing what they want when being in a higher latency network – see #242379).

Fork me on GitHub