Mariano's PhD was on this - as mentioned it to me a few weeks ago. This was one of the reasons for building fuel - to enable this sort of thing on top - and he proved it worked.
Dimitrus - the idea is to I have a small core that loads quick and then less used elements can be paged in when needed (but maybe that's what you're saying too).
I disagree that Pharo desperately needs image assembly tools. It's quite specialised - and we have some core tools to work with, and minimal images to start from.
While I'd love more - finishing off what we already have in play (e.g. Got, bloc, Calypso ...) would seem more urgent.
Tim
Sent from my iPhone
I still dont know what opening has to do with transmitting, even when you do it remotely , a socket / websocket connection should be all you need. For me transmitting the entire image would be necessary only in the case you want to install it remotely and that remote location has no immediate access to the installation.
I understand that to mean effectively that you are "opening" the image across the net - so eventually you need to whole image transmitted, but you don't have to wait for the whole thing before you start running it.
cheers -ben