[Seaside] Re: Using traits in Squeak / Seaside - Advice sought
stephane.ducasse at free.fr
Sat Sep 29 07:12:53 UTC 2007
But philippe none of the "bugs" you mentioned is a runtime problem.
At runtime traits do not exist.
Damien worked 5 months full time with traits and everything worked well.
So using traits is the only way to make them real. I will try to
allocate some times, investigating the problems.
The tools are improving too but with no user then people doing them
On 17 sept. 07, at 09:15, Philippe Marschall wrote:
> 2007/9/17, Adrian Lienhard <adi at netstyle.ch>:
>> On Sep 15, 2007, at 08:29 , Philippe Marschall wrote:
>>> Besides the tool issues there are other issues as well. There is
>>> somewhere a bug in ClassBuilder and every trait in the image ends up
>>> with each user twice.
>> That's wrong. New traits don't have multiple users. There are
>> existing traits in the image that have multiple users. They must have
>> got there during the 3.9 process. How that happened has not been
>> found out (as Philippe noted, its potentially a bug in the
>> ClassBuilder). As said earlier, rehashing those sets gets rid of the
>>> Also copy class doesn't work correctly for
>> The problem here is that also methods from traits are copied, but
>> like the bug above, its not a show stopper.
>>> It's likely that there are more bugs like this.
>> Right, but we woun't find them if we wait using traits.
> It's just the question whether you want to be the one who spots them
> in your production project and wait for a fix.
>> In my
>> oppinion, the implementation of traits is stable enough for real use.
>> I mean, part of the Squeak kernel is implemented with traits...
>> Rather a limiting factor is UI support. Although various pleople have
>> been working traits aware tools and extensions, there is missing a
>> coherent and maintained package.
>> Seaside mailing list
>> Seaside at lists.squeakfoundation.org
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
More information about the seaside