kvid

I'm sorry that I've been offline and not available for contributing for many weeks. As I wrote earlier, I do like this idea, but unfortunately I've not had time to...

See also https://github.com/wireviz/WireViz/issues/225#issuecomment-951164193 where @formatc1702 strongly considers consolidating the optional `style` attribute into `category` that already exists for both connectors and cables. Maybe this issue is an extra argument for...

@martinrieder wrote: > I like the idea of consolidating. If connector `type:` would not already be in use, I would suggest to use this instead of `category:` for both cables...

Maybe just stick with `category` for now? It's perfectly legal to be member of more than one category if needed.

@RobinMaub - Thank's for reporting this unexpected behaviour. Can you provide a dump from your command shell screen, showing commands you try and their output? Have your tried installing it...

@ThomasDus wrote: > any chance to install as a beginner? Have you tried the recommended instructions? https://github.com/wireviz/WireViz/blob/master/docs/README.md#installation

@akikinho wrote: > [...] > * How do I display the splice name? In addition to the details @martinrieder asks you about, it will also help providing an example YAML...

I suggest using e.g. SVG to enable high-quality scaling when needed. Maybe see how these projects store logos: - https://github.com/simple-icons/simple-icons - https://github.com/gilbarbara/logos

I agree with most arguments by @tobiasfalk that a simple logo is better. It should IMHO be easily recognizable also when shown as small icons, e.g. in Windows. Of the...

@martinrieder wrote: > [...] > That brings up the question: does the logo need to include the WireViz text? IMHO - no, because that is unrealistic to recognize for small...