Can you create GraphViz's HTML-like labels in Clojure using rhizome?
So far I have found only the library tangle to support it.
Related
I need to do some research in MDA/MDD to find Open-Source-Tools which will help me to develop code-generators and transformators.
But there are only a few tools which are actually supported. Do I search in the wrong direction?
Do You know open source tools for MDA/MDD?
Greetings Dominic
I found andromda, Eclipse Modelling Framework and a few tools like plantuml, which help to create diagrams .
My plan is to read diagrams with plantuml and convert them with emf to code and the reverse way.
Telosys could be a solution to your need (https://doc.telosys.org/)
Telosys has its own DSL to define the models (based on text files with a simple grammar), see https://doc.telosys.org/dsl-model
A Telosys model can be used to generate any kind of target language (including PlantUML) but Telosys cannot parse PlantUML files, so the input model must be a Telosys model (or a database schema if you create the model from a relational DB).
I have been trying the tufte handbook style on RStudio using the skeleton.Rmd script. It works ok excepting the [#R-base] side citation that sets cursive for the rest of document probably because of bad format in reference. Other than that, it works nicely. As I am not very experienced in TeX output in Rmarkdown, I would like to know if the Tufte format is necessarily linked to LaTeX and xelatex engine, or using the ConText engine can manage it and I could use ConText engine in Quarto to generate Tufte formatted document with Tex output. I'm using Quarto with context engine to write a technical book and that option would be so nice. Thanks for help!
The tufte styles use the tufte LaTeX package; they cannot be used with ConTeXt.
There are very few (if any) predefined styles for ConTeXt, so you'd have to build this yourself. The only help I can offer is to link this ConTeXt template, which might contain a few pointers on how to build a suitable ConTeXt pandoc template.
The Dia diagram editor has a python module named dia that comes with the installation of the editor. It can be used to write plugins for the editor but I can't seem to find any documentation for it. I would like to know what classes/methods are defined in the module so I can write my plugin. The only example I was able to find was a hello world plugin which is particularly useless for understanding the module.
Are the any resources/code snippets that could be used to gather further understanding of this module? I would like to get information about diagram elements in a diagram, I'm trying to write a custom export function basically.
I am looking for a good java library to manipulate box, arrows and labels in order to dynamically create and fill diagrams like the following and render them to a png :
Another example
I can create a static template to be filled later, but I will need to dynamically create labels for every box and edges in the diagrams.
For now I have tried using batik to manipulate an svg template but creating multiline labels for the edges is proving quite complicated. The SVG way with batik seems to force me to create 1 text object for each label line with absolute positioning for each which is a real pain.
I would like to be able to define the label specifying only the text and the link they relate to, eventually some hints as to how it should be placed and let the library place them.
Any suggestions ?
If this is in a commercial scenario, the Java graph drawing library yFiles can be a good match for your requirements:
You can use a convenient API to create and style your diagram and automatically layout the diagram with lots and lots options to constrain the resulting layout to suit your needs.
Multi-line and (simple) HTML labels are supported out-of-the-box.
Also you can export to PNG (as well as other pixel based image formats) and vector graphics formats like SVG, PDF, EPS.
This can be done both in a regular Java (Swing) application as well as in a headless environment (e.g. to create images on a server and to send them to a web-based thin client dynamically).
To get a feel what can be done using that library, I suggest you take a look at the freely available graph editor application "yEd" that is based on yFiles and lets you try out the above steps in an interactive manner.
(Disclosure: I work for yWorks, but on Stackoverflow I do not represent my employer.)
I'm working on a C++ project in the field of automatics I'd like to start documenting. I'm rather decided for Doxygen. But, apart of documenting particular fields of data and drawing class-hierarchy UML-diagrams, I'd like to document several methods' functionalities with block diagrams like this one:
What are the solutions?
I'm familiar with LaTeX. I've read Doxygen has some support for LaTeX, I don't know how far this goes, though. Is it possible to use any LaTeX package within Doxygen? Which particular packages would you recommend and could you provide some simple examples as well?
I'm also open to recommendations of something different than Doxygen.
If it's only about getting the control-systems structure, variables etc. documented you can generate the diagram elsewhere (e.g. Dia, XFig or Inkscape if you want to use open source tools) and embed them into your Doxygen documentation via the image keyword from within your code:
/*!
.. Doxygen doc here..
\image html Data_Model.png "Figure 1: UML Diagram of the Data Source and Data Model Relationships"
*/
To do this you'll need to tell Doxygen in the Doxyfile file where to find the images, and place the images relative to your doxygen path (DOCROOT/images in this case):
# The IMAGE_PATH tag can be used to specify one or more files or
# directories that contain image that are included in the documentation (see
# the \image command).
IMAGE_PATH = images
Using latex extensions or other language driven graphical markups for generating graphs from within Doxygen doc does imho not justify the overhead of learning the language, getting the tool-chain configured and aligned. On the other hand if you have some tool already which is generating the graph automatically (from your code or a config file), it should be a breeze to run the tool from within a Makefile, let it generate the image and embed the image in your doxygen doc via the image keyword.