vAtelier | Main / Synthesis

To do

specify the goal
- The goal is to get more value out of my existing PIM thanks to webVR, relying on the knowledge gained thanks only to the demos done before.

2.1. list and organize the assets

unify the demos (path, inclusion, etc)
- use redirection in lighttpd conf to keep it neat
including way to keep them up to date cf tooling/ (~1h)
- ~~translate from Python and Bash to NodeJS~~ not a priority
improve the pseudo JSON wiki file to better include linked pages
- cf spherenew.html with modified Python script, does not support backlink though
- fundamental for proper graph traversal
- cf http://blog.xkoder.com/2008/07/10/javascript-associative-arrays-demystified/

2.2. list the added value of each demo in regard of the defined goal

Demo	Specificities	Added value
sphere.html	spherical layout	ModifiedScene = sphericalLayout(listOfPages);
MyDemo/	dynamically listing content
graph.html/graph.js	gaze picking using composite objects (forced by vreticle.js limitation)
edits.html/edits.js	good example of tweening and using the STLloader
futurui.html/futurui.js	good example of gaze with tangible interaction, composite arguable complex geometry
generate/	using a template demo
TheWalk/	textured skybox
ZeldaInRivierenhof (GiftPreparation)	mainly HUD and pseudo collisions
WatchInterface/	controller, can be used for HUD toggle and feedback
websockets-discovery vr.html	multi user, can be used for shared attention
GroupAsSphere.html	listing by group of pages, navigate from N pages to 1 page
PageAsRoom.html	arguably navigating back to a calling demo
race.html/race.js	grouping objects

2.3. list the usages sorted by priority (expected ROI)

focus on the added value compared with the existing PIM
- distraction free moment in time and space, perfect focus
- infinite wall size (still limited by vision system)
- infinite number of spatial organisation and re-organisations
- granular unaltered attention analytics
decide on a starting point with a starting view e.g. last edited page, all pages, etc
Wiki/3DVisualization
initial goal on Reddit
CognitiveEnvironments/

match usages (2.3) with assets (2.1) with collected useful bits of code (2.1)
- focus only on one with matching!
move non priorities (stroked out e.g. ~~translate to NodeJS~~) to a secondary session
- anything that wasn't matched
clean install process
1. get and use the latest version the boilerplate
  - bower install webvr-boilerplate
2. use http://requirejs.org instead of scripts
- overall not that efficient so will do a clean directory to clone when needed
  - with key includes and commented code to activate/de-activate key components (e.g. tweening, reticle, etc)
verify UX with Zsuzsanna, 20milliseconds and others
1. Keeping in mind LessonsLearned
verify PIM functions with stux and others
redefine the process based on external feedback

moved stroked out items here
moved everything that didn't get done during the session here
keep log of gazes (short, long) for statistics
- e.g. bring forward items with longer gazes on previous sessions than others
- not the "evil" version
improve my understand of Javascript
- e.g. https://frontendmasters.com/courses/advanced-javascript/
page edition
shared attention must be visualized
- e.g. 2 persons long gaze on a page
update PebblePIM interface
- use on tap + direction left -> move next, direction right, move back)
the neater the interfaces (or libs) the more fun and productive the session
- declare proper constructor with function or events for each demo reused

Prepare a WatchPeopleCode session announced for Saturday 19/12/2015 following the previous one.