kvid

@ggrossetie wrote: > @kvid @formatc1702 Hey! Is the `dev` branch (0.4.x) stable? To be honest, I don't know. I've not had time to check out all the new code merged...

> > (...) , but as this process has been much more time consuming than expected, this has unfortunately blocked all progress of other PRs and releases. > > Let...

Please take a look at PR #239 and try out the related branch to test if most of your suggested features will be covered. You can also comment in this...

I'm sorry, @nyq that I wasn't fully updated on the state of #239. You are right the included demo02 fails in this branch. However, @formatc1702 has joined several of his...

Hi Scott, There are 4 usage areas of pin as far as I can see: 1. Text output in diagram and BOM mainly. Does it make sense to (optionally for...

It's described in #189 that Graphviz doesn't support base64-encoded images, so we probably would need to decode them into temporary image files in the preparation phase. That will also be...

See my bottom question in https://github.com/wireviz/WireViz/pull/309#issuecomment-2095708116 where I point out that the code to be released now only lists quite old Python versions in `setup.py` and our github workflow. However,...

After thinking a bit, I now believe it's best to leave the supported Python versions unchanged for this release. #251 has already such changes, and we'll get more time testing...

Thank's for accepting most of my suggestions. Note that I pushed a small commit that you should approve or undo. I think it'll help users with old YAML files to...

@formatc1702 wrote: > v0.4 is released 🎉 Congratulations! Thank's a lot for your effort. > The next step is somehow integrating #251 into `dev`... First, we need to include all...