live-interface VS Pinout.xyz

If you've got some nodejs, Ruby or Python projects and you want to keep them around for posterity then I recommend thinking how you can package them up so they can be safely archived. You could use docker or a virtual machine image.

In my editor project ( screncast https://github.com/samsquire/live-interface/blob/master/scre... )

In components written in Nodejs, Ruby and Python and they're all in disrepair because I failed to pin dependencies.

Also recommend taking lots of screenshots.

I created a text editor that was meant to be programmable like a spreadsheet but interactive like a IPython notebook.

There's screenshots here:

https://github.com/samsquire/liveinterface

The code is Angular 1 legacy codebase.

https://github.com/samsquire/live-interface

There's a screencast here https://github.com/samsquire/live-interface/blob/master/scre...

It's not buildable at this time due to dependencies...

At one point I tried creating what is Notion/Obsidian style system in 2013. I called it "living documents".

here's one of the last surviving screenshots of living documents version 1.

https://github.com/samsquire/interface-experiments/blob/mast...

The system accepted RDF N3 triples and it queried Jena Fuseki database to render graphs with d3. You could introduce facts into the system with the three boxes at the top. if you changed them, they would autocomplete and change the graph view. You could insert references or links into the document by typing them.

I have the code trapped in a JSBIN SQLite file. It's somewhere in here https://github.com/samsquire/jsbin It uses KnockoutJS.

Living documents v2 has a screen cast of it here https://github.com/samsquire/live-interface/blob/master/scre...

Obligatory shameless plug of https://pinout.xyz where I’ve been maintaining an interactive Raspberry Pi SBC pinout for some years, and the newer https://pico.pinout.xyz where I’ve tried to do the same for the Raspberry Pi Pico board. The latter also became a command-line pinout via the Python package “picopins”

I feel- and of course I’m biased- that if anything is worth bringing to the table for device pinouts it’s interactivity and accessibility. The latter, in particular, is lost in static images. I really leaned into this with the Pico Pinout, including everything from visual accessibility accommodations (avoiding low contrast text background colours), to markup for screen readers to the ability to turn off labels and reduce noise. I’m still unsure if I actually achieved my goal, but it’s been fun.

There is a great resource to be found at pinout.xyz that details a lot of boards and the pins they actually use.

All the LEDs have their negative pins together and go through two 1k resistors in series on their way to ground (any gpio ground pin). Then a short piece of jumper wire goes from the positive lead of each LED to it's GPIO pin number. Don't use the pin order number, use the GPIO number.

I wanted to create an accessible alternative to the official Pico pinout image, offering more complete pin details, light/dark modes, screen-readable text, and at least some capacity to focus on the peripherals you’re interested in. It’s a sister site to the now ancient Raspberry Pi pinout (https://pinout.xyz/) which started out life hosted on a Raspberry Pi.

GPIO PIN numbers - its a real pain with both board and BCM numbers (see pinout.xyz for details) without having to translate what the libraries use by default!

The pins are at top right corner here: https://pinout.xyz/ and you just connect TX to RX, RX to TX and GND to GND. On the software side you can use picocom on the builtin serial device. Not sure which though, seems to depend on the software and exact revision of your RPi.

You can see all the pins on the pin documented at https://pinout.xyz

Use pinout.xyz to see what pins are used for the SPI interface on your Pi.

You have mixed up the PIN numbers - the Pi has two sets on numbers (board and BCM) - see here for details