[lively-kernel] Code reorganization in Webwerkstatt - please check your js files
robert.krahn at gmail.com
Fri Oct 28 07:40:06 CEST 2011
Hi, Fabian --
you are absolutely right on this, getting rid of specifying manually what code to load had several advantages. On the one hand you can start Lively with little code (=kernel) which allows faster booting. With the combinedModules approach you still only require one request to load the kernel. Even browser caching plays nicely with it (we provide a combinedModuleHash that tells the browser when to reload). This increased the load time of Lively tremendously.
Also the idea of having a more or less continuously running live system works better if you can easily load code on demand and specify requirements. This is exactly what the current module system does.
On Oct 27, 2011, at 9:00 PM, Fabian Bornhofen wrote:
> What's cool about the recursive load is that in your xhtml
> files, you only need to link to bootstrap.js and it takes care of
> everything else. If you add references to all core modules to your
> worlds, you'd have to manually update these every time we add or
> remove a core module. (Well, you should not expect this to happen too
> often..) It also makes it easy to build e.g. a facebook app that
> displays worlds.
More information about the lively-kernel