Bugzilla – Full Text Bug Listing
| Summary: | [Export] Export to HTML website | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Raphael Faudou <raphael.faudou> |
| Component: | Core | Assignee: | Project Inbox <mdt-papyrus-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | arthur.daussy, benoit.maggi, c.eeckhout, cletavernier, faure.tristan, johan, klaas.gadeyne, kristof.berx, papyrus-bugs, pierre.gaufillet, raphael.faudou, ronan.barrett |
| Version: | 0.10.2 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | nwadsl | ||
|
Description
Raphael Faudou
I agree this would be very useful. At the moment we have to export each diagram individually and get no report or website. Has there been any progress on this HTML-export issue lately? Exporting diagrams with shapes to pdf does not work well. I can add some more details of the use-cases we see now: 1) HTML Report export - Here it would be good to have a report so that users who are not technical can see the models in a structured way without needing to install/launch Papyrus. This is a usual feature of modelling tools. 2) RTF/PDF Export - This is needed as often reviews are done on models and their documentation. Reviewers need to be able to add comments directly to the model/diagrams without changing the model. Also another use-case here is that often a snapshot of the model is needed to be stored in a document management system. 3) Presentation Export - Here the diagrams should be exportable so they can be used in presentations. Ideally each diagram element should be independently group/ungroupable so the diagram can be tweaked. The elements must also be scalable so zooming can be performed in some presentation tool without loss of quality. Perhaps the model diagram in papyrus could be cut & pastable into a presentation tool directly. When exporting diagrams each diagram get exported to its individal file. Exporting to jpeg works pretty well, but exporting to pdf does not. Scalable images can be achieved by exporting to SVG, but if the diagrams contain SVG shapes this export does not work well either. Another use case: 4) Our network architects have asked for diagrams to be exported straight to powerpoint, where elements in the diagram becomes separate objects on the slide. This could be useful when there is a need to make adjustments to the diagram before/while presenting it, perhaps advicing how the model should be updated. For UC #3 Cut & Paste from Papyrus to Powerpoint is possible today. The images (.png) are scalable but not ungroupable (assuming a diagram export with many elements). Exporting as a website is also very relevant to us in order to ease user access. As Papyrus supports the linking of diagrams over hyperlinks, this should be supported as well. The graphical export functions are often not generating the correct content if the diagram is not opened in the viewer (colours are gone). When a fresh copy is made of a diagram and the related names are renamed, the original diagram is generated when exporting to a graphical format. It requires restarting Papyrus in order to have this solved. > The graphical export functions are often not generating the correct content if the diagram is not opened in the viewer (colours are gone).
This has been fixed at least on Mars
(In reply to Raphael Faudou from comment #0) > It should be very useful to give the user ability to export the model (and > diagrams) as a web site. This fucntionality is available in all commercial > tools and in TOPCASED and is well appreciated as it gives access to the > model for people who do not have Papyrus installed. > Solution: migrate the code from TOPCASED. Hi Raphael, Do you know if the source code of topcased is still available somewhere? (In reply to Klaas Gadeyne from comment #8) > (In reply to Raphael Faudou from comment #0) > > It should be very useful to give the user ability to export the model (and > > diagrams) as a web site. This fucntionality is available in all commercial > > tools and in TOPCASED and is well appreciated as it gives access to the > > model for people who do not have Papyrus installed. > > Solution: migrate the code from TOPCASED. > > Hi Raphael, > Do you know if the source code of topcased is still available somewhere? Hi Klaas, Topcased sources have been backed up by Pierre Gaufillet I believe. @Pierre, do you confirm that? New Gerrit change created: https://git.eclipse.org/r/70755 I close the bug as duplicated. For what it worth, Topcased source may be found here: https://github.com/bmaggi/Topcased (I used the latest version I had) *** This bug has been marked as a duplicate of bug 518310 *** |