UMLX Bugs

This is preliminary code, so there are no bugs just very annoying features.

This document is rather more of a TODO list.

Model Registry

User/Modeler Interface

The property pages should have hierarchical editing capability, e.g. drag an element up/down the folder hierarchy.

Occluded model bindings should be shown struck-out.

Drag and drop of models to bindings would be good.

API/Toolsmith Interface

The ModelResolver API needs fleshing out.

Usage of IFolder etc should be wrapped so that the code can be used standalone with just File.

A Model Registry Builder might maintain problem markers for bad model bindings.

Something might keep track of platform resource refactorings.

Is there a way of automating the nature addition. Perhaps a different technique. Perhaps an corrollory of some other nature inheriting/referencing it.

QVTr Editor

The domain replace attribute is not recorded since the QVT model has no property for it.

Quick assists should

  • do syntax suggestions
  • do meta-model element suggestions
  • do meta-model binding
  • The syntax coloring should context sensitive so as to avoid highlighting e.g. domain when used in an expression.

    Semantic validation should be incremental.

    An Outline View would be good.

    QVTr execution

    The QVTrelation to QVTcore transformation needs debugging.

    A QVTcore to perhaps ATL transformation needs writing.

    UMLX

    The earlier GEF-based code needs resurrecting in a GMF environment.