<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi, Lauritz<div><br></div><div>I definitely think it should go into the users folder, but since you changed the codebase the users folder are out of reach </div><div>for loading moduless.... so I moved the code into the codebase again. How should we deal with multiple roots?</div><div><br></div><div>Best,</div><div>Jens</div><div><br><div><div>Am 27.10.2011 um 19:49 schrieb Lauritz Thamsen:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Jens --<div><br></div><div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>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.</div><div>Kernel is therefore a bad name, because the kernel is under "lively" and we would not call the rest kernel, or would we?</div></div></blockquote></div><div>Yes, I agree it shouldn't be 'kernel/', so we will rename it to 'core/' later in the evening (Oct 28, 1 a.m. CEST or Oct 27 4 p.m. Pacific Time). However, I am not sure that "personal modules" should be part of our core distribution. Either such code belongs into apps/, lib/ or into lively/ and should be synched across repositories or it should remain in a user's folder and shouldn't be synched across repositories. What do you think? </div><div><br></div><div>Best,</div><div>Lauritz</div><div><br><div><div>On Oct 27, 2011, at 2:18 AM, Jens Lincke wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi, Lauritz <div><br></div><div>works for most pages. How do we deal with non kernel code additions in the wiki. Code in users or project directories such as</div><div><a href="http://lively-kernel.org/repository/webwerkstatt/projects/BP2012/">http://lively-kernel.org/repository/webwerkstatt/projects/BP2012/</a></div><div><a href="http://lively-kernel.org/repository/webwerkstatt/users/ahold/">http://lively-kernel.org/repository/webwerkstatt/users/ahold/</a></div><div><br></div><div>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.</div><div>Kernel is therefore a bad name, because the kernel is under "lively" and we would not call the rest kernel, or would we?</div><div><br></div><div>Best,</div><div>Jens</div><div><br></div><div><div><div>On 27.10.2011, at 07:58, Lauritz Thamsen wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hi.<br><br>As announced yesterday, we reorganized Webwerkstatt a bit.<br><br>Please let us know if you experience any problems regarding loading or saving.<br><br>Best,<br>Lauritz<br><br><br>On Oct 25, 2011, at 5:10 PM, Fabian Bornhofen wrote:<br><br><blockquote type="cite">Hi -<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">as mentioned earlier, we want to simplify code distribution.<br></blockquote><blockquote type="cite">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.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">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.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">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).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">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).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Please contact Lauritz or me if you have any questions or if you need assistance.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Rationale:<br></blockquote><blockquote type="cite">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.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Regards,<br></blockquote><blockquote type="cite">Fabian<br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">lively-kernel mailing list<br></blockquote><blockquote type="cite"><a href="mailto:lively-kernel@hpi.uni-potsdam.de">lively-kernel@hpi.uni-potsdam.de</a><br></blockquote><blockquote type="cite"><a href="http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel">http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel</a><br></blockquote><br>_______________________________________________<br>lively-kernel mailing list<br><a href="mailto:lively-kernel@hpi.uni-potsdam.de">lively-kernel@hpi.uni-potsdam.de</a><br><a href="http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel">http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel</a><br></div></blockquote></div><br></div></div></blockquote></div><br></div></div></blockquote></div><br></div></body></html>