[Seaside] Question about WASelectTag class hierarchy...
boris at deepcovelabs.com
Sat Apr 28 15:45:22 UTC 2007
Please don't do traits, we use VisualWorks and I would very much not want to load experimental code into our production environment. In this case I don't see a problem with code duplication.
(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: Sat Apr 28 01:31:13 2007
Subject: Re: [Seaside] Question about WASelectTag class hierarchy...
> Or, is this just a case of some missing method(s) in either
> WACollectionTag (parent of WASelectTag) or WASelectTag that should be
> implementing #tabindex:?
The problem with many attributes is that we can either put them into
many specific tags or into the superclass of all tags. Either-way
there are some drawbacks. If we put these attributes into many
specific tags we have code duplication, if we put them into the
superclass we provide an attribute that might not be available to all
The answer are Traits of course, that fit very well the XHTML
attribute modules. Since the development of Seaside is going on in 3.9
I wonder if it would make sense to take advantage of that? If only
Monticello would transparently load a flattened view into older
images, I would certainly vote for going this way ...
Seaside mailing list
Seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside