Damus et Capimus

Last week's instalment of the CDO integration tech preview series for the Kepler release explored model validation in repository models. This week, we take a look at customizing the Properties View.

Papyrus offers end users a powerful model-driven solution for customization of the Properties View. This enables a convenient UI for editing model elements tailored to what's important in a specific domain, such as SysML, MARTE, or whatever you can invent yourself. In the Juno release, the models that describe the Properties View are stored in the local workspace's metadata area. Now, we bring them into the repository to share and access from any workspace.

Have a look at the video after the break for a quick (less than 10 minutes) tour.

One of the most important things we can do with our models is to validate them, testing them against general-purpose and domain-specific well-formedness rules. Last week, we saw how to reuse packages from models stored in a repository in the Papyrus Kepler release.

This week, we take a look at validating models. After all, you wouldn't want to share and re-use packages that aren't up to muster, would you? See a short demonstration video after the break.

In last week's instalment of the Papyrus Model Repository tech preview series, I showed how to create new models in a CDO repository. This week we look at reusing model content by importing packages and applying profiles from models stored in a repository.

The latest development on the cdo_kepler branch in Papyrus SVN refactors the "Import Package From Workspace" and "Apply Profile(s)" dialogs to support pluggable model import sources, including CDO repositories in addition to the Eclipse Workspace. Also, the workflow in these dialogs is stream-lined a bit and some of the code that handles profile migration is generalized to work with non-XMI resources. See the video after the break to take a tour.