Tweak mainstream in Squeak
cputney at wiresong.ca
Mon Jul 10 20:55:23 UTC 2006
On Jul 10, 2006, at 4:22 PM, Julian Fitzell wrote:
> I'm not saying don't break compatibility, I'm just saying be aware
> every time that you are doing it. And the thought that there be a
> relatively stable API for a core set of classes that doesn't change
> without some forethought is perfectly reasonable, in my opinion.
> At least then, when compatibility is broken, detailed instructions
> could be provided on how to update your software in each case.
Here, here. I'll add an example of the kind of incompatibility that
I, at least, am frustrated by.
I try to keep OmniBrowser compatible with Squeak 3.6 and later. Prior
to 3.9, you can fetch a menu icon for delete operations by sending
#deleteIcon to the class MenuIcons. In 3.9 you have to send
#smallDeleteIcon. As far as I can tell, the change is completely
gratuitous. The icon is small, yes, but there's no corresponding
#largeDeleteIcon. #deleteIcon was just removed, it wasn't changed to
call through to #smallDeleteIcon or even deprecated.
Apparently, I have to jump through some hoops to make menus work in
Squeak 3.9 because somebody wanted to make the selectors more
consistent. I'm all for progress, but this kind of thing is just
More information about the Squeak-dev