<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>Re: [Seaside] Question about WASelectTag class hierarchy...</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>There's traits for VW.<BR>
<BR>
Cheers!<BR>
<BR>
-Boris<BR>
(Sent from a BlackBerry)<BR>
<BR>
----- Original Message -----<BR>
From: seaside-bounces@lists.squeakfoundation.org <seaside-bounces@lists.squeakfoundation.org><BR>
To: Seaside - general discussion <seaside@lists.squeakfoundation.org><BR>
Sent: Sat Apr 28 09:03:54 2007<BR>
Subject: Re: [Seaside] Question about WASelectTag class hierarchy...<BR>
<BR>
How do you load experimental code into VisualWorks nowadays?<BR>
<BR>
Cheers<BR>
Philippe<BR>
<BR>
2007/4/28, Boris Popov <boris@deepcovelabs.com>:<BR>
><BR>
><BR>
><BR>
> Please don't do traits, we use VisualWorks and I would very much not want to<BR>
> load experimental code into our production environment. In this case I don't<BR>
> see a problem with code duplication.<BR>
><BR>
> Cheers!<BR>
><BR>
> -Boris<BR>
> (Sent from a BlackBerry)<BR>
><BR>
> ----- Original Message -----<BR>
> From: seaside-bounces@lists.squeakfoundation.org<BR>
> <seaside-bounces@lists.squeakfoundation.org><BR>
> To: Seaside - general discussion<BR>
> <seaside@lists.squeakfoundation.org><BR>
> Sent: Sat Apr 28 01:31:13 2007<BR>
> Subject: Re: [Seaside] Question about WASelectTag class hierarchy...<BR>
><BR>
> > Or, is this just a case of some missing method(s) in either<BR>
> > WACollectionTag (parent of WASelectTag) or WASelectTag that should be<BR>
> > implementing #tabindex:?<BR>
><BR>
> The problem with many attributes is that we can either put them into<BR>
> many specific tags or into the superclass of all tags. Either-way<BR>
> there are some drawbacks. If we put these attributes into many<BR>
> specific tags we have code duplication, if we put them into the<BR>
> superclass we provide an attribute that might not be available to all<BR>
> tags.<BR>
><BR>
> The answer are Traits of course, that fit very well the XHTML<BR>
> attribute modules. Since the development of Seaside is going on in 3.9<BR>
> I wonder if it would make sense to take advantage of that? If only<BR>
> Monticello would transparently load a flattened view into older<BR>
> images, I would certainly vote for going this way ...<BR>
><BR>
> Lukas<BR>
><BR>
> --<BR>
> Lukas Renggli<BR>
> <A HREF="http://www.lukas-renggli.ch">http://www.lukas-renggli.ch</A><BR>
> _______________________________________________<BR>
> Seaside mailing list<BR>
> Seaside@lists.squeakfoundation.org<BR>
> <A HREF="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</A><BR>
><BR>
> _______________________________________________<BR>
> Seaside mailing list<BR>
> Seaside@lists.squeakfoundation.org<BR>
> <A HREF="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</A><BR>
><BR>
><BR>
_______________________________________________<BR>
Seaside mailing list<BR>
Seaside@lists.squeakfoundation.org<BR>
<A HREF="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</A><BR>
</FONT>
</P>
</BODY>
</HTML>