-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature specification content on the website #5
Comments
Upstream issues:
|
I wonder if we should directly incorporate PlantUML into site generation rather than relying on PNG files? |
Sure, could be another plugin. This one is convenient in that if you switch to another diagram generator it won’t break project sites downstream, and that it takes any PNGs, not just a UML spec.
… On 25 Nov 2018, at 8:32 PM, Ronald Tse ***@***.***> wrote:
I wonder if we should directly incorporate PlantUML into site generation rather than relying on PNG files?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Yes indeed. Maybe that is desirable. Let's hold off PlantUML for now. |
Yeah seems pragmatic to hold off PlantUML for now since handling its dependencies (or containerizing the whole thing) complicates things. Adding the Metanorma engine next, there’re some challenges there too. PNG illustration engine to fix #34 is working at the moment, pending deployment: http://www.metanorma.com/specs/metanorma-model-gb/ |
BTW it is easy to build Metanorma documents now using Travis, you can see the Travis CI file here https://github.com/riboseinc/ogc-tcpnp. So it should be really easy to have a Jekyll plugin that renders Metanorma. |
To build PlantUML sources into SVG, rather than rely on images being part of model repo, it should be possible to call these methods: https://github.com/nus/gitbucket-plantuml-plugin/blob/master/src/main/scala/com/yotaichino/gitbucket/plugins/plantuml/PlantUMLUtils.scala#L12 |
You can consider the |
No description provided.
The text was updated successfully, but these errors were encountered: