[Seaside] Where to look to find out what...

Julian Fitzell julian at beta4.com
Thu Mar 2 18:10:27 UTC 2006

There's always work being done, but you should be safe to use it.  There 
are certainly plenty of people who are and the only reason it isn't the 
default is really to avoid breaking backwards compatibility.

You may have to make small changes if you're updating seaside but they 
shouldn't be too major...


Rick Flower wrote:
> Julian Fitzell wrote:
>> Whatever your component returns when sent #rendererClass will be used 
>> as the renderer for that component.
>> WAPresenter (a superclass of WAComponent) implements it like this:
>> rendererClass
>>     ^ WAHtmlRenderer
>> So your components will all use the old rendering API unless you 
>> reimplement that method to return WAHtmlCanvas instead.  If you want 
>> to do this, it's probably best to make a component subclass for your 
>> project and then subclass that for all your components.  This is good 
>> practice anyway as there always seems to be behaviour you want to 
>> share across all your components anyway.
> Thanks Julian -- my next question is whether or not the WAHtmlCanvas is 
> sufficiently stable at this point to use it (e.g. is the design going to 
> change enough to break things as I proceed down my path and perhaps 
> upgrade Seaside occasionally as I go).. If there is still working being 
> done that may break things that use it, I'll probably continue using 
> what I've got now (WAHtmlRenderer).. Thanks!
> -- Rick
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the Seaside mailing list