[squeak-dev] Roassal3 "action plan"

gettimothy gettimothy at zoho.com
Sun Oct 25 14:11:58 UTC 2020


Hi Tom,



After thinking on it, it makes sense to port all the pharo Athens calls to methods in "some appropriate class" in the Balloon or Graphics area and modifying the pharo call to those methods to use the Balloon/Graphics methods.



AND



when doing that, duplicate the Tests for those calls.



All the while asking for pointers on specific instances.





The approach gives me a needed structure, instead of doing "stupid stuff" like cloning in the GraphicsPaint class from Athen's directly into squeak, just to make things work.



Sound like a plan?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20201025/301a905d/attachment-0001.html>


More information about the Squeak-dev mailing list