Document when blankCanvas calls its argument

[nomeata]

It took me a bit of experimenting and help in #77 to figure out that:

• blankCanvas executes its argument (say run) the moment the user opens the browser windows,
• opening a second browser window will execute a new, independent instance of run
• closing a window browser does not stop the instance
• reloading hence starts a new instance (useful after the window changed size), but the previous keeps running.

So if one is creating animations and reloads the page a few times, many instances are running in parallel.

Is the above correct? Could it be added to the docs of blankCanvas?

Also, why is it not possible to kill an instance after the browser window has been closed/reloaded?

[andygill]

This is a good summary. We'll add something to the docs.

There is no way for the blank canvas process to know that the client has disconnected. But we can look into adding something to comet that will give this ability. Also, there is a websockets version, that should be looked at - the close will be easier to detect.

[nomeata]

Ok, moved the killing to #80, to keep the issues on single topics.