OpenFLOW – Quickly make beautiful infrastructure diagrams local to your machine
21–30 of 86 posts
Re: OpenFLOW – Quickly make beautiful infrastructure diagrams local to your machine
#22Node version? Could not get it running with 22 or 24 on linux.
Re: OpenFLOW – Quickly make beautiful infrastructure diagrams local to your machine
#23Diagrams look great - well done. Reminds me of a similar project years ago that was doing the same thing - they ultimately struggled with monetization and folded (I forget the name) -- however this one is MIT OSS, so I'm guessing that's not a key concern right now. Note that your "Built with the Isoflow library" link at the bottom to isoflow 404's to https://github.com/isoflow/isoflow
Thanks! I can't take any credit at all for the icons/design that's all Isoflow, but their community edition is designed to steer you to the pro version. No plans at all for money making, just want people to enjoy using it. Thank you for pointing out the link, I'll get on that ;)
this way i could tell the LLM that will be generating my JSON to include the following links as X and create the output JSON immediately
Re: OpenFLOW – Quickly make beautiful infrastructure diagrams local to your machine
#24This is a little tangential, but I've wondered for a while if there's a better way to visualise the composition of software systems. Often, there's not only a single way to look at one: There's a user interaction flow through components, but those components also consist of hardware; the hardware might be virtual and composed of several, spread, sub-components, or even containers. You can go down this path pretty dee…
At least for the layering + using text aspect, D2 support this: defining diagrams as multiple layers like so x -> y layers: { inside_x: { a -> b } } A fleshed out example hosted on our web service: https://app.terrastruct.com/diagrams/664641071
Re: OpenFLOW – Quickly make beautiful infrastructure diagrams local to your machine
#25This is a little tangential, but I've wondered for a while if there's a better way to visualise the composition of software systems. Often, there's not only a single way to look at one: There's a user interaction flow through components, but those components also consist of hardware; the hardware might be virtual and composed of several, spread, sub-components, or even containers. You can go down this path pretty dee…
At least for the layering + using text aspect, D2 support this: defining diagrams as multiple layers like so x -> y layers: { inside_x: { a -> b } } A fleshed out example hosted on our web service: https://app.terrastruct.com/diagrams/664641071
Re: OpenFLOW – Quickly make beautiful infrastructure diagrams local to your machine
#26Why JS world frequently uses "beautiful" or "modern" to describe its project? Often that hides something else.
Re: OpenFLOW – Quickly make beautiful infrastructure diagrams local to your machine
#27This is a little tangential, but I've wondered for a while if there's a better way to visualise the composition of software systems. Often, there's not only a single way to look at one: There's a user interaction flow through components, but those components also consist of hardware; the hardware might be virtual and composed of several, spread, sub-components, or even containers. You can go down this path pretty dee…
At least for the layering + using text aspect, D2 support this: defining diagrams as multiple layers like so x -> y layers: { inside_x: { a -> b } } A fleshed out example hosted on our web service: https://app.terrastruct.com/diagrams/664641071
Does that make sense?
Re: OpenFLOW – Quickly make beautiful infrastructure diagrams local to your machine
#28Earlier quoted context omitted.
At least for the layering + using text aspect, D2 support this: defining diagrams as multiple layers like so x -> y layers: { inside_x: { a -> b } } A fleshed out example hosted on our web service: https://app.terrastruct.com/diagrams/664641071
Terrastruct looks really nice, and kind of like a 2D version of the 3D thing I'm thinking of; if you could attach key-value properties to nodes and vertices, and had different rendering modes that made use of any of these properties to render the item differently, that would probably be pretty close. For example, a layer that displays a physical network might only consider vertices with a `kind` attribute of "physica…
a.class: backend
b.class: frontend
# hide everything
**: suspend
layers: {
backend: {
# show backend stuff
**: unsuspend {
&class: backend
}
}
}
see more here: https://d2lang.com/blog/c4/Re: OpenFLOW – Quickly make beautiful infrastructure diagrams local to your machine
#29"beautiful" here is definitely subjective. I only see a diagram and it looks like from PowerPoint presentation from the marketing team to the sales team. Why JS world frequently uses "beautiful" or "modern" to describe its project? Often that hides something else.