live-interface VS FordACP-AUX

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...

There was some previous hobbyist research into implementing the protocol which is the Ford Audio Control Protocol. You can see my summary and all sources linked here http://ansonliu.com/2017/09/ford-acp-cd-changer-emulator-aux...