[Seaside] Updating code to Canvas API

Boris Popov boris at deepcovelabs.com
Fri Jul 21 19:38:55 UTC 2006

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.



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

boris at deepcovelabs.com


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

Thank you.

-----Original Message-----
From: seaside-bounces at lists.squeakfoundation.org
[mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Damien
Sent: Friday, July 21, 2006 12:32 PM
To: Seaside
Subject: [Seaside] Updating code to Canvas API


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 ?

Seaside mailing list
Seaside at lists.squeakfoundation.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3370 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20060721/f6034c3e/smime.bin

More information about the Seaside mailing list