Entitlements user interaction designs and proof of concept

Federico Bonelli 8b0b7ce8cc all fonts so far 3 years ago
docs 3dfe51178b made icon and logo of choser 3 years ago
ui-elements 8b0b7ce8cc all fonts so far 3 years ago
Bitmap.png 3dfe51178b made icon and logo of choser 3 years ago
Entitlements-Table.png 1aa6e4a1a0 Added an entitlements table 3 years ago
Logo.png 3dfe51178b made icon and logo of choser 3 years ago
Readme.md e61662176d added Readme 3 years ago
diff.xml 562381249b clean up lines 3 years ago
entitlements.html 1552e1a94a clean up outline 3 years ago
entitlements.org 1552e1a94a clean up outline 3 years ago
primitives.sketch ef3b3b8ff6 minor changes 3 years ago
processing.js 5b11b5e802 initial color function 3 years ago



The docs directory contains high level concept designs in pdf format describing the overall ideas and design metaphors underpinning the interactive proof of concept.

Interactive proof of concept

The proof of concept is developed as a set of code blocks using (spac)emacs org-mode, in the file entitlements.org. You can open and read the entitlements.org file in any text editor, but for the best readability and code blocks support you will need org-mode.

The file 'entitlements.html' is the exported html result that you can use to interact with the proof of concept in the browser.

The file diff.xml is generated during evaluation of the code blocks and contains a random set of fake wallet profile data. Because the diff.xml needs to be read at runtime, use Firefox to open the entitlements.html from the filesystem. Chrome and safari will restrict access to the xml file without a web server, and prevent the poc from rendering.

The file processing.js is a runtime library downloaded from processingjs.org;

'You write code using the Processing language, include it in your web page, and Processing.js does the rest. It's not magic, but almost.'

Modifying the prototype

Probably no need to do this, but for those who are adventurous...

emacs configuration

The code blocks are written in javascript, ruby and processing (java). So if you want to evaluate the code blocks you need to configure emacs to include these in the active babel languages;

;; active Babel languages (org-babel-do-load-languages 'org-babel-load-languages '((ruby . t) (js . t) (processing . t) (emacs-lisp . nil)))

And of course support for the programming languages themselves. In order to export to html, make sure to include the htmlize package in your configuration;

dotspacemacs-additional-packages '(htmlize)