Re: Seaside 2.6 Example?

Hi all.

I just subclassed WAComponent and have YASPComponent with no additional
methods or i-vars. All my real components subclass YASPComponent.
I do such thing for every project by the way.
Now it is very easy for me to switch to 2.6 whatever will be default renderer.
Also I can have customized dialogs for confirm: inform: etc defining them in 
YASPComponent.

Someone just noted this technique and I used it just for a God sake :-)

Seems this method deserves to be noted on the seaside.st ?

-Dmitry.


Avi Bryant wrote:
> On Jan 25, 2006, at 12:16 PM, Rick Zaccone wrote:
>
> > Wouldn't it make more sense if WAPresenter>>rendererClass was  defined as
> >
> > WAPresenter>>rendererClass
> >     ^WARenderCanvas
> >
> > I thought that the thrust in Seaside 2.6 was to use a Canvas.  Why  is 
> > WAHtmlRenderer the default?
>
>
> For backwards compatibility.  But if people are willing to add
>
> rendererClass
>   ^ WAHtmlRenderer
>
> to all of their existing classes in order to update to 2.6, I'm more  
> than happy to switch it.
>
> Avi
> _______________________________________________
> Seaside mailing list
> Seaside@xxxxxxxxxxxxxxxxxxxxxxxxxx
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside