Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » Papyrus » SysML modeling with Papyrus - excluding UML-only features
SysML modeling with Papyrus - excluding UML-only features [message #1032137] Tue, 02 April 2013 16:02 Go to next message
Yannick S. is currently offline Yannick S.
Messages: 15
Registered: February 2013
Junior Member
Hello, all,

we would like to use Papyrus for SysML modeling; SysML was designed to simplify UML for systems engineers and remove or hide features which looked too much software-oriented (tainted ?).

Now, our users are a bit overwhelmed when facing Papyrus and all the diagrams and features, including UML.

Is there a straightforward way (like an option somewhere in the preferences) to remove or hide everything that is not part of SysML in the menus, dialogs, properties and so on ?

Thank you very much.
Regards.
Re: SysML modeling with Papyrus - excluding UML-only features [message #1032161 is a reply to message #1032137] Tue, 02 April 2013 16:36 Go to previous messageGo to next message
Camille Letavernier is currently offline Camille Letavernier
Messages: 481
Registered: February 2011
Senior Member
Hi Yannick,


Papyrus aims at providing the tools to allow you to do that. We currently support the following:

- Palette: OK
- Properties view: OK

- "NewChild" (In the ModelExplorer): Not yet; we only have a prototype/proof of concept for that.
- Modeling Assistants ("Accelerators", in the diagram): Not yet. Planned for Kepler M7.
- Remove UML-specific diagrams/table: Not yet

Then with these tools, you should be able to tailor Papyrus to your exact needs. Papyrus does not aim at providing the final configuration for a pure-SysML modeler. It is a much more generic and configurable tool.

So, currently, you cannot do what you want. Or, more precisely, to do what you want, you'd need to provide a Papyrus-based RCP, and fork a few plug-ins to remove the contributions you want to hide (I'd say, 10-15 plug-ins to fork, and you'd mostly have to remove a few plugin.xml contributions)

In the mid-term vision of Papyrus (Luna / June 2014?), you might be able to do that without actually forking Papyrus, just providing a few new plug-ins.

But it is unlikely that Papyrus provides a native configuration for a pure-SysML modeler, neither now nor in mid-term. We really focus on the configuration tools, rather than on the configuration itself.


Regards,
Camille


Camille Letavernier
Papyrus developer
Re: SysML modeling with Papyrus - excluding UML-only features [message #1032616 is a reply to message #1032161] Wed, 03 April 2013 07:57 Go to previous messageGo to next message
Marc-Florian Wendland is currently offline Marc-Florian Wendland
Messages: 67
Registered: January 2013
Member
Camille,

are there any plans available with respect to what features are going to be
realized in the mid-term for Papyrus?

>- "NewChild" (In the ModelExplorer): Not yet; we only have a
>prototype/proof of concept for that.

Does this mean that in mid-term one would be able to switch off the default
"new child" entry?

>- Modeling Assistants ("Accelerators", in the diagram): Not yet. Planned
>for Kepler M7.

What are these Modeling Assistants? Sounds interesting (in particular
because we do have a similar concept).

What is the best way to provide you solutions for new features for tailoring
Papyrus?

Regards,
Marc-Florian

"Camille Letavernier" wrote in message
news:kjf1dj$bsg$1@xxxxxxxxe.org...

Hi Yannick,


Papyrus aims at providing the tools to allow you to do that. We currently
support the following:

- Palette: OK
- Properties view: OK

- "NewChild" (In the ModelExplorer): Not yet; we only have a prototype/proof
of concept for that.
- Modeling Assistants ("Accelerators", in the diagram): Not yet. Planned for
Kepler M7.
- Remove UML-specific diagrams/table: Not yet

Then with these tools, you should be able to tailor Papyrus to your exact
needs. Papyrus does not aim at providing the final configuration for a
pure-SysML modeler. It is a much more generic and configurable tool.

So, currently, you cannot do what you want. Or, more precisely, to do what
you want, you'd need to provide a Papyrus-based RCP, and fork a few plug-ins
to remove the contributions you want to hide (I'd say, 10-15 plug-ins to
fork, and you'd mostly have to remove a few plugin.xml contributions)

In the mid-term vision of Papyrus (Luna / June 2014?), you might be able to
do that without actually forking Papyrus, just providing a few new plug-ins.

But it is unlikely that Papyrus provides a native configuration for a
pure-SysML modeler, neither now nor in mid-term. We really focus on the
configuration tools, rather than on the configuration itself.


Regards,
Camille
Re: SysML modeling with Papyrus - excluding UML-only features [message #1032666 is a reply to message #1032616] Wed, 03 April 2013 09:17 Go to previous messageGo to next message
Camille Letavernier is currently offline Camille Letavernier
Messages: 481
Registered: February 2011
Senior Member
Hi,


Quote:
are there any plans available with respect to what features are going to be realized in the mid-term for Papyrus?


For Kepler:

http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/modeling/mdt/papyrus/project-info/plan_indigo.xml&component=Papyrus

For the next versions, we don't really have a plan yet.

Quote:
Does this mean that in mid-term one would be able to switch off the default "new child" entry?


Yes. Hopefully, for Luna (June 2014).

Quote:
What are these Modeling Assistants? Sounds interesting (in particular because we do have a similar concept).


The popup toolbar in GMF Diagrams, which is a kind of "quick palette" for the hovered element. It is currently disabled in Kepler, but works for the other versions (Indigo, Juno).

Quote:
What is the best way to provide you solutions for new features for tailoring Papyrus?


Do you mean, contributing patches and new tools to Papyrus? I guess it depends on the kind of contribution. You can provide patches directly on the Bugzilla (and notify us when we miss them). For new features, it's probably better to contact us directly by e-mail.


Regards,
Camille


Camille Letavernier
Papyrus developer
Re: SysML modeling with Papyrus - excluding UML-only features [message #1032841 is a reply to message #1032161] Wed, 03 April 2013 13:57 Go to previous messageGo to next message
Yannick S. is currently offline Yannick S.
Messages: 15
Registered: February 2013
Junior Member
Hello, Camille,

thank you for this clear statement.

We'll have a look at how to remove unwanted features.

Best regards.
Yannick.
Re: SysML modeling with Papyrus - excluding UML-only features [message #1032912 is a reply to message #1032841] Wed, 03 April 2013 15:55 Go to previous message
Ed Willink is currently offline Ed Willink
Messages: 4095
Registered: July 2009
Senior Member
Hi

If it's only visibility in the UI that worries you, there is a
tremendous amount that can be done with the org.eclipse.ui.activities
extension point (often called capabilities).

You might want to make some recommendations on clearer 'id' spelling to
make tailoring significantly easier.

Regards

Ed Willink


On 03/04/2013 14:57, Yannick S. wrote:
> Hello, Camille,
>
> thank you for this clear statement.
>
> We'll have a look at how to remove unwanted features.
>
> Best regards.
> Yannick.
Previous Topic:How to assign a value for a slot of type NFP_Duration
Next Topic:Help
Goto Forum:
  


Current Time: Thu Oct 23 19:25:32 GMT 2014

Powered by FUDForum. Page generated in 0.03359 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software