[Seaside] Re: A Seaside2 application for SVG clients

[Klaus D. Witzel]

On Mon, 06 Aug 2007 11:27:40 +0200, Matthias Berth wrote:
> Hi,
>
> looks interesting, if you want to include IE users, have a look at Dojo  
> gfx,
>
>  http://www.sitepen.com/blog/2007/03/27/ajaxworld-and-sxsw-talks-on-dojogfx/
>
> it is a cross-browser JavaScript library that will render SVG (where
> possible) and WML on IE.

Thank you Matthias, will check and see if that can be added that to the  
staging process.

> Might be interesting to think about Morphs
> rendering to a web page and events being sent back to the server.

Go ahead, please :) Where/with what would you start to get an initial Aha?

/Klaus

> Matthias
>
> On 8/6/07, Klaus D. Witzel wrote:
>> On Mon, 06 Aug 2007 07:02:16 +0200, Philippe Marschallwrote:
>> > 2007/8/6, Klaus D. Witzel:
>> >> 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
>>
>> That's a good point, keeping an eye on the coder's convenience.
>>
>> >> 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.
>>
>> Yes, WARenderCanvas seems misplaced in the class hierarchy (on first
>> sight).
>>
>> And ProtocolBrowser, which separates by message-category name (example:
>> #html and #'form-buttons'), is not of much help for finding overrides  
>> and
>> responsibilities of the sub/superclass. Is there any better tool/view  
>> for
>> Squeak which someone would recommend.
>>
>> >> 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.
>>
>> Have you considered taking WARenderCanvas away from its superclass.
>>
>> >> o any other comment or suggestion, all appreciated
>> >
>> > Can we see the code? ;-)
>>
>> Yes, Seasiders can :)
>>
>> /Klaus
>>
>> > Philippe
>> >
>> >> /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
>> >>
>>
>>
>> _______________________________________________
>> Seaside mailing list
>> Seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>