Child pages
  • What's new in MPS 2.5 M1

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • ...
  • Cross-project variables support
  • Base-directory management in buildScript
  • Project dependency management

New Scopes

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

Version control

More reliable merge conflict handling

...

Distribution

  • MPS plugin structure/ability to switch on/of some parts of MPS by disabling plugins.

New Productivity Guide

Good command of the tools is undoubtedly one of the attributes of an efficient developer. MPS 2.5 can monitor your actions and give you statistics on how frequently you use its most prominent editing and refactoring capabilities. Go to Help | Productivity Guide to see how well you do:

Additionaly, we've prepared a list of a couple dozen tricks you could learn through the Tip of the Day window to become more fluent with the MPS editor:

MPS.Classpath module removed

There are four specific modules used to expose all available Java API of the platform and MPS as JavaStub models:

  • MPS.Core
  • MPS.Editor
  • MPS.Platform
  • MPS.Workbench

These modules were created as a substitution to MPS.Classpath module existing in previous version. Talking briefly, MPS.Classpath was split in those four modules to isolate core code from any dependencies on UI-/Editor-/Platform- specific APIs.

Distribution

One of the goals for MPS 2.5 release was making our platform modular. By exploring Plugins page in setting dialog it's easy to see increased number of plugin forming MPS 2.5 platform. If some plugins are not necessary for current tasks those plugins can be simply switched of increasing performance of the platform. Same trick can be used to create reduced IDE for some specific DSLs based on MPS.

Image Added

Migration

If you are already using MPS in your projects, it definitely make sense to read our migration guide with the detailed description of migration process.