I have not seen a sample with double row connectors.

Can Pinout work on boards like this one ?
https://github.com/infphyny/FpgaRiscV/blob/main/data/Deca/Deca.svg

When exporting there is following differences of text not center aligned inside labels in the SVG version whereas PNG version left is Ok. Any clues?

These are a few random thoughts I had while working with 0.0.9, not sure how useful they are, so take them as you will, 0.0.9 is great as-is anyways! :)

Feels a bit weird to have YAML and the py files, in the main branch the data is in py and just the style stuff is in CSS, that makes sense to me. It also feels weird that half of the legend info (i.e. position) is in py but then width and radius are in YAML. I guess my confusion comes from the fact that the YAML mixes two types of information: styles (colors, fonts, etc.) and data (tag names).

It feels a bit weird that the tags info is spread between YAML and py, I get that the categories param for add_legend is optional and only useful if you want to hide some tags, but if you want to add a new tag, you have to do it in two places. Maybe it would be better to add a visible property to the tags in YAML, have them be true by default s you only set false for the ones you want to hide.

I wish I could provide colors as #112233 hex values for the tags :D

I was surprised to find out that the labels don't adjust their width to fit the whole text they contain, but I do understand it might be hard to calculate that dynamically with custom fonts, weights, and all that. Not a big deal.

It would be great to be able to provide background AND text colors for tags as I did in my fork. Some colors don't work as well with black text, but some do.

Can't wait to be able to add custom text in random places!

• the stuff I did in my work: parallelogram labels, a bullet at the end of the leaderline, hiding leaderlines between labels, having all the leaderlines be one color, and injecting raw svg code

Thanks!

I had somewhat of a difficult time getting started with my first board. The issue was a repeated edit file, run pinout, reload image process as I tried to position pinout items on my image with a trial-and-error process. I wrote a little script to automate the first two (then manually refresh the browser):

#!/usr/bin/env bash

while  [ 1 -eq 1 ]; do 
  inotifywait -e modify styles.css pinout_ulx3s.py data.py
  echo "Change! $(date)"
  rm pinout_ulx3s.svg
  python3 -m pinout.manager --export pinout_ulx3s pinout_ulx3s.svg
done

Perhaps this would be useful to others... but I'm also wondering if better documentation on the positioning parameters would help? What do you think of taking the quickstart data file, and having it notated in an image with all the respective data file <x,y> coordinates as defined in the respective data file?

Enable users to provide config settings in their own config module. This will allow better styling portability between diagrams. Potentially useful where entire config requires amendment/swapping - eg. where unit measurements are changed from px to mm, cm or in.

AND ...Update all modules to refer to revised config

Explore possibilities for extracting data direct from a kicad_pcb file. Options/ideas:

• Create pinout KiCad footprint library for documenting label coordinates and content
• Add "pinout-data" to existing footprint instances (modules) as an "fp_text" entry
• Extract and draw CutLines and nominated components

Related Note: pcbdraw looks promising as a source for PCB images - as suggested by others. Windows (my dev env) is not well supported by current KiCad release and consequently I've not tried it out yet.

As commented in Twitter (https://twitter.com/dcuartielles/status/1396565190007824385) there are some SVGs of Arduino boards available in Fritzing sources/packages: https://github.com/fritzing/fritzing-parts/tree/develop/svg/core/breadboard. Some other are available in the Arduino documentation site, but not all of the boards provide "Fritzing Files". See, for instance, https://docs.arduino.cc/hardware/nano-every and https://docs.arduino.cc/hardware/nano.

I was about to try using one of those with pinout, but the quick start is not working for me:

# git clone https://github.com/j0ono0/pinout
# cd pinout
# PYTHONPATH=$(pwd) python -m pinout.file_manager --duplicate quick_start
Traceback (most recent call last):
  File "C:/msys64/mingw64/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:/msys64/mingw64/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "T:\pinout/pinout/file_manager.py", line 3, in <module>
    import pkg_resources
ModuleNotFoundError: No module named 'pkg_resources'

tried to follow instructions. "Open a command line in the location you plan to work and enter the following: py -m pinout.file_manager --duplicate quick_start"

I do not know how to fix this or what is complaining

$ py -m pinout.file_manager --duplicate quick_start

/usr/bin/py:16: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated since Python 3.3, and in 3.9 it will stop working (not working in 3.8.6!) from collections import Iterable usage: py [-x] [-l] [-c PRE_CMD] [-C POST_CMD] [-V] [-h] [expression] py: error: unrecognized arguments: -m --duplicate quick_start

$ python --version Python 3.8.6

current method of documenting pin-labels is (possibly) unnecessary verbose where labels share many common geometry features. Review and amend method of label configuration.

Enable easier method of inserting custom components into a label if possible. ...or a method of 'assembling' labels from user defined elements

key ideal outcomes:

• custom label body
• custom leaderline

annotations sample labels a micro usb-c --don't think this exists! hardware board 'microcontroller' has an unlikely pin-count - add more pins to match a popular component.

Add a method to get started quickly on a project as an alternative to the quick_start files (which are more oriented as a tutorial of the basics). Focus on 'best practice' file structure and a recommended starting point for a new project.

Enable users to input dimensions in physical units.

Might be desirable because aspects of the diagram are intrinsically measured in physical/defined scales: PCBs are created according to physical dimensions Diagrams are likely to be printed out on standardized paper sizes (and at dpi higher than screen dpi)

title block content is an obvious source of content that might be useful in a pinout diagram - Providing access to the title block will remove need for doubling up on content input.

Create a pinout template example that can be used for similar boards. Use the Tomu family as an example.: https://tomu.im/

Project goals:

• Source data from spreadsheet(s)
• Maximise automation