[Seaside-dev] Canvas Differences

[Avi Shefi]

Phillipe,
Thanks. I've read the class comments, however I noticed that the following
elements do have callbacks but are on the WAHtmlCanvas:
 - anchor
 - iframe
 - map (WAImageMapTag)

Judging by the class comments, weren't these supposed to go on
WARenderCanvas ?


I'm not trying to be picky, I just want to understand the difference because
I'm working on changes to this package.

Thanks,
Avi.

On Tue, Feb 1, 2011 at 10:28 PM, Philippe Marschall <
philippe.marschall at gmail.com> wrote:

> 2011/2/1 Avi Shefi <avishefi at gmail.com>:
> > Hi,
> > I'm working on improving HTML5 support on Seaside, and wondered what's
> the
> > semantic difference between WAHtmlCanvas and WARenderCanvas ?
> > From an overview it looks like HTML5 input-related elements are on
> > WARenderCanvas, and the rest is on WAHtmlCanvas.
> >
> > What kind of tags should be implemented where?
>
> Lemme quote from the class comment:
>
> WAHtmlCanvas
> This is an abstract canvas that knows about HTML but nothing about
> callbacks. Subclasses must implement #document.
>
> WARenderCanvas
> This canvas knows about callbacks and is intertwined with the rest of
> the framework.
>
> Cheers
> Philippe
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20110204/6990ee47/attachment.htm