[Seaside] Gemstone / Magritte

Dale Henrichs dale.henrichs at gemstone.com
Tue Aug 7 16:10:26 UTC 2007

James is correct that in many cases you can override methods with no ill 
effects, but in the case of the class-side #description method we'd have 
to make some changes in the base GemStone code to avoid problems 
(Monticello also uses #description and would get confused if 
#description were overridden).

At this point, I would say you count on us changing the infrastructure 
to eliminate the problem.


Philippe Marschall wrote:

>2007/8/7, James Foster <Smalltalk at jgfoster.net>:
>> Philippe Marschall wrote:
>> 2007/8/7, i p <cappadonza at hotmail.com>:
>> Hey i'm currently building an app using the Magritte framework in squeak.
>>eventually i want to use Gemstone for persitance. Any know how easy or
>>difficult it would be to migrate it Gemstone
>> Magritte's #description might conflict with Gemstone.
>> A number of additional features have been added to GemStone/S in order to
>>make migration from Squeak as easy as possible. For example, GS/S now
>>supports the underscore character for assignment. More importantly (for
>>Philippe's concern), each VM may load its own base class overrides and
>>additions. Thus, if some class has a #description method whose behavior is
>>different from the base image, you may load a Monticello package that
>>provides the new behavior. Given that Magritte is already available on two
>>dialects (Squeak and VisualWorks), it seems that porting it to GS/S would
>>not be a major difficulty. Given that GS/S can import from Monticello, it
>>ought to be reasonably easy to find out.
>Magritte creates a #description method in Object on the instance and
>on the class side.
>Seaside mailing list
>Seaside at lists.squeakfoundation.org

More information about the Seaside mailing list