I know that Capella Studio allow to go from Project.data.vptxt → into Project.ecore. Similarily to this :
I was wondering if it was ever possible to follow the opposite path, meaning you could add an EClass in the tree editor of Porject.ecore and then having them translated into code in Project…vptxt.
I tried adding an EClass in the ecore editor, and it did not show up in the data.vptxt…
The Ecore and vptxt files are not tightly coupled so yoir modification in the Ecore will not be impacted on the vptxt automatically.
But ! There is a feature in the tooling to generate the vptxt content from an ecore file:
This feature is targeting the generation of a brand new vpdsl project, generation on an already existing project may break the existing content. I advise you to backup your existing content before doing so. Or you can generate a new vpdsl project and merge the generated content.
Great! I just tried it, but it seems to generate only the “.pvdesc” file, the following are missing for instance:
And the .data.vptext as “illustrated” in the vpdesc of the newly generated “project” seems to be containing no Classes:
Edit: I usually start working from the spec.vptext (where you can add manually all the other .vptext files), not sure how to start from a fresh .vpdesc…
I tried the “generate vptext files”:
But they are empty:
And can you get the ecore or vptext from the odesign file?