Well, for transitional projects, like some I'm working on now, the
older WAHtmlRenderer based code can run happily under 2.6 and my new
stuff subclasses a common component that overrides rendererClass.
Then I can work on new parts with Canvas and the old stuff doesn't
have to be changed at all until it's time for a refactor.
Brian
On Jan 25, 2006, at 2:17 PM, 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
