kvid

This look can be implemented quite easily, supporting images for both connectors and cables:  I can create a draft PR if this looks useful as a first implementation. Please...

> That seems like a great first start. Thank's. > Here's a sample diagram for a [high-density D-Sub26 connector](https://www.zaber.com/w/images/a/a0/X-MCC_3A_motor_and_sensor_connector_diagram.png) and for a [4-pin terminal block](https://www.zaber.com/w/images/6/60/X-MCC_E-Stop_Connector.jpg), unfortunately in different styles. The...

> Let's not forget the earlier comment: > > > Yes, definitely up to the user for adding the images. Maintaining a library is difficult to say the least! >...

> One important thing that's missing from the sample images discussed so far: > ⚠️ The important distinction whether one is looking at the connector from the mating side, or...

> A separate `caption` attribute is more elegant and just as practical. OK > It should be displayed in the same cell as the image, to differentiate it from the...

> There is no CSS in GraphViz, correct. > Having triple nesting of tables seems like a bit of overkill, yes :D I found a way that didn't affect the...

To support image scaling, I suggest adding these two attributes for connectors and cables: - `image_scale` specifies how an image will use any extra space available in its cell. Allowed...

Now, I've tried in Windows 10 with Python 3.9.13, and this similar installation procedure seems to work there: ```bash ver echo %COMSPEC% dot -V git clone https://github.com/formatc1702/WireViz.git clean-WireViz cd clean-WireViz/...

> The idea is to make the new syntax work in additon to the current one, which generates unknown, auto-incremented designators not exposed to the user, since that should be...

This issue seems to be related to #230.