[lively-kernel] Code reorganization in Webwerkstatt - please check your js files

Jens Lincke jens.lincke at hpi.uni-potsdam.de
Thu Oct 27 11:18:00 CEST 2011

Hi, Lauritz 

works for most pages. How do we deal with non kernel code additions in the wiki. Code in users or project directories such as

Should we require them differently such as we did with the modules from the CodeDB? In the meantime I will move the modules in question below the kernel/ dir.
Kernel is therefore a bad name, because the kernel is under "lively" and we would not call the rest kernel, or would we?


On 27.10.2011, at 07:58, Lauritz Thamsen wrote:

> Hi.
> As announced yesterday, we reorganized Webwerkstatt a bit.
> Please let us know if you experience any problems regarding loading or saving.
> Best,
> Lauritz
> On Oct 25, 2011, at 5:10 PM, Fabian Bornhofen wrote:
>> Hi -
>> as mentioned earlier, we want to simplify code distribution.
>> As a first step, we are going to reorganize some files in Webwerkstatt and move the core code from /repository/webwerkstatt to /repository/webwerkstatt/kernel.
>> To keep your worlds running, we will run a script on all xhtml files in Webwerkstatt that changes the path to bootstrap.js. For most worlds, you will not notice any difference. If you have never written a Lively JavaScript module on your own,   then most probably you do not need take any action.
>> However, if any of your worlds have dependencies on other js files (e.g. js files in your home folder), please check references to these paths. Config.codeBase will be /repository/webwerkstatt/kernel instead of /repository/webwerkstatt. Paths relative to Config.codeBase therefore should be fixed (typically with another '../' at the beginning).
>> We want to apply and commit our changes to Webwerkstatt on early Thursday morning (Oct 27, 1 a.m. CEST or Oct 26 4 p.m. Pacific Time).
>> Please contact Lauritz or me if you have any questions or if you need assistance.
>> Rationale:
>> We want to create a repository of the minimum set of files that is needed for running the Lively Kernel. This could be hosted on Github, Launchpad, or elsewhere. By centralizing these files in Webwerkstatt (which is effectively our upstream repository right now), it will be possible to check them out as a Subversion submodule that can be kept in sync with other version control systems.
>> Regards,
>> Fabian
>> _______________________________________________
>> lively-kernel mailing list
>> lively-kernel at hpi.uni-potsdam.de
>> http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
> _______________________________________________
> lively-kernel mailing list
> lively-kernel at hpi.uni-potsdam.de
> http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hpi.uni-potsdam.de/archive/lively-kernel/attachments/20111027/c1fc77f3/attachment.html>

More information about the lively-kernel mailing list