Posted by & filed under JavaScript, Uncategorized.

I was awaiting it for some time, until yesterday. It is amazing easy to play with hardware with espruino. It is easy to transfer my daily web workflow onto hardware. Still lots of thing to learn, hence I feel the the learning curve of Espruino is a very rewarding one ;-). See below for my first very small tinkering project with the Espruino Pico.

Controlling servo with distance sensor



var servo = require("servo").connect(B7);

var sensor = require("HC-SR04").connect(B3,B4,function(dist) {
  //module output in cm
  if(dist <= 20){
    servo.move(0.5, 500);
  if(dist >= 30){
    servo.move(1, 500);
setInterval(function() {
  //send pulse
}, 500);

As you can see the code is very compact. The possibility to console.log sensor reading in the console is priceless!

Posted by & filed under books, web developing.

  • Author: Stephen Wendel
  • publisher: O’Reilly Media ( No Starch Press )
  • pages: 400


Designing for behavior written by Steve Wendel, is an excellent book guiding developers and entrepreneurs, managers in making behavior changing apps or webapps that really work.

The fact that the book takes a, practical approach based on academic literature and personal experiences of the author makes it valuable. Many of the experiences comes from his dayjob, Working as a Pricipal Scientist at HelloWallet, nevertheless most of the examples in the book are taken form a daily live perspective.

Decision process

The book gave me a clear insight and made me conscious about my and others brain and its decision process. And of course which steps should be taken to build an “habit” changing app. And more importantly how the app should tested, refined and reevaluated.

The book never leaves the main “brain decision flow”. The CREATE funnel

  • Cue: The user needs to think about something related to your product
  • Reaction: The mind reacts is the thought appealing enough to do something with it or does the user dislike the thought.
  • Evaluation. How much effort will the effort take and will I be rewarded
  • Ability. The person must actually be able to act some actions might not be possible driving a car for example, or doesn’t like to run in the rain when a fitness bracelet gives a notification
  • Time pressure. The user must have the time, or be pressurized enough to drop the current tasks or occupation.

This flow returns throughout the book and makes it sure that you never forget that there is a long process/ action sequence necessary before the user, will download your app. And if the app is downloaded, the sames CREATE sequence is necessary for the user to use your app to change behavior every time.

The book also makes it clear that most apps and webapps still have a difficulty to keep the main focus on the main task the app is for. This is a known lesson but forgotten easily through the lifetime of an app / webapp

One minor issue with the book is the localized content, for example using America’s pension/retirement fund 401k to illustrate principles. This makes it harder to understand for non americans.


Overall I surely can recommend this book, especially for developers who like to build ideas before they have given ideas a proper thought or dicussed them with others. Myself included 😉

The books product page

Posted by & filed under CSS, html, web developing.

Get the source at Github

I struggled with SVG, creating an early protoype of a mobile webapp. I wanted to create an interesting background for the webapp. It needs to be resolution independent and scalable without quality loss, SVG seems the best choice because of the vectors.

My initial thought was to make a 9-slice attempt for SVG. However since the app should be used with a phone in portrait orientation and I felt that repeating parts of the background would not be sufficient for final app. Therefore stretching should be full isze and strechable.


First I created an illustrator file with the symbol sprayer to create a framelike graphic, I exported it as svg with the default setting with “Save for web”. You can see the example below.

Background in illustrator for SVG export

Secondly make sure the svg element has the folowing style:

	position: absolute;
	width: 100%;
	height: 100%;

The trick is to make sure that the width and height of the input SVG in pixels matches the width and height of the viewbox, and that the start corner matches you desired result. Viewing the examples makes it more clear.


example : desired results

SVG properties

As you can see Illustrator defaults the viewbox as desired. Is moves the mask (viewbox) to the position 166.646, 114.09 of the dimension of the available vector art in the drawing.

	 viewBox="166.646 114.09 720 1280"

example : undesired result now it shows all the artwork

SVG properties

In this example the viewbox contains all the available vectors in the illustrator file.

	 viewBox="0 0 994 1517"


The examples and the illustrator file can be downloaded from Github


Posted by & filed under 3D, JavaScript, web developing.

Get the source at Github

For a while I wanted to experiment with audio visualisation in the browser, with the new functionality in Chrome. My graduation project concerned the other way around, namely the sonification of the dom of any webpage. To create this demo I mainly used, some html5rocks info


Check the “chrome only” demo

WebGl audio visualisation

Parts explained

The workhorse of the visualisation is the “webkitAudioContext” currently available in Chrome. With the webkitAudioContext it is possible to create an audio analysis. The following snippet is the setup for the analysis .

     // create the analyser
     var context = new webkitAudioContext();
     var analyser = context.createAnalyser();

    function onLoad(e) {
                var source = context.createMediaElementSource(audio);
     window.addEventListener('load', onLoad, false);

The rafCallback function is where the visualisation happens, the data of the audio is stored in an bytearray every available frame. For this visualisation I only used 15 ‘frequency’ bars to keep the animation smooth, for real purposes you should use the whole spectrum.

     // bind the audio data to the web gl cubes
     function rafCallback(time) {

                var freqByteData = new Uint8Array(analyser.frequencyBinCount);

                for (var j = 0; j < MAX_BAR; j++) {
                    var magnitude = freqByteData[j];
                    var delta = magnitude / 100;
                    cubes[j].position.y = cubesPos[j] + delta * 0.25;
                    cubes[j].scale.y = delta;
                    // categorize color on amplitude
                    var color =  0xf5a711;                
                    if( delta > 0 && delta < 1 ){
                       color = 0xf5a711;
                    }else if( delta > 1 && delta < 2 ){
                        color = 0xf55c11;
                        color = 0xcd0505;
                    cubes[j].material.color.setHex( color );

Feel free to use and abuse the source

Posted by & filed under CSS, JavaScript, web developing.

For some time I wanted to improve my front-end workflow. The search for an optimized workflow almost made me switch to mac, and I am still considering the switch. It seems to me that the windows front-end developing environment lacks serious momentum compared to the progress being made on linux and osx.

However now onto the good stuff. I had a few goals for my new workflow; LESS / SASS, auto refresh function, file minification and optional device checking. All this in combination with a proper IDE. At first I gave a shot at Yeoman, the installation with Chocolatey went perfect, however Yeoman itself gave some windows related errors. I am sure Yeoman should work fine, but I like to have my stack divided in several software sections.

The first goal was getting autoreload for the browser. For windows there are several options, all with there own pros and cons.

  • First there is “web essentials” an extension for visual studio, these make it possible to reload the css only. This could be a use full start if your company restricts you to use visual studio for front-end development.
  • Netbeans 7.3 with live html, this is an easy way to get a lot of functionality. However the beta version had difficulties to detect changes made by external compilers. For example css files compiled by the winless less compiler were not detected by the live html functionality. Netbeans live html has the advantage that it works on all file locations, a local server isn’t required.
  • Livereload browserplugin, i use this plugin in combination with sublime text 2. This solution works perfect, combined with some LESS plugins for sublime the less files compile automatically and the updated css file updates the livereload plugin.
  • At last there are a lot of scheduled refresh options, these refresh the browser every on predefined time. I think these options work but are not a very “clean” solution for the problem.

I’m more than happy that I have renewed my workflow, especially “Sublime text” is an instant saver, although it is lacking some deeper IDE functions, like recognizing functions from other files ( If there are some plugin to solve this please share them ). But overall Sublime is an amazing fast and “clean to the eye and mind” editor.

My current stack is as follows; sublime coupled with some less formatting plugins. Less compiling is done with WinLess. Livereload in chrome is coupled with sublime and chrome is optionally connected to devices with Adobe Edge Inspect.
Coding now feels like typing a letter, focused on the code, instantaneous feedback, brilliant 😉

At least until I need to merge the code back into visual studio and TFS, and of course next year there will definitely be new shiny toys.