You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I like very much the idea of accessing the pinout of the development boards I use at the command line so I was interested with picopins.
I tried to add some boards I am currently using and found it a little cumbersome to change data and some parts of code to create a new board pinout.
So I splitted the code in two.
one is the part that displays the pinout with little modification to what you have made. It is a class named showpins that the boards will inherit from. The major change I made is adding a loop that walk through a list of lists describing the LEDs and associated GPIOs that are on the board as it was the part that bothered me when creating new boards
the second is the definition of the board, it only contains data defining the board and an instance of the showpins class
Now, adding a new board is just modifying a string and some lists, no more code to change.
If you want, you can have a look at the code here: https://github.com/fdufnews/pinouts
Regards
The text was updated successfully, but these errors were encountered:
Hi,
I like very much the idea of accessing the pinout of the development boards I use at the command line so I was interested with picopins.
I tried to add some boards I am currently using and found it a little cumbersome to change data and some parts of code to create a new board pinout.
So I splitted the code in two.
Now, adding a new board is just modifying a string and some lists, no more code to change.
If you want, you can have a look at the code here: https://github.com/fdufnews/pinouts
Regards
The text was updated successfully, but these errors were encountered: