I recall running into that problem a couple of weeks ago, but the 3.0RC
was being pushed out, so I figured I'd ignore it until things settled
down a bit. Since GemStone has implemented a subset of the Squeak
protocol for GLASS, Andreas' fix may take care of things for GLASS and
yes I expect to use the Welcome component.
Dale
Julian Fitzell wrote:
> If we do in fact have other platforms using the Welcome screen then I
> suggest we push this code onto the platform (in a Seaside package for
> now, I guess). Can the other platforms chime in with whether they
> intend to use the Welcome package?
>
> Julian
>
> On Sat, Jul 24, 2010 at 9:26 PM,
> <
[hidden email]> wrote:
>> Nick Ager uploaded a new version of Seaside-Welcome to project Seaside 3.0:
>>
http://www.squeaksource.com/Seaside30/Seaside-Welcome-NickAger.23.mcz>>
>> ==================== Summary ====================
>>
>> Name: Seaside-Welcome-NickAger.23
>> Author: NickAger
>> Time: 24 July 2010, 7:25:57 pm
>> UUID: 1404e38e-7bc1-46c2-b12b-a81f06e17cdd
>> Ancestors: Seaside-Welcome-DaleHenrichs.22
>>
>> Fixed Squeak/Pharo cross platform difference in the component creator, Pharo had a helper for component creation, Squeak requires all parameters to be specified.
>>
>>
>> _______________________________________________
>> commits mailing list
>> To unsubscribe, email
[hidden email]
>>
http://lists.seaside.st/listinfo/commits>>
> _______________________________________________
> seaside-dev mailing list
>
[hidden email]
>
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Locked
