The Sphinx 0.10.0 release is focused on some functional enhancements as well as on bug fixes.
The most prominent functional enhancements include:
Model Split Service
A capability allowing resources or model object contents to be traversed and distributed over multiple resources according to user-defined model split policies.
Access to the "ordered" attributes in metamodels and "ordered"-based sorting in Common Navigator-based views
An extended BasicExtendedMetaData implementation that allows an extra "ordered" flag to be specified for and retrieved from structural features of Ecore metamodels. Can be used as safe place to put the conceptional "ordered" information instead of the structural features' ETypedElement#ordered attribute whose setting is typcially rather driven by technical constraints.
The common navigator integration for EMF models provided by Sphinx has been extended to prevent the model objects being displayed from being automatically sorted in alphabetical order everywhere. Instead, it evaluates the extra "ordered" annotation on the underlying structural features and maintains the original order of the values in the model in case that it is set.
Metamodel and view content agnostic problem decorator for model elements
A generic label decorator for Common Navigator-based views in Sphinx that decorates all resource and model object items on tree paths containing model objects affected by validation warnings or errors with appropriate overlay icons. Does neither depend or make any assumptions on the structure of the underlying metamodel(s) nor on that of the content provider exposing the model objects and fully supports tree contents where referenced model objects are displayed as children of their referrers.
Reusable base implementation of an IURIChangeDetectorDelegate for URIs with hierarchical fragments
Makes it easy to add URI change detection support for models being persisted resources that rely on URIs with hierarchically structured fragments for representing cross-references between model objects. As a result, Sphinx can automatically analyze the changes being made on the loaded models, determine all model objects whose URIs are impacted by these changes and rewrite not only all directly changed resources upon saving but also all resoures that will need to updated because they contain cross-references to changed model elements.