monk,

there are a couple of ways this can work right now.
At first I tried to make default generic self run apps loadable directly into the workspace, but due to my lack of skills I couldn't make it work.

The current method for getting custom code in is with dynamic linking (a folder/tree of .so files are scanned dynamically - like the current hildon desktop).

I also have the library in the backend able to be used by a standalone application in a manner similar to SDL (ie, allocate screen, load images, throw around, rinse repeat).

Internally, new sections of the screen come from calling a function and return a block of memory allocated as a cell, wherever that memory comes from is fine by me.

So, once I get everything cleaned up for release there are a number of possible directions and perhaps someone can figure out how to do the shared memory standard binary visible on desktop thing that I so far can't suss out.

Incidentally, it runs nicely on my laptop in a little window or fullscreen, it shocked me how nice the calendar looks there.

*i hate flu*

Hope you get better soon, lcuk.

full sequence, for Tracy