• M-x command execution
• C-u universal-argument
• Emacs style selection
• Emacs style search and query/replace
• A kill ring for deleted text
• Balanced expression (s-expression) commands
• Split editor windows via keystrokes
• Rectangle commands
• Named registers and both global and buffer-local mark rings
• Tags search (without tags)
• Transposition of characters, words, lines and s-expressions
• Line and character commands
• Space and blank line handling
• Simple text manipulation commands
• End-of-line comment operations

A plugin offering support for the Erlang language (http://www.erlang.org), the concurrency-oriented language developed by Ericsson (to be downloaded separately).
The plugin offers:
* editor with syntax highlighting
* integrated builder
* integrated debugger
* console access to underlying Erlang node
* live expressions
* code completion
* documentation view (for the standard libraries)
and more, with even more to come really soon!

At first glance, you might answer: nothing. Indeed, the information needed to complete the source code is primarily in the developer's brain. Yet we present a code completion system that is able to predict the code you *will* write in the near future. To a certain extent ;)

Eclipse users know code completion. When writing source code, a widget can propose you a list of code snippets to be inserted in the current source file. For instance, when writing Java software with Eclipse, pressing Ctrl+Space gives you all the methods callable on an instance x according to its declared type. This feature really increase the speed of writing code, especially when the results are filtered by the first characters of the method name.

However, we all noticed that the Eclipse code assist proposals are always polluted by a bunch of irrelevant or rarely used methods. For instance every proposal contains all 10 methods of "java.lang.Object" (for instance equals, notify or wait). But when using an application class, say an SWT Button, it is more likely to call Button.setText() rather than Object.notify(). However, the Eclipse code completion system sorts the recommendations alphabetically, which means that Button.setText() can be found far below notify() even if it would be much more likely than any other method call.

To make things more complicated: Did you notice that the public interface of SWT Button consists of more the 120 methods? Finding the appropriate methods in such a long list of proposals is sometimes really complicated and especially unexperienced developers run frequently into trouble here. Consequently, learning how to use a framework like SWT is much more complicated than it needs to be (in our opinion :) ).

Because of these issues we started a new Eclipse project which aims to build an intelligent code recommender system which (i) seamless integrates into the look-and-feel of Eclipse' Code Assist, and (ii) predicts only those method calls that are likely to be used by a developer in his current (code) situation. Now, we have finalized our first prototype of such a code recommender engine cabable to predict method calls for instances of the Eclipse SWT & Eclipse JFace framework, i.e., objects like SWT Buttons, Labels, Texts etc. as well JFace Wizards, WizardPages, PreferencePages, and many more.

Visit the project home for screencasts and screenshots showing the Eclipse Code Recommender in action!

Update