We are happy to announce Kotlin Eclipse Plugin version 0.3.0. This release is loaded with new features:
- Kotlin M13 support
- Find references
- Parameter hints
- Select enclosing/next/previous element
- Override/Implement action
- Body conversion intention
- Debugger: Run to cursor
- Debugger: Step into selection
- Better performance
A very common task in daily activity of any developer is looking up references to a function, property or class all over the project. Find References in 0.3.0 searches through usages of Kotlin declarations in both Java and Kotlin code. And running Find References for a Java declaration reveals usages in Kotlin too! The same
Ctrl+Shift+G / ⇧⌘G shortcut works for both languages.
Kotlin Eclipse plugin now supports parameter hints. To look up the order of function parameters or their names and types, place the cursor inside the parentheses and press
Ctrl+Shift+Space / ⇧⌃Space to see a hint.
Select Enclosing Element
Some IDE features proved to be really addictive, and once accustomed, you will always miss them if they are not present. A good example is a Select Enclosing Element. It’s far more convenient to select “function arguments”, “statement”, “function body” or “whole class” instead of thinking where should selection begin and end.
Please note that Select Next/Previous element actions are also supported for Kotlin.
Since 0.3.0 Kotlin Eclipse plugin can help in resolving a very frequent “not implemented” error. Quick Fix menu (
Ctrl + 1 / ⌘1) has an Implement Members item that will generate all missing declarations after selection.
It’s also possible to call Override/Implement Members and select methods you want to implement as a separate action from Quick Access (
Ctrl + 3 / ⌘3).
Body Conversion Quick-Fix
Kotlin allows you to declare methods in a really short way, and now Eclipse can to convert one form to another with a quick fix (
Ctrl + 1 / ⌘1).
Several important debugger features are ready to be tried out.
Run To Line
While debugging your program it’s a very common task to skip some code and stop the execution an particular line. This is very much like a “one-time breakpoint”, but removing a breakpoint right after hitting it is tedious. This is why debuggers have Run To Line (
Ctrl + R / ⌘R) feature which is now also supported for Kotlin code.
Step Into Selection
It’s often not enough to debug in terms on lines. Imagine the situation when there’re several calls in one line and you want to skip two of them but wonder what the third function does. Instead of cycling through Step-Into, Step-Out actions it’s better to hit Step Into Selection (
Ctrl + F5 / ⌥ F5) action.
This release has a significant boost in performance of build and completion on board.
While it might seem that we choose features for release at random it’s not exactly so Actually we are gradually addressing problems we have in our project with the percentage of Kotlin code growing and pretty happy with the result.
If you have an idea what feature should be implemented next, please create an issue in our tracker.
Have a nice Kotlin in Eclipse!