Code source wiki de Confluence bridge for Gliffy
Modifié par Admin le 16/10/2025 - 23:33
Afficher les derniers auteurs
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{include reference="Confluence.Macros.DiagramMacros" /}} | ||
| 2 | |||
| 3 | {{velocity}} | ||
| 4 | #checkDiagramAppInstall() | ||
| 5 | {{/velocity}} | ||
| 6 | |||
| 7 | = Description = | ||
| 8 | |||
| 9 | This is a Confluence bridge for the Gliffy macro. By default, the macro displays the preview of the diagram. The user can edit it by converting it to a proper [[XWiki diagram>>https://extensions.xwiki.org/xwiki/bin/view/Extension/Diagram%20Application]], always having the option to go back to the preview of the original diagram. | ||
| 10 | |||
| 11 | = Parameters = | ||
| 12 | |||
| 13 | |=Parameter|=Description | ||
| 14 | |**name**|The diagram identifier. It should be the **name of the attachment** storing the Gliffy diagram data. (% style="color: red"%)It should not have a filename extension(%%). The Gliffy diagram exports consist in attachments added to the parent page. For example, for a diagram called //MyGliffyDiagram//, there will be two attachments on the parent page: //MyGliffyDiagram.png// (the filename with a ".png" extension) representing the preview of the diagram and //MyGliffyDiagram// (with **no filename extention**) representing the diagram data. | ||
| 15 | |||
| 16 | {{info}} | ||
| 17 | The other parameters coming from Confluence are ignored by this bridge. | ||
| 18 | {{/info}} | ||
| 19 | |||
| 20 | = Example of usage = | ||
| 21 | |||
| 22 | The syntax of the macro using the diagram called "MyGliffyDiagram" is the following: | ||
| 23 | |||
| 24 | {{code}} | ||
| 25 | {{confluence_gliffy name="MyGliffyDiagram" /}} | ||
| 26 | {{/code}} | ||
| 27 | |||
| 28 | The result is the following: | ||
| 29 | |||
| 30 | {{confluence_gliffy name="MyGliffyDiagram" /}} |