Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » Papyrus » Some Papyrus questions
Some Papyrus questions [message #469071] Mon, 19 January 2009 09:46 Go to next message
Erlend Stav is currently offline Erlend StavFriend
Messages: 2
Registered: July 2009
Junior Member
Dear Papyrus team,

I am writing to you because I am a participant in the EU IST project
MUSIC, http://www.ist-music.eu/

In the MUSIC project we are developing middleware and model driven tools
for development of adaptive, context aware applications. Most of our tools
are centered around the Eclipse platform, and we use the MOFscript tool
for model to text transformation (from eCore UML2 model to Java).

All tools and middleware developed in the project are/will be released as
open source (under LGPL). However, we have so far dependended on a
commecial UML tool (Enterprise Architect) because we have not previously
found a suitable open source UML tool which covers our requirements. The
latest versions of Papyrus do however look promising, and we are currently
considering to make an attempt at remodelling our tutorial examples using
Papyrus to check that it covers all features supported in our modelling
approach and UML profile.

Before we start on this work, I do however have some questions about
Papyrus and its future development.

We already have an eCore/UML2 version of our UML profile which we use as
input for the MOFscript tool when performing transformations, and I think
this profile should be useable with Papyrus.

1. We have noticed that you are currently in the process of producing a
new version of Papyrus under the Eclipse MDT project. From the wiki, it
seems that this version is a major new version, and that currently it do
not contain all the diagram editors. Our approach currently depend on the
Class diagram, the Composite Structure diagram, and the Deployment
diagram. Would you recommend that we start now modelling with the 1.11
version of Papyrus, or do you foresee major changes which would mean that
we have to recreate the models once you release the version under Eclipse
MDT?

2. When is the first relase version of Papyrus under the Eclipse MDT
project expected?

3. Is it possible in the current / future version of Papyrus to easily
create custom versions of diagrams which would support our profile /
modelling approach better? What we would like to do is to e.g. restict the
palette of modelling elements for the custom versions of the diagrams
(e.g. specialized from Class and Composite diagrams) so that the palette
would show only the modelling elements which are applicable when following
our approach, and preferably include stereotyped versions of these
elements in the palette.

4. Is it possible, and if so, how difficult is it to create other kind of
extensions to diagram editors? Extensions that might be of interrest to us
is e.g. being able to intercept the creation of new model elements in a
diagram by opening a new dialog to fill in extra information and/or to
create a other model elements and substructions along with the new
element.


Best regards,

Erlend Stav
Re: Some Papyrus questions [message #469226 is a reply to message #469071] Thu, 22 January 2009 15:39 Go to previous messageGo to next message
Sebastien Gerard is currently offline Sebastien GerardFriend
Messages: 121
Registered: July 2009
Senior Member
Hi Erlend,

see below my answers.

Reagrds,

S
Re: Some Papyrus questions [message #469244 is a reply to message #469226] Thu, 22 January 2009 17:11 Go to previous message
Sebastien Gerard is currently offline Sebastien GerardFriend
Messages: 121
Registered: July 2009
Senior Member
A small complement w.r.t. the point 4 that Yann Tanguy has provided to me:

The extension point, ModelHelper, from Papyrus v1.X enables to overload the
mechanism associated to a button (tool) of a palette for a given diagram
editor.

According to Yann, it is quite simple to do, even if it is not totally
java-less ( ;-), there is not a lot of code to write, and it will mainly
reuse by inheritance. The main drawbacks of this approach is finally the
same as for Palette: currenlmty in Papyrus 1.x, we can add tools (buttons)
to a given palette but not hide or delete. However, it seems that this
should at least satisfy your requirements. Moreover, maybe you can also
improve this part and send us a patch that we will be pleased to integrate
in Papyrus.

Regards... S
Re: Some Papyrus questions [message #581427 is a reply to message #469071] Thu, 22 January 2009 15:39 Go to previous message
Sebastien Gerard is currently offline Sebastien GerardFriend
Messages: 121
Registered: July 2009
Senior Member
Hi Erlend,

see below my answers.

Reagrds,

S
Re: Some Papyrus questions [message #581463 is a reply to message #469226] Thu, 22 January 2009 17:11 Go to previous message
Sebastien Gerard is currently offline Sebastien GerardFriend
Messages: 121
Registered: July 2009
Senior Member
A small complement w.r.t. the point 4 that Yann Tanguy has provided to me:

The extension point, ModelHelper, from Papyrus v1.X enables to overload the
mechanism associated to a button (tool) of a palette for a given diagram
editor.

According to Yann, it is quite simple to do, even if it is not totally
java-less ( ;-), there is not a lot of code to write, and it will mainly
reuse by inheritance. The main drawbacks of this approach is finally the
same as for Palette: currenlmty in Papyrus 1.x, we can add tools (buttons)
to a given palette but not hide or delete. However, it seems that this
should at least satisfy your requirements. Moreover, maybe you can also
improve this part and send us a patch that we will be pleased to integrate
in Papyrus.

Regards... S
Previous Topic:How to Attach a Port to a Component in the Graphical editor?
Next Topic:Sequence diagram with Papyrus
Goto Forum:
  


Current Time: Fri Aug 14 05:02:21 GMT 2020

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

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

Back to the top