[Seaside] WAHtmlRenderer or WAHtmlCanvas?
romain.robbes at gmail.com
Mon Apr 2 08:52:01 UTC 2007
In seaside 2.7 and newer, WAHtmlCanvas is the default renderer. Which
version of seaside are you using?
Il giorno Apr 1, 2007, alle ore 8:40 PM, Marco Primi ha scritto:
> i started to work on a simple application with seaside almost a
> month ago,
> currently i'm subclassing WAHtmlCanvas and using it as
> 'rendererClass' for my
> My goal was to extend seaside to render SVG graphics inline,
> generating it
> inside xhtml, and this has worked fine so far
> However, trying some examples from the seaside official documentation,
> for example:
> html form:
> [html text: 'Name: '.
> html textInputWithValue: person name callback: [:val | person
> name: val].
> html break.
> html submitButton]
> results in an error, since methods like
> #textInputWithValue:callback: are
> implemented in WAHtmlRenderer which is not in my hierarchy.
> Searching in this list i found a message from a couple of years ago
> that says
> "WAHtmlCanvas is still under development, don't use it"
> What is the state of development today? Is WAHtmlCanvas ready to be
> if so, what is the equivalent of #textInputWithValue:callback: with
> the new API?
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Seaside