|Re: Mylyn Intent and Papyrus [message #1220025 is a reply to message #1219966]
||Mon, 09 December 2013 08:47
Intent is meant to work nativelly with any EMF model, and for any kind
of artifact (Java code, Manifest files, bugzilla issues...) as long as
an EMF-bridge allowing to represent this artifact as an EMF model has
As papyrus diagrams are standard EMF models, you should be able to
reference them inside Intent documents without additional work. To
reference a diagram inside your Intent documentation :
- create a Modeling Unit and reference your Papyrus diagram @M @ref
"<URI of your PapyrusDiagram>" M@
- OR drag and drop your papyrus diagram from projet explorer to your
Intent Editor (this should work by default).
Once your diagram gets referenced:
- any time you will make a change on this diagram Intent will raise a
synchronization issue on the little documentation parts referencing the
diagram you changed, so that you can quickly update the outdated
- using Ctrl+click (or F3) in the Intent editor will allow you to
navigate from doc to diagrams.
Notice that you can do exactly the same for the semantic models
corresponding to each diagram.
That being said, for a nice integration between Intent and Papyrus, we
should also provide a custom Export for Papyrus diagrams, so that when
exporting an Intent document (in HTML, PDF...) referencing Papyrus
diagrams, each diagram reference is exported as an image of the diagram.
As the generators used by Intent are written with Acceleo, we should be
able to use Acceleo extensibility mechanism (Templates override) to
customize this precise behavior.
I hope I answered your question, do not hesitate and spam me with other
questions if I didn't :)
Le 07/12/2013 15:33, Tomas Sandkvist a écrit :
> I have just stumbled over Mylyn Intent and I wonder if this can be used
> for creating documentation from Papyrus diagrams or in some other clever
> way can be used similar to GenDoc in Topcased?
> Tomas Sandkvist
Powered by FUDForum
. Page generated in 0.02163 seconds