[Seaside-dev] About Continuation>>#invoke:

[Michael Lucas-Smith]

Likewise. We import directly from squeaksource and publish to our 
internal store and public store. So we too can compare changes using our 
regular tools. It's very convenient.

Cheers,
Michael

Dale Henrichs wrote:
> The GemStone folks are actually using Monticello directly. It is true 
> that we maintain our own version of Seaside, but we use the Monticello 
> tools for integrating changes from the Squeak version - Monticello 
> merge makes it real straightforward.
>
> If you have a Dolphin-based source code comparison tool, you might 
> consider cracking open a monticello file ... one of the components of 
> a monticello file is a fileout (chunk format) of the source...it might 
> be a bit easier to find changes that way...
>
> Dale
>
> Lukas Renggli wrote:
>
>>> You always comment the changes, if minor, between versions?
>>> If I can trust on that, I can directly modify it on my image without
>>> having to port everything again from Squeak, and only do so when
>>> changes are major.
>>>   
>>
>> I guess that is not really possible. Sometimes changes go over many
>> classes and touch many methods in subtle ways. It would be the easiest
>> if you wrote a script that you can use to regularly and automatically
>> pull in whole trunk. This is what the VisualWorks, GemStone and GST
>> guys are doing in more or less sophisticated ways ;-)
>>
>>  
>>
>>> ps: I still need to learn how to use Monticello.
>>>   
>>
>> Monticello can show you changes between two versions. Load the version
>> you originally ported. Then click on the version you want to port to.
>> Click on changes. A dialog should then show up and list all the
>> changes between these two versions.
>>
>> Cheers,
>> Lukas
>>
>>  
>>
>
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev