[Seaside] A Seaside2 application for SVG clients

Philippe Marschall philippe.marschall at gmail.com
Mon Aug 6 05:02:16 UTC 2007

2007/8/6, Klaus D. Witzel <klaus.witzel at cobss.com>:
> Dear Seasiders,
> with only a handful of methods it was possible to create a prototype
> Seaside2 application[1] which serves SVG clients[2]. Many thanks to all
> the Seaside developers which have put in such a lot of effort to make it
> so easy for new applications and developers :)
> The next logical step is to make a canvas for SVG, like the one which
> exists for HTML. So may I ask,
> o are there any do's and dont's for a Seaside renderer/canvas

WAHtmlCanvas once had code that would automatically generated the code
of all the tag generation methods for you. One rule that has emerged
is to use a the full name instead of the real element name: #anchor
instead of #a

> o is there anything you would have done completely different,
>   if you could start all over again (without any backward compatibility)

In WARenderCanvas? Yes, if we had better traits tools we would use them.

> o if at some point in time #callback: would be added,
>   are there any drawbacks, things to be aware of ahead of time

You'll probably end up duplicating the funtionality of WARenderCanvas.

> o any other comment or suggestion, all appreciated

Can we see the code? ;-)


> /Klaus
> -----------
> [1] http://squeak.cobss.ch/seaside/sextant
> Does some effects on the builtin Seaside top.jpg image.
> [2] Firefox and Opera support SVG, Firefox only to "some" extent.
> Opera even supports the Ajax script.
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the Seaside mailing list