Jens just "deployed" a solution for the SCB that is using the list
implementation :-). So it should work now - as long as it is a list (he just
told me that it can only work with a list, not an object).
So I guess his question was more a "what do you think" than "go and implement"
:-p
- Marko
On Nov 3, 2011, at 17:27 , Fabian Bornhofen wrote:
> That would probably work and make everything related to module lookup
> more explicit.
> Do you have any immediate use cases? (I'm inclined to first fix the
> SCB regression introduced by the current solution :) ).
>
> Best,
> Fabian
>
>
> On Thu, Nov 3, 2011 at 9:11 AM, Jens Lincke
> <[email protected]> wrote:
>> 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?
>> Best,
>> Jens
>> On 02.11.2011, at 23:51, Fabian Bornhofen wrote:
>>
>> Hi Jens -
>>
>> On Fri, Oct 28, 2011 at 5:52 AM, Jens Lincke
>> <[email protected]> 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
>>
>>
> _______________________________________________
> lively-kernel mailing list
> [email protected]
> http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
_______________________________________________
lively-kernel mailing list
[email protected]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
