This sounds like a nice opportunity to climb on the native widget soap box for a moment. I am not at all convinced that native widgets would make us faster (though they might help with specific things, e.g. rendering large blocks of text), but they would force discipline on us. Imagine the cruft that would disappear if the windowing system were *completely* replaced. That is, of course, more easily said than done, and a lot of code depends on the cruft. You did say you wanted to start a discussion :) Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Sean P. DeNigris [sean@clipperadams.com] Sent: Wednesday, November 23, 2011 2:20 PM To: pharo-project@lists.gforge.inria.fr Subject: [Pharo-project] Backward Compatibility The Pharo Manifesto (http://code.google.com/p/pharo/) lists "Not backward compatible" as one of its 4 tenants. Yet, while working through the issue tracker, I've noticed some adding/keeping complexity to keep things backward compatible - most recently http://code.google.com/p/pharo/issues/detail?id=5007. I just wanted to start a discussion because obviously the more mature Pharo gets, the harder it will be to remove things... Sean -- View this message in context: http://forum.world.st/Backward-Compatibility-tp4101111p4101111.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

On 23 November 2011 20:20, Sean P. DeNigris <sean@clipperadams.com> wrote:

The Pharo Manifesto (http://code.google.com/p/pharo/) lists "Not backward compatible" as one of its 4 tenants. Yet, while working through the issue tracker, I've noticed some adding/keeping complexity to keep things backward compatible - most recently http://code.google.com/p/pharo/issues/detail?id=5007.

I just wanted to start a discussion because obviously the more mature Pharo gets, the harder it will be to remove things...

i think this is overestimated . i think pressing cmd-s on dialog with single text entry should work as if you pressed ok (and accepted the modified text, of course). because for 'not accepting' there is a cancel button, normally. As for keeping things compatible or not, my own vision is following: - if you can improve thing while keeping it compatible, no problem - if you cannot, but making changes will require a lot of effort, maybe it is better to keep things as is, and do just cosmetic changes, until - at some point you can find time/people who can make an overhaul and rewrite the stuff, without caring about compatibility, but caring about making things working :)

Sean

-- View this message in context: http://forum.world.st/Backward-Compatibility-tp4101111p4101111.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

-- Best regards, Igor Stasenko.