On 23.11.2011 20:20, Sean P. DeNigris 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...
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.
I don't get it, I don't see how ctrl-s does anyhing in the original case... You click OK without accepting the contents first, and it still returns the modified text. Why not just remove the yellow "this editor has unaccepted contents" marker for this type of dialog? Altering ctrl-s to do an accept of the input isn't really what I'd expect from an input dialog... Cheers, Henry