Community
Participate
Working Groups
I've just started to try to use UMLX in earnest and need an image document to support review. There is an "Export representations as images" - excellent. But it is very very slow - disappointing. It defaults to really huge JPG - much better to use SVG or PNG as default. It supports HTML output - good But the HTML for e.g. a PNG is just a trivial wrapper for each diagram. Suggest better to generate a single perhaps index.html, with an alphabetically sorted H2 heading per diagram type and an alphabetically sorted H3 heading per diagram.
(In reply to Ed Willink from comment #0) > I've just started to try to use UMLX in earnest and need an image document > to support review. > > There is an "Export representations as images" - excellent. > > But it is very very slow - disappointing. Yes, we already had this observation from some users when we added high-definition export by default in Sirius 5.0. This was modified a little in 5.1 with preferences (a global one for the default behavior, which can be overridden on each individual export). See https://www.eclipse.org/sirius/doc/Release_Notes.html#UserVisibleChanges and https://www.eclipse.org/sirius/doc/Release_Notes.html#Changesinorg.eclipse.sirius.diagram.ui for the details). The upcoming 5.1.1 has further improvements (bug #527047) which replaces the boolean preference with a more fine-grained scale. > It defaults to really huge JPG - much better to use SVG or PNG as default. In theory, I agree. In practice we rely on the rendering pipelines provided by GMF Runtime and GEF, which uses different code paths and produce different results for each format. The JPG renderer is the one one that produces the highest fidelity (in the sense that the result looks like what you see in the actual Sirius editor). PNG has various issues, for example with gradients, and SVG has different sets of problems (with labels/fonts, edges position...). We don't have the resources to fix those, so we default to JPG with quality set to 100%. Less than ideal, but post-processing/conversion is still possible afterwards if needed. > It supports HTML output - good > > But the HTML for e.g. a PNG is just a trivial wrapper for each diagram. > Suggest better to generate a single perhaps index.html, with an > alphabetically sorted H2 heading per diagram type and an alphabetically > sorted H3 heading per diagram. We have such a generator (written in Acceleo) available in Obeo Designer Community. We never got around to actually publish it independently but it's free and it should be possible to install it by pointing at e.g. http://www.obeo.fr/download/release/designer/10.1/community/latest/repository/. The feature is fr.obeo.dsl.designer.gen.html.feature. I'm closing this as it's more observations (like the title say) than actual actionable issues. Feel free to reopen with more specific requests if needed.
(In reply to Pierre-Charles David from comment #1) > it should be possible to install it by pointing at e.g. > http://www.obeo.fr/download/release/designer/10.1/community/latest/ > repository/. The feature is fr.obeo.dsl.designer.gen.html.feature. No this is a 403. > I'm closing this as it's more observations (like the title say) than actual > actionable issues. Feel free to reopen with more specific requests if needed. You have responded helpfully to the earlier observations, however the usable index.html within Sirius at eclipse.org rather than at some inaccessible proprietary site is a reasonable enhancement request.
Here is the correct update site location containing the feature "Obeo Designer HTML Export" (id: fr.obeo.dsl.designer.gen.html.feature): http://www.obeo.fr/download/release/designer/10.1/community/latest/repository You will not have the possibility to see the content in your browser but is working in the "Install new software..." menu of Eclipse.
