Three topics of theoretical focus :
Of constraints, their usefulness and influence they exerce on design and designers of the Primer artefact
Daniel :: Hello world !
::
Initial digital primer templates.
What You hear now is just a dim reflection of what You'll hear then.
Some useful know-how for creation of Your own digital Primer.
LEFT (north, south) :: back in browser history
RIGHT (south, north) :: forward in browser history
DOWN (east, west) :: user info
UP (west, east) :: activity info
AIRWHEEL :: zoom
Hardware is Raspberry Pi, OS is Raspbian which after booting automatically logs in the user fibel whose .bashrc specifies to launch xinit whose .xinitrec specifies to run chromium
Frontend is running in chromium which loads index.html which loads all the rest.
Interaction between backend services / sensors and frontend takes place by means of websockets. Every backend service pipes it outputs into pipes located in /dev/fibel, these pipes are created by bunch of gwsocket-daemons launched at startup, config file for service2port associations is in /etc/fibel/sockets.
All necessary frontend code for dealing with sockets is in js/sockets.js
Of main properties of the Primer, motivation behind them and means how to implement them
Coded in vim (front-end: D3.js; back-end: kastalia.medienhaus) by Prof. Daniel D. Hromada (UdK / ECDF).