Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 328693 - [Usability] Papyrus shall provide support for automatic diagram creation.
Summary: [Usability] Papyrus shall provide support for automatic diagram creation.
Status: RESOLVED DUPLICATE of bug 330186
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.7.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: M5   Edit
Assignee: Yann Tanguy CLA
QA Contact:
URL:
Whiteboard: Usability
Keywords: plan
Depends on: 330186
Blocks:
  Show dependency tree
 
Reported: 2010-10-26 08:32 EDT by Sébastien Gérard CLA
Modified: 2017-06-19 06:53 EDT (History)
5 users (show)

See Also:
sebastien.gerard: indigo+


Attachments
A QVTo transformation from UML to Papyrus notation+di (6.31 KB, application/octet-stream)
2010-10-27 03:11 EDT, Nicolas Rouquette CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sébastien Gérard CLA 2010-10-26 08:32:26 EDT
Papyrus shall provide support for automatic diagram creation.
Comment 1 Nicolas Rouquette CLA 2010-10-27 03:11:05 EDT
Created attachment 181800 [details]
A QVTo transformation from UML to Papyrus notation+di

I've attached a simple example in QVTo that maps a UML model (*.uml) to a Papyrus diagram (*.notation and *.di).

Since much of the diagram support in Papyrus is generated, it would be nice if the diagram code generator could also produce QVTo java black-box helpers to faclitate the programmatic creation of Papyrus diagrams either in Java or in QVTo. This would give users more flexibility in choosing the language & strategy for programmatically creating diagrams.
Comment 2 Sébastien Gérard CLA 2011-02-18 08:24:25 EST
Solved by the tool attached to task 330186.
Comment 3 Sébastien Gérard CLA 2011-02-18 08:26:13 EST

*** This bug has been marked as a duplicate of bug 330186 ***
Comment 4 Sébastien Gérard CLA 2011-02-18 08:27:16 EST

*** This bug has been marked as a duplicate of bug 330186 ***