YUML – Easy Embeddable Diagrams
yuml.me
yuml.me
I don't think YUML is going to be my answer, though -- it's paid and doesn't seem to be a local tool, but rather a SaaS model.
This product feels like it should be a local compile-into-image workflow. But that's probably my bias for text-based declarative formats coming through. :)
It seems to me that a keyboard driven OneNote would be fantastic. I already do a lot of writing in my vim/markdown setup because folding is so useful. I just want more mindmap style control, or the ability to define my own notations. On paper I often comment or converse with ideas on the right third of the page, and I should be able to do that with a `<` denotation just like markdown does blockquote with `>`.
upper/left arrow lower/right
So e.g. you write: upperBlock <-- lowerBlock
instead of: lowerBlock --> upperBlock
This alone drasticly cuts on the amount of hidden arrows with forced directions you need to use in larger diagrams.That said, plantuml could use a more explicit way of providing layout hints. E.g. an extra declaration that some objects form a grid. Something like:
grid
Comp1 Comp2 Comp3
Comp4
Comp5 Comp6
endgridThink I know what you're saying. That said, there are many people using a command line wrapper to generate yUML diagrams as part of an automated workflow.
The paid features are more for people who want better management of diagrams.
I wish I could use YUML to make flow charts!
I've no issues with paying for a SaaS but it has to provide value and this for me doesn't.
Frankly, I think UML is a waste of time. Anything that fits in a diagram, is too trivial to document. It's the stuff that doesn't fit that matters more. And attempting to document a very complex system with UML is both pointless and painful.
Most diagrams I've seen just state the bleeding obvious. There's a thingy; it uses another thingy and extends that other thingy over there. Best case it's not a complete over simplification; worst case it tells less than half the story or it is hopelessly out of date because diagrams rot even faster than code.
IMHO the best diagrams are those on whiteboard that you wipe out after the meeting. Don't bother taking photos, nobody ever looks at those.
[1] https://assets.sysadmincasts.com/e/g/45-ansible-ping-pong.pn...
[2] https://assets.sysadmincasts.com/e/g/47-ansible-load-balance...
It's a command line tool so someone interested enough can package it up as a docker container and provide a simple wrapper script that would mostly work in-place.
ETA: I actually am on a Mac, but I've decided for other reasons that my next one won't be. As far as I'm concerned the 2015 Macbook Pro was the last of the good ones.
> Graphviz.app currently doesn’t build on OSX Mojave because of Apple API changes. It would be wonderful if someone can fix this.
https://graphviz.gitlab.io/download/
It's a general theme that Apple doesn't take compatibility very seriously but each case is annoying.
In our team (non enterprise), there's a lot of visual flow models for UX, and still some class/interaction/activity diagrams for explaining how stuff hangs together.
I've done the diagrams using the free Camunda Modeler [1], and they have an online version [2].