<!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>Doesn't mean much in VisualWorks and other dialects I suspect.<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: Sun Apr 29 14:00:58 2007<BR>
Subject: Re: [Seaside] Question about WASelectTag class hierarchy...<BR>
<BR>
2007/4/29, Boris Popov <boris@deepcovelabs.com>:<BR>
><BR>
><BR>
><BR>
> On the other hand if someone has html reference handy and you're looking for<BR>
> href and can't find it things might get frustrating for some. Either way,<BR>
> that's a discussion outside of the subject.<BR>
<BR>
You can still do Ctrl+shift+e on 'href'<BR>
<BR>
Cheers<BR>
Philippe<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: Sun Apr 29 13:57:06 2007<BR>
> Subject: Re: [Seaside] Question about WASelectTag class hierarchy...<BR>
><BR>
> 2007/4/29, Boris Popov <boris@deepcovelabs.com>:<BR>
> ><BR>
> ><BR>
> ><BR>
> > But if they get flattened for ports anyway, does it really matter if you<BR>
> use<BR>
> > them or not? In which case why bother?<BR>
><BR>
> This is what I'm trying to say. I can't see how it affects anybody but<BR>
> developers.<BR>
><BR>
> > Wouldn't you rather auto generate all<BR>
> > accessors from the DTD? :)<BR>
><BR>
> Sucky (C-like) attribute names like href. A lot of the methods in<BR>
> WAHtmlCanvas were actually generated.<BR>
><BR>
> Cheers<BR>
> Philippe<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: Sun Apr 29 13:30:46 2007<BR>
> > Subject: Re: [Seaside] Question about WASelectTag class hierarchy...<BR>
> ><BR>
> > traits are group of methods that you can compose/reuse in classes to<BR>
> > avoid duplicated code.<BR>
> > They are just like first class method categories.<BR>
> ><BR>
> > Stef<BR>
> ><BR>
> > On 29 avr. 07, at 18:58, Rick Flower wrote:<BR>
> ><BR>
> > > Philippe Marschall wrote:<BR>
> > >> Yes, because there won't be any traits anymore once they flattened.<BR>
> > ><BR>
> > > Did we ever come up with a suggested solution here that everyone is<BR>
> > > happy with? I've got no idea what traits are so I'm going to leave<BR>
> > > that to the rest of you. I guess for the time being I'll build an<BR>
> > > override of my own that allows me to get around this for now..<BR>
> > ><BR>
> > > I think I read that someone (Lukas?) was suggesting to get rid of<BR>
> > > #tabindex: in favor of #tabIndex: to better align with other multi-<BR>
> > > word method names -- correct?<BR>
> > ><BR>
> > > Thanks!<BR>
> > > _______________________________________________<BR>
> > > Seaside mailing list<BR>
> > > Seaside@lists.squeakfoundation.org<BR>
> > ><BR>
> ><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>
> ><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>
> > _______________________________________________<BR>
> > Seaside mailing list<BR>
> > Seaside@lists.squeakfoundation.org<BR>
> ><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>
><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>
><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>