Is there a yaml or json dialect for general purposes graphviz?
I see wireviz is defined using yaml and builds on graphviz. I’ve always wanted to do more with graphviz but reluctant to use the [dot language][0] graphviz uses by default.
Yeah after doing more research I’m leaning towards just writing dot. It does look nice.
Still, from a programmatic standpoint is there JSON equivalent? If wanted to build something like WireViz I would think that would be the most strait forward approach. I know there are lots of libs that compose it with mixes classes but I rather just build json objects...
This is super cool! Pinouts and wire colors are only part of a harness, though. Other things I care about:
Branch lengths and locations, where individual connectors branch off the main trunk of the harness.
Terminal types, because a single connector sometimes has different terminals per pin position, or per wire type, or other requirements.
Custom wire colors and gauges; multiconductor cables aren't always all the same gauge.
Inline splices (these may be implementable as a special case of a connector where most wires just pass through and just a few join on one "pin"?).
Is there a WYSIWYG or live-updating editor so you can see the result as you edit the markup? I understand why it's written that way, but it'd be a lot of work to translate certain harnesses to be expressed that way.
When I edit graphviz, I usually watch my source file(s) with reflex [1] to re-generate the output image, and use an image viewer with auto-reloading support like sxiv [2]. Works really well for me!
I don't think I've ever seen diagrams like these from GraphViz. I've spent the last couple of days trying to structure some complicated data for it to format to nicely, and I can't make it sing or dance nearly as well.
This is cool. Working on a small project with lots of sensors and associated amps/adcs/etc the wiring quickly gets out of control if you're just using breadboards. This will help keep things documented and surface the actual layout to help build dedicated connectors/cables.
Could this also incorporate a library of common connector designs, to be included in the generated documents? Often it can be difficult to work out the numbering when they're very small on the real connectors.
It would be of tremendous help if you could also use it for optical fiber buffers. Does anyone know if it's possible, if it's on the roadmap or if there's another FOSS tool that can do this? Thanks.
this is excellent, next time I'm at my amusement park job working on the analog PBX system, I will definitely use this in order to document the punch Downs and other wire cable runs from the analog phones to the voice gateways.
If you are looking for feature requests :)
I had a quick look at the code, looks nice and clean, I might have a go at one of the easier ones (like labels) a bit liater this week.edit: formatting