Usability and look-and-feel (was Re: [squeak-dev] The future of Squeak & Pharo (was Re: [Pharo-project] [ANN] Pharo MIT license clean))

Ian Trudel ian.trudel at gmail.com
Mon Jun 29 20:37:08 UTC 2009


2009/6/29 Stéphane Rollandin <lecteur at zogotounga.net>:

Stéphane,

There are definitively merits in favour of backward compatibility.
Changes should probably be brought at a slower pace: small changes in
minor versions, bigger changes to be expected in major versions.
Hardly any news here. Migration tools to help maintainers should be
considered. It's possible to make progress and change coexist, we have
to figure out what will work in the Squeak community.

How hard would it be to implement migration tool(s) in Squeak? Anyone? Ideas?

> ... and reading today what I wrote almost 5 years ago, I see that I don't
> need to change a word: it's still pretty much the same situation.

Yes. And it will come back as long as the situation is not resolved.


What kind of maintenance do you have to do on your projects when
changes are brought? What packages are your projects based on? You
have to open up a little bit if you hope the community to find a
suitable solution.

Ian.

-- 
http://mecenia.blogspot.com/



More information about the Squeak-dev mailing list