Better control over flowchart shape sizes, title text for charts
See original GitHub issueI’ve been using Mermaid in Typora for a couple of months now as well on the live editor to see if there is something in Typora that is not working yet.
After taking a look at the source code for the Flow Chart shapes, one of the most vexing issues is how decisions (“questions”?) are rendered in diamonds.
Often I feel like they get too big, even when using <br>
for line breaks to wrap the text.
Part of the issue is that diamonds are drawn as diagonal squares rather than rhombuses (rhombii?)
Rendering such a shape shouldn’t be that hard, just allow the user better control over the width and height of the shape. I honestly won’t mind it that much if the text overflows outside the shape just a little bit. (Though, it might be a good idea to allow the ability to adjust the text size, which I think might already be implemented.)
Is there a way to add some width and height features for shape nodes?
I also noticed that we can create titles for pie charts, but why not for other diagrams like class charts, flow charts, etc.?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (1 by maintainers)
Top GitHub Comments
Good to know. Add it to documentation.
Now there’s just the request for better shape size controls to deal with.
While that is a resourceful idea, that is not what the elongated hexagons are used for.
This guide shows what each of the flowchart symbols are used for. And while it states that IBM (who developed the flowchart shapes) now discourages the use of the elongated hexagon since it wasn’t used that much by them, another program called Flowgorithm, presents a better use for this shape: loops.
There are a couple of shapes that Mermaid doesn’t seem to recreate that seem to be pretty important still. The symbols for documents, for starters.
(Those two shapes were not made in Flowgorithm, but they were in a flow chart that I saw in a class I’m taking.)
There are some symbols that are part of Mermaid that don’t seem to be recognized, but I think that has to do with the version of the particular Markdown editor I’m using, an issue I will need to take up with them.