Updating code to Canvas API

Hi,

I've seen that Seaside examples are slowly converted to Canvas API.
Should we do this for all classes ? Should we try to remove the old API
from the 2.6 branches ?


Bye
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

By removing, you mean removing it from examples only? Removing it completely
would surely break a few existing applications out there unless we're
willing to take the risk of trying to force everyone onto the Canvas API.

Cheers!

-Boris

--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

[hidden email]

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Damien
Cassou
Sent: Friday, July 21, 2006 12:32 PM
To: Seaside
Subject: [Seaside] Updating code to Canvas API

Hi,

I've seen that Seaside examples are slowly converted to Canvas API.
Should we do this for all classes ? Should we try to remove the old API
from the 2.6 branches ?


Bye
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

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

Boris Popov wrote:
> By removing, you mean removing it from examples only?

Sure, sorry for not having been clear. I mean changing the code that use
the old API to the new API, not removing the old API. For examples and
other components.

What do you think ?
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

On Jul 21, 2006, at 11:31 PM, Damien Cassou wrote:

> Boris Popov wrote:
>> By removing, you mean removing it from examples only?
>
> Sure, sorry for not having been clear. I mean changing the code  
> that use the old API to the new API, not removing the old API. For  
> examples and other components.
>
> What do you think ?

+1

Avi
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Avi Bryant wrote:
I'm doing this in 2.6b1, is it ok ?
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

2006/7/22, Damien Cassou <[hidden email]>:
I think we should find a consensus how much code we want to break.
Converting tools (eg. WALibraryBrowser) and examples (eg. WACounter)
is unlikely to break any client code. But once we start converting
stuff in 'Seaside-Components-Widgets' we might break client code that
subclasses these components.

For WATableReport there is a separate class for the canvas API. Is
this something we want for all the components or only the important
ones (WATableReport obviously, any others)?

We have only very few code that would be affected by this, so this
would be no problem for us but I don't know about others.

Philippe
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside