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

Jens Lincke Jens.Lincke at hpi.uni-potsdam.de
Thu Nov 3 17:11:08 CET 2011

Hi, Fabian

thanks for implement the paths so that there is no searching any more.
Currently you implemented it as a list:
      Config.modulePaths // [users/, projects/]

but I thought more of it like a mapping:
Config.modulePaths // {
		users: "../users", projects: "../projects", 
		externlsite: "http://externlsite/path/to/repos",
       codeDB: "http://couchdb.lively...."}

What do you think?


On 02.11.2011, at 23:51, Fabian Bornhofen wrote:

> Hi Jens -
> On Fri, Oct 28, 2011 at 5:52 AM, Jens Lincke
> <jens.lincke at hpi.uni-potsdam.de> wrote:
>> I would also opt for extending this codebase only on a per path basis...
>> e.g. mapping "users.*" to
>> "http://lively-kernel.org/repository/webwerkstatt/users/"
>> That would make the query if something exists in one codebase or another
>> unnecessary, because we would know before loading where we have to look for
>> everything that begins with "users".
> Implemented. Paths can be specified in the Config object of a world
> (Config.modulePaths).
> Defaults are users/ and projects/ (to be found in bootstrap.js). That
> means that modules with names starting with 'users.' or 'projects.'
> will be found. There's no probing any more, no 404s, just plain
> loading.
> Please let me know if anything breaks because of that.
> Best,
> Fabian

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

More information about the lively-kernel mailing list