MPS plugin for IntelliJ IDEA

MPS 2.5 can be run as a plugin for IntelliJ IDEA enabling MPS-based DSLs to be used directly in a Java IDE and so interoperate tightly with the Java code. Custom languages can be exported from MPS as IDEA plugins as well. IntelliJ IDEA became another platform for MPS-based DSLs use, besides standalone Java applications and MPS itself.

There are several aspects of integrating MPS into IntelliJ IDEA:

Dependencies analyzer

The Dependencies Analyzer can report dependencies among modules or models. It can be called from the main menu or from the popup menu of modules/models:

          

The interactive report, shown in a panel at the bottom, allows the user to view usages of modules by other modules. The panel on the right side displays modules and models dependent on the module selected in the left-hand side list.

Module Dependencies Tool

The Module Dependencies Tool allows the user to overview all the dependencies and used languages of a module or a set of modules, to detect potential cyclic dependencies as well as to see detailed paths that form the dependencies. The tool can be invoked from the project pane when one or more modules are selected.


Module Dependency Tool shows all transitive dependencies of the modules in the left panel. Optionally it can also display all directly or indirectly used languages. It is possible to expand any dependency node and get all dependencies of the expanded node as children. These will again be transitive dependencies, but this time for the expanded node.

Select one or more of the dependency nodes in the left panel. The right panel will show paths to each of the selected modules from its "parent" module. You can see a brief explanation of each relation between modules in the right tree. The types of dependencies can be one of: depends on, uses language, exports runtime, uses devkit, etc. For convinience the name of the target dependent module is shown in bold.

There are two types of dependency paths: Dependency and Used Language. When you select a module in the Used Language folder in the left tree, the right tree shows only the dependency paths that introduce the used language relation for the given module. To show "ordinary" dependencies on a language module, you should select it outside of the Used Languages folder (e.g. the jetbrains.mps.lang.core language in the picture below). It is also possible to select multiple nodes (e.g. the same language dependency both inside and outside of the Used Language folder). In that case you get a union of results for both paths.

If you want to track not only "visible" but also runtime dependencies you should check "runtime" option in toolbar. Only runtime dependencies are marked with "(runtime)" comment in the left tree.

By default dependency paths are shown in "from the shortest to longest" order. But there are still paths that are not shown: paths with the same tail part as one of the already shown path. It is still possible to see all such paths in the right tree with the "Show all paths" option. Only starting (distinct) part of path is shown, symbols "... -->" mean that there is continueation of the path already shown in the tree; you can follow path by double clicking its last element.
Modules participating in dependency cycles are shown in red color in the left tree. It is possible to see paths in cycle by selecting module dependency equal to parent or for convinience by using popup menu: 

For some types of dependencies it is possible to show usages or safe delete with popup menu. For "depends on" (dependency without re-export) Dependencies Analyzer will be invoked on Show Usages.

Changes in Refactoring language

UI for getting refactoring parameters now is removed from refactoring language. Now choosers for parameters are not called, it is not allowed to show UI in init (e.g. ask and ask boolean), keystroke has no effect. All this functionality should be moved to an action correspondent to the refactoring.

The following constructs added to the refactoring language:

It is necessary to manually migrate user refactorings. Migration consists of

Suppressing errors

It is possible to suppress errors in editor (and in model checker) now.

If node is instance of a concept which implements ISuppressErrors interface, then all errors in this node and it's children won't be shown. For example comments in baseLanguage implement ISupressErrors.

It is also possible to define child roles, where errors should be suppressed, by overriding interface boolean method suppress(node<> child).

Also if node has attribute of concept implementing ISuppressErrors, errors in such node will be suppressed too.

There is default implementation of ISuppressErrors node attribute. It can be applied only to nodes that are instances of ICanSuppressErrors.

Here is an example of using this attribute and corresponding intention:

There is an error in editor:

 

BaseLanguage Statement imlpements ICanSuppressErrors, so user can apply highlighted intention here:

Now the error isn't highlighted, but there is a cross icon in the left pane. SuppressErrorsAttribute can be removed either by pressing on that cross or by applying corresponding intention

Extensions support

Extensions provide a possibility to extend certain aspects of a solution or a language, which are not covered by the standard language aspects and the plugin mechanisms.

Support for extensions exists in

Quick howto

  1. Create an extension point
  2. Create one or more extensions
  3. Both must be in the plugin model
    1. Each extension must provide a get method, returning an object
    2. Each extension may opt to receive activate/deactivate notifications
    3. An extension may declare fields, just like class

Extension language

The language jetbrains.mps.lang.extension declares concepts necessary for building extensions.

Extension point

ExtensionPoint concept represents an extension point. The extension object type must be specified as a parameter.

Extension

Extension concept is used to create a concrete extension.

Accessing extension point

An extension point can be accessed by reference using extension point expression.

Accessing extension objects

An extension point includes a way to access all objects provided by its extensions.

Objects returned by the extensions have transient nature: they may become obsolete as soon as a module reloading event happens. It is not recommended to e.g. cache these objects, instead is it better to get a fresh copy each time.

Java API

public interface Extension<T> {

  String getExtensionPointId ();

  T get ();

  void activate ();

  void deactivate ();
}

public class ExtensionPoint<T> {

  public ExtensionPoint (String id, Class<T> type) { ... }

  public Class<T> getType () { ... }

  public Iterable<Extension<T>> getExtensions () { ... }

  public Iterable<T> getObjects () { ... }

  public String getNamespace () { ... }

  public String getId () { ... }

}

Extension points and extensions are managed by the ExtensionRegistry core component.

Saving Transient Models Status In The Status Bar

A button in the status bar allows to enable and disable saving transient models with one click.

If transient nodels saving is enabled, this button shows a notification popup when generation starts.

Popup can be disabled in Settings -> IDE Settings -> Notifications -> Saving Transient Models Is On.

New XML language

Custom persistence for MPS models

Make process improvements

Editor improvements

Generator improvements

Collections language improvements

Build language redesigned

New Scopes

MPS.Classpath was split into: MPS.Core, MPS.Editor, MPS.Platform and MPS.Workbench

Migration

Version control

More reliable merge conflict handling

...

Distribution