[Seaside] Re: Using traits in Squeak / Seaside - Advice sought

Philippe Marschall philippe.marschall at gmail.com
Sat Sep 15 06:29:50 UTC 2007

2007/9/14, itsme213 <itsme213 at hotmail.com>:
> >> Should I use traits in my work?
> >
> > What is your work?
> A tool for software architects, in which I think I see several places where
> trait-like structuring could be useful.
> >> Know of any real deployed projects that have used traits to good effect?
> >
> > Only on a very small base, 2 or 3 traits.
> That is quite useful to know, though I was hoping otherwise.
> >> Do the tools manage the cost of all the finer-grained bits, debugging,
> >> etc?
> >
> > Debugging is not a problem. The problem is that the code browser and
> > Monticello are only 80% there, RB is not trait aware, ....
> Ah, also most useful to know. I wanted to use traits more than build up the
> tooling for it.
> >> Will using traits affect (a) possible port to VW? (b) possible use of
> >> Gemstone/S?
> >
> > You mean because they don't support traits? Yes of course.
> All in all sounds like it may not be quite ready yet. Thank you very much
> for the input..

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. Also copy class doesn't work correctly for
traits. It's likely that there are more bugs like this.


More information about the seaside mailing list