Smalltalk › Frameworks & Tools › Seaside › Seaside Development

Canvas Differences

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

littleSmalltalker

Canvas Differences

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?

Thanks,
Avi.

_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Philippe Marschall

Re: Canvas Differences

2011/2/1 Avi Shefi <[hidden email]>:
> 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
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

littleSmalltalker

Re: Canvas Differences

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 <[hidden email]> wrote:

2011/2/1 Avi Shefi <[hidden email]>:

> 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
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Philippe Marschall

Re: Canvas Differences

2011/2/4 Avi Shefi <[hidden email]>:

> 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.

No problem, looking at the code again this is a left over from the
Seaside 2.8 days when the callbacks where in the canvas. Now we have
WARenderContext and the callbacks there.

Anyway I created http://code.google.com/p/seaside/issues/detail?id=639

Cheers
Philippe
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Julian Fitzell-2

Re: Canvas Differences

On Sat, Feb 5, 2011 at 9:56 AM, Philippe Marschall
<[hidden email]> wrote:

> 2011/2/4 Avi Shefi <[hidden email]>:
>> 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.
>
> No problem, looking at the code again this is a left over from the
> Seaside 2.8 days when the callbacks where in the canvas. Now we have
> WARenderContext and the callbacks there.

I was thinking the same thing... that it must be related to the
introduction of the render context. The two classes are probably not
required anymore... I added a comment to the issue 639.

Julian
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev