41–50 of 124 posts
This is the type of thing I want to use AI for. Beautiful tool, but this looks daunting.
I've used ChatGPT to generate chart wireframes in Mermaid. Basically 'create a mermaid chart for the whole year'. Not exactly the same as data viz, but it worked for my use case, and cut out a heap of stuffing around and googling.
Penrose looks great. Beautiful diagrams and readable code. What are some other text-driven diagramming languages / tools? I know of: https://mermaid.js.org/ https://graphviz.org/ https://flowchart.fun/
This is the type of thing I want to use AI for. Beautiful tool, but this looks daunting.
I've used ChatGPT to generate chart wireframes in Mermaid. Basically 'create a mermaid chart for the whole year'. Not exactly the same as data viz, but it worked for my use case, and cut out a heap of stuffing around and googling.
I have always found "diagrams as code" tools to be limiting. There will be that scenario where the generated diagram is not what you expected. The flexibility you get by using code is outweighed by these limiting scenarios. I switched to Mermaid.js but ended up switching back to normal diagramming tools because of these limitations.
- The second half of the 900 line style file is commented out code. Ugh. Should I be learning from examples or reviewing code when I read this?
- The end if the style file define/replaces coordinates which are not defined in the substance file. Why? Isn't it the point that a substance file has all the data? All coordinates and whatnot?
Overall, it does look cool. I like the idea of distinct substance/style/domain files. I probably won't give it a spin until it looks rock solid from a distance.
[1]: https://penrose.cs.cmu.edu/try/?examples=walk-on-spheres/Sig...
Penrose looks great. Beautiful diagrams and readable code. What are some other text-driven diagramming languages / tools? I know of: https://mermaid.js.org/ https://graphviz.org/ https://flowchart.fun/
I have always found "diagrams as code" tools to be limiting. There will be that scenario where the generated diagram is not what you expected. The flexibility you get by using code is outweighed by these limiting scenarios. I switched to Mermaid.js but ended up switching back to normal diagramming tools because of these limitations.
Some reasons on why we still use them: (1) They're source-control friendly. And (2) in some cases, we could generate them directly from code. We deal with a lot of state machines on embedded devices, and whenever management asks for "documentation", we run a transformer script that consumes the source code and spits out state diagrams that would placate them.
I have always found "diagrams as code" tools to be limiting. There will be that scenario where the generated diagram is not what you expected. The flexibility you get by using code is outweighed by these limiting scenarios. I switched to Mermaid.js but ended up switching back to normal diagramming tools because of these limitations.