we really need help

[stéphane ducasse]

On 11 oct. 05, at 09:56, Adrian Lienhard wrote:

> Hi,
>
> I''ve had a quick look... As I understand there are basically two  
> problems
> - MC speed
> - load order
>
> For the first, MC is very slow for big packages. I think, that what  
> Impara did with the diff MC versions was to get around this a bit,  
> maybe this could help here, maybe improving dictionariy performance  
> would help too.
> Anyway, I guess that the complexity is not linear, thus, looking at  
> the scripts in ScriptLoader does not surprise me if this is really  
> slow. Do you need _all_ packages in these scripts to be loaded at  
> once?

for me this is really important to have complete script for a  
version. Else we may have problem at the end.


> I suggest to decompose as much as possible, else working on the  
> second problem becomes very painful. Another question: why do you  
> do a merge instead of a load? I don't think its worth merging, if  
> people have their own changes they have to deal with them before  
> loading an image update (after all, that was what changesets did  
> anyway). I guess, loading would again be faster than merging.

I follow what avi and daniel suggested

> For the second problem (that's what I've been confronted concerning  
> loading traits): If the changes are not that complex (as it seems  
> to be in this case of FasterRectangelInsetBy)

I would say that it is trivial.

> it should be doable with two packages that have to be loaded one  
> after the other (thus, not using the merger of the script!). The  
> backporting feature of MC can help here to create the pre-load  
> package (backport all changes without the critical one to the  
> previous version).

I do not understand what is backporting.

> Maybe I can have a closer look in the evening. How can I get to the  
> latest working version (IIRC, MorphicSplitters loading was working)?

Yes
script 5 is working well.

Stef


>
> Adrian
>
>
>
> On Oct 10, 2005, at 9:36 PM, Marcus Denker wrote:
>
>
>>
>> Hi,
>>
>> Sadly I really have no time to work on Monticello... or even to  
>> look at
>> the current state too much. So no idea for that problem.
>>
>> For sure, we need to get the whole mess working soon.... I will  
>> try to find
>> some time, but I fear that this will need to wait till I'm settled  
>> in Santiago,
>> so maybe end of next week.
>>
>>
>>
>>> I tried to tweak a bit the script by loading first kernel-md.42.mcz
>>> take a 6693 image
>>>     - merge MC275
>>>     - scriptloader-sd.8.mcz
>>>     script 6
>>>     - but now I get an error because Debugger does not know  
>>> stepAt:in:
>>>
>>>
>>>
>>
>> This is caused by the fact that #stepAt:in: has been moved to the  
>> morphic
>> package, so just loading "kernel" will delete that method.
>>
>>      Marcus
>>
>>
>
>