Bug 434957 - Separate Sirius "Modeling" views from generic Sirius mechanisms
Summary: Separate Sirius "Modeling" views from generic Sirius mechanisms
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Core (show other bugs)
Version: 1.0.0M7   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2014-05-15 08:43 EDT by Alain Bernard CLA
Modified: 2015-01-26 07:27 EST (History)
3 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 Alain Bernard CLA 2014-05-15 08:43:26 EDT 
When integrating Sirius in a RCP application, the import of "org.eclipse.sirius.ui" is required to use the specified diagrams/tables/trees. This import implies that the "Modeling perspective", "Modeling nature" and other Sirius-specific mechanisms appear in the RCP application, which may be confusing for users. 

It could be great to split the "org.eclipse.sirius.ui" plugin in two separate plugins, the first one containing the required stuff to open representations in an application, the other one containing the Sirius-specific views (for example, in a "org.eclipse.sirius.ui.ide" plugin).
Comment 1 Alex Lagarde CLA 2014-05-15 08:48:02 EDT 
Mark the issue as triaged, this is a legitimate need.

We'll have to determine what is the target milestone for this (definitely not Sirius 1.0 as we are about to release RC1).

In the meatine, you may refer to [1] to see if you can hide those views & perspectives.

[1] http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fworkbench_advext_activities.htm
Comment 2 Alain Bernard CLA 2014-05-16 02:49:33 EDT 
Thank you. The issue is not blocking as we currently are in prototyping/evaluation phase. Melanie sent me the link about activities too, I'll look at it.