[Seaside] Question about WASelectTag class hierarchy...
boris at deepcovelabs.com
Sun Apr 29 20:39:57 UTC 2007
But if they get flattened for ports anyway, does it really matter if you use them or not? In which case why bother? Wouldn't you rather auto generate all accessors from the DTD? :)
(Sent from a BlackBerry)
----- Original Message -----
From: seaside-bounces at lists.squeakfoundation.org <seaside-bounces at lists.squeakfoundation.org>
To: Seaside - general discussion <seaside at lists.squeakfoundation.org>
Sent: Sun Apr 29 13:30:46 2007
Subject: Re: [Seaside] Question about WASelectTag class hierarchy...
traits are group of methods that you can compose/reuse in classes to
avoid duplicated code.
They are just like first class method categories.
On 29 avr. 07, at 18:58, Rick Flower wrote:
> Philippe Marschall wrote:
>> Yes, because there won't be any traits anymore once they flattened.
> Did we ever come up with a suggested solution here that everyone is
> happy with? I've got no idea what traits are so I'm going to leave
> that to the rest of you. I guess for the time being I'll build an
> override of my own that allows me to get around this for now..
> I think I read that someone (Lukas?) was suggesting to get rid of
> #tabindex: in favor of #tabIndex: to better align with other multi-
> word method names -- correct?
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
Seaside mailing list
Seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside