kvid

@formatc1702 wrote: > I have resumed work on the refactoring after a longer period of inactivity. and I would like to propose a course of action to get the bulk...

I've not yet had time to test all new code, but I list here a few issues I've noticed so far: - The code building examples still use the `.bom.tsv`...

My argument related to this issue in https://github.com/formatc1702/WireViz/pull/94#issuecomment-659995911 > Personally, I'm actively using the input files together with the output files (those that don't depend on the Graphviz version) for...

Responce from @formatc1702 in https://github.com/formatc1702/WireViz/issues/100#issuecomment-660604620 > Regarding the output files: > > I agree doing diffs for regression testing is a good idea. > > Probably the biggest annoyance is...

The YAML input below test all color codes currently defined in `_color_hex` and `COLOR_CODES`. Until bugfix #145 is accepted, the error message `Unknown color specified` is repeated 40 times. ```yaml...

I suggest including YAML input examples from #138 as regression tests.

You are right, the automatic conversion between AWG and mm² is not perfect. The current AWG to mm² conversion does indeed deviate from some other conversion tables, but see my...

I'm currently testing some draft code that will be able to read YAML input like this: ```yaml X1: pincount: 4 box: color: WH bgcolor: BK fontcolor: IV fontname: times fontsize:...

By moving the `title` dict into `box` and likewise into all the option dicts with color/font attributes, it becomes easier to specify common `title` attributes.

I suggest we consider accepting something like this refined syntax: ```py options: bordercolor: WH bgcolor: BK fontcolor: IV fontname: times fontsize: 16 connector: bgcolor: RD title: fontsize: 18 cable: bgcolor:...