Bug 471537 - Support nsURI from target platform
Summary: Support nsURI from target platform
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Core (show other bugs)
Version: 3.0.0   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2015-07-01 03:06 EDT by Melanie Bats CLA
Modified: 2015-07-06 06:32 EDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Melanie Bats CLA 2015-07-01 03:06:31 EDT 
To develop UML Designer, I am using a target platform which contains the uml metamodel. When I try to reference the uml metamodel from the "Metamodels" tab on a representation, if the metamodel is only defined in the TP, the wizard does not proposes it as possible selection. As I am not using the live editing mode, it could be interesting, that the metamodels selection wizard provides also the nsURI coming from the target platform.
Comment 1 Cedric Brun CLA 2015-07-01 03:12:17 EDT 
We should probably have a look on how the code evolved in the EcoreEditor when support for Target Platform Ecore's was added (especially in the dialog which opens when picking "load resource") and adapt our code in the same way to get the same dialog.
Comment 2 Maxime Porhel CLA 2015-07-01 05:23:05 EDT 
See org.eclipse.emf.ecore.presentation.EcoreActionBarContributor.ExtendedLoadResourceAction


This dialog was used in the previous "metamodel" property section of the RepresentationDescription and RepresentationExtensionDescription, see: 
 . RepresentationDescriptionMetamodelPropertySection 
 . RepresentationExtensionDescriptionMetamodelPropertySection


The property sections to correct are: 
 . RepresentationDescriptionMetamodelPropertySectionSpec
 . RepresentationExtensionDescriptionMetamodelPropertySectionSpec