- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Backward Compatibility

by Igor Stasenko

On 23 November 2011 20:20, Sean P. DeNigris <sean(a)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.

Nov. 23, 2011

Re: [Pharo-project] Backward Compatibility

by Henrik Sperre Johansen

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

Nov. 23, 2011

Re: [Pharo-project] World intermittently becoming a mess

by Alexandre Bergel

Yes, I experienced this a couple of times. I think it has to do with the UI Thread. This happened when I was debugging a Roassal visualization Alexandre On 23 Nov 2011, at 16:38, Sean P. DeNigris wrote: > Every once in a while, in my 1.3-rc image, the World becomes a mess. > Specifically: > * moving windows without the fast dragging setting enabled leaves a trail > * previews from hovering over the task bar remain in the World and don't > delete themselves when the mouse is no longer over the task bar > > I haven't been able to reproduce it, but it's happened a few times. Has > anyone else experienced this? > > I opened an issue: http://code.google.com/p/pharo/issues/detail?id=5013 > > -- > View this message in context: http://forum.world.st/World-intermittently-becoming-a-mess-tp4101204p410120… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 23, 2011

[Pharo-project] [TODO 1.3] Open Issues in 1.3

by Marcus Denker

Just 6. Three of them have suggested solutions that just need to be checked: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.3 -- Marcus Denker -- http://marcusdenker.de

Nov. 23, 2011

[Pharo-project] Call for feedback: assessing the test coverage with Hapao

by Alexandre Bergel

Dear All, As you may know, Vanessa and I have been working on a visual tool to help people increase the test coverage. The website contains screenshots, documents and screencast: http://hapao.dcc.uchile.cl/ Hapao is easy to install: -=-=-=--=-=-=--=-=-=--=-=-=- Gofer new squeaksource: 'Spy'; package: 'ConfigurationOfSpy'; load. (Smalltalk at: #ConfigurationOfSpy) project lastVersion load -=-=-=--=-=-=--=-=-=--=-=-=- And then get it from the world menu. We crucially need feedback. This is necessary to target serious conferences. It does not take long to try. If you are developing right now, then you can let Hapao help you focus where you write new unit tests. You can leave your feedback on: https://docs.google.com/spreadsheet/viewform?hl=en_US&formkey=dDRKMzh4VzZBZ… We need feedback before the end of the month. Thanks to all! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 23, 2011

[Pharo-project] [TODO 1.4] Open Issues in 1.4

by Marcus Denker

http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.4 -- Marcus Denker -- http://marcusdenker.de

Nov. 23, 2011

[Pharo-project] World intermittently becoming a mess

by Sean P. DeNigris

Every once in a while, in my 1.3-rc image, the World becomes a mess. Specifically: * moving windows without the fast dragging setting enabled leaves a trail * previews from hovering over the task bar remain in the World and don't delete themselves when the mouse is no longer over the task bar I haven't been able to reproduce it, but it's happened a few times. Has anyone else experienced this? I opened an issue: http://code.google.com/p/pharo/issues/detail?id=5013 -- View this message in context: http://forum.world.st/World-intermittently-becoming-a-mess-tp4101204p410120… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 23, 2011

Re: [Pharo-project] Backward Compatibility

by Schwab,Wilhelm K

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(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Sean P. DeNigris [sean(a)clipperadams.com] Sent: Wednesday, November 23, 2011 2:20 PM To: pharo-project(a)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.

Nov. 23, 2011

Re: [Pharo-project] GUI Testing Library

by Alexandre Bergel

I will invite you for a couple of beers at the next esug :-) I cannot try it right now (bad internet connection), but I checked the source code. It looks good. Cheers, Alexandre On 23 Nov 2011, at 13:12, Sean P. DeNigris wrote: > > Alexandre Bergel-7 wrote >> >> I opened an issue: http://code.google.com/p/pharo/issues/detail?id=5010 >> > > Fix (although I guess there are more widgets to fix?) in 1.4 inbox > SLICE-Issue-5010-Testing-GUI-widgets-SeanDeNigris.1 > > > Alexandre Bergel-7 wrote >> >> This is very valuable. Currently it is really hard to test GUI in Pharo. >> > I think it could be very easy with a little work > > > Alexandre Bergel-7 wrote >> >> One problem I faced several times is that GUI are not uniformly managed: >> some GUI widgets use of exceptions (which is cool), some other are >> blocking the currently thread (which is not cool). >> > The hook points are in MorphicUIManager's "ui requests" protocol. For each > type of interaction (e.g. confirm), in the method that takes the most > arguments (e.g. #confirm:label:, not #confirm:), ProvideAnswerNotification > is signaled. > > > Alexandre Bergel-7 wrote >> >> For example, I can write... >> > Thanks for the examples. I wrote them into Morphic tests (incl. in fix > above) > > > Alexandre Bergel-7 wrote >> >> self should: ['/tmp' = ([UIManager default chooseDirectory] >> valueSupplyingAnswer: #('/tmp'))] >> > This works now, but the syntax is ...valueSupplyingAnswer: { 'Choose > Directory'. FileDirectory on: '/tmp' }. > > HTH, > Sean > > -- > View this message in context: http://forum.world.st/GUI-Testing-Library-tp4097866p4100236.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 23, 2011

[Pharo-project] Backward Compatibility

by Sean P. DeNigris

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.

Nov. 23, 2011