April 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] Handle Close Event in Image - necessary for 1.0?

by Torsten Bergmann

>open a ticket As I wrote, there is an issue 2131 already. >provide some tested code I can just provide an old changeset mixed up from Squeak code - it works but I do not have tested or look if it merges correctly with Pharo. At least it works, I dont like the "TheWorldMenu basicNew quitSession" hack. Someone (with knowledge of the event handling system) should review or enhance it (Marcus?). You will find it attached. >I cannot do everything especially for platform I do not have access to. We should handle this in-image now for all platforms since it is AFAIK this is now supported by all VM's. How is it done on Mac and Linux these days? >Then, for 1.1 open a ticket so that someone try to fix the problem with the >version 4. There is already one: http://code.google.com/p/pharo/issues/detail?id=2131 If we want to keep quality high we should care about this. Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

April 6, 2010

Re: [Pharo-project] FFI tests

by Schwab,Wilhelm K

True that FFI works in general, but do double return values work? I'm getting some weird results. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck [marianopeck(a)gmail.com] Sent: Tuesday, April 06, 2010 5:47 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] FFI tests Those tests never worked for me. However, FFI does work. so I guess it is a problem in the tests and probably in the libraries it uses and the current OS where you are running them. Cheers Mariano On Mon, Apr 5, 2010 at 9:33 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> wrote: Hello all, Is anyone having success with the FFI tests on Linux? I have been having some weird problems with an RC1 image and noted that many of the tests fail in it. My image builder is almost ready for another attempt at making a newer image, and I will prioritize the tests. I also have an idea or two on how to try to reproduce the problems I am having. Bill _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 6, 2010

Re: [Pharo-project] Handle Close Event in Image - necessary for 1.0?

by Mariano Martinez Peck

Thanks Torsten for reporting. I don't think this is a stopper for 1.0 at all. We can release an older VM without that problem ? Even more because the new version 4 doesn't bring anything new for Pharo. isn't it ? The only problem where ImageSegment...Ok, I rather to have working this thing of closing the windows. Can you tell us exactly the link of the previous vm that was working ? because we are doing the one-click now and we took the 4. Then, for 1.1 open a ticket so that someone try to fix the problem with the version 4. Cheers Mariano On Tue, Apr 6, 2010 at 7:22 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > I think I've found something that should be fixed > before releasing 1.0 since it is meanwhile a major problem on Windows. > > In "old" Squeak/Pharo you could close the native world window > using the "X" or hit ALT+F4 on Windows and the system > asked you if you really want to close the whole Smalltalk system > using a native dialog which was provided by the VM. > > With the new VM's (4.0.1 and 4.0.2 on Windows, see [1]) the native > "window close event" is now dispatched from the VM into > the image so it could be handled by Smalltalk code. > This is currently not done/handled in Pharo. Only in Squeak so far. > > The recent Squeak trunk/release candidate already handles the > event within the image and now provides an in-image dialog > to ask the user to quit. > > So: in Pharo now NOTHING happens when you try to close the window > using "X", you can only quit using the world menu - which is IMHO really > a show stopper since you cant close using "X" or ALT+F4 (the key > combination to close any windows program). > > Two possible options: > > A) we should handle the event now in-image similar to Squeak > by fixing and integration issue 2131 (see [2]), so not only > for 1.1. but also for 1.0 > > B) release and distribute Pharo 1.0 with an old VM < 4.0 > > > BTW: > You can get the old behavior on Windows by additionally using SHIFT, so > SHIFT + ALT + F4 allows to close. > But this is not very convinient, doesnt follow what the typical > Windows user expects and one has to know about it... > > Bye > T. > > [1] > http://lists.squeakfoundation.org/pipermail/vm-dev/2010-March/004142.html > [2] http://code.google.com/p/pharo/issues/detail?id=2131 > > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 6, 2010

Re: [Pharo-project] Handle Close Event in Image - necessary for 1.0?

by StÃ©phane Ducasse

if you want this to be fixed for 1.1 open a ticket provide some tested code I cannot do everything especially for platform I do not have access to. Stef > I think I've found something that should be fixed > before releasing 1.0 since it is meanwhile a major problem on Windows. > > In "old" Squeak/Pharo you could close the native world window > using the "X" or hit ALT+F4 on Windows and the system > asked you if you really want to close the whole Smalltalk system > using a native dialog which was provided by the VM. > > With the new VM's (4.0.1 and 4.0.2 on Windows, see [1]) the native > "window close event" is now dispatched from the VM into > the image so it could be handled by Smalltalk code. > This is currently not done/handled in Pharo. Only in Squeak so far. > > The recent Squeak trunk/release candidate already handles the > event within the image and now provides an in-image dialog > to ask the user to quit. > > So: in Pharo now NOTHING happens when you try to close the window > using "X", you can only quit using the world menu - which is IMHO really > a show stopper since you cant close using "X" or ALT+F4 (the key combination to close any windows program). a showstopper is something that breaks and put the system on its knees. So this problem may be fixed but only for 1.1. > > Two possible options: > > A) we should handle the event now in-image similar to Squeak > by fixing and integration issue 2131 (see [2]), so not only > for 1.1. but also for 1.0 > > B) release and distribute Pharo 1.0 with an old VM < 4.0 > > > BTW: > You can get the old behavior on Windows by additionally using SHIFT, so > SHIFT + ALT + F4 allows to close. > But this is not very convinient, doesnt follow what the typical > Windows user expects and one has to know about it... > > Bye > T. > > [1] http://lists.squeakfoundation.org/pipermail/vm-dev/2010-March/004142.html > [2] http://code.google.com/p/pharo/issues/detail?id=2131 > > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 6, 2010

[Pharo-project] Handle Close Event in Image - necessary for 1.0?

by Torsten Bergmann

I think I've found something that should be fixed before releasing 1.0 since it is meanwhile a major problem on Windows. In "old" Squeak/Pharo you could close the native world window using the "X" or hit ALT+F4 on Windows and the system asked you if you really want to close the whole Smalltalk system using a native dialog which was provided by the VM. With the new VM's (4.0.1 and 4.0.2 on Windows, see [1]) the native "window close event" is now dispatched from the VM into the image so it could be handled by Smalltalk code. This is currently not done/handled in Pharo. Only in Squeak so far. The recent Squeak trunk/release candidate already handles the event within the image and now provides an in-image dialog to ask the user to quit. So: in Pharo now NOTHING happens when you try to close the window using "X", you can only quit using the world menu - which is IMHO really a show stopper since you cant close using "X" or ALT+F4 (the key combination to close any windows program). Two possible options: A) we should handle the event now in-image similar to Squeak by fixing and integration issue 2131 (see [2]), so not only for 1.1. but also for 1.0 B) release and distribute Pharo 1.0 with an old VM < 4.0 BTW: You can get the old behavior on Windows by additionally using SHIFT, so SHIFT + ALT + F4 allows to close. But this is not very convinient, doesnt follow what the typical Windows user expects and one has to know about it... Bye T. [1] http://lists.squeakfoundation.org/pipermail/vm-dev/2010-March/004142.html [2] http://code.google.com/p/pharo/issues/detail?id=2131 -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

April 6, 2010

Re: [Pharo-project] SUnit (which tests call which methods?)

by Stan Shepherd

Adrian Kuhn wrote: > > We got some more ideas (... search in test results) > Is there a way to see which tests invoked a given method? Sometimes you're trying to understand a method, to see if it does what you're trying to achieve. In such cases, it would be really handy to see which tests used a given method during a system-wide test, and then invoke one of those to give you a handle on the method. Does such a thing already exist? ...Stan > Niko and me are thinking about doing some work on SUnit. > > Background is that we are working on Phexample, which extends SUnit with > test > that expand on one another [1]. We got test dependencies working with the > current SUnit, but had to do some quick ugly hacks. So we thought about > cleaning the internals SUnit up, and then include test dependencies in > the > core. > > Things we would possible change (we will certainly identify more as we > clean > up SUnit...) > > - store test resources in a dynamic variable rather than a static one > - refactor the assert: protocol to a trait, such that they can be used in > setup and teardown of test resources as well (actually I already did > that, > you can find a version on my squeaksource account) > - apply the fixes to test resources in Niall's slide deck that Lukas > showed us > - add expectations matchers as used in behavior-driven testing > - break testcase into two classes, and to run the test and one to store > the > result (no more #cleanUpInstanceVariables hack to avoid memory leaks) > - add test dependencies to test results, such that one test can extend on > the > return value of another test > - fix expected failures such that they are a first-class result (no more > #shouldPass with O(n^2) or worse behavior) > > So you see, the idea is twofold: first to clean up what is there, and > second > to add test dependencies as a new feature. For those that dont know test > dependencies. They had first been proposed by Markus GÃ¤lli based on an > analysis of all Squeak tests years ago. He found that most tests cover a > superset of another test's coverage set. A prototype in Java as been > implemented later by Lea HÃ¤nsenberger and me. We published a case study > at > XP 2008, which lead to PHP folks to include test dependencies in the > latest > PHPUnit. The idea of explicit test dependencies is to shift the burden of > isolating test cases from the developers to the framework. You avoid > duplicate test code and you get less red test cases per failure. Please > refer to Niko's blog post for more details [2]. > > We got some more ideas (such as API baseline testing, search in test > results, > etc...) but they will not likely make it into a first clean up. > > One thing we do not know is how many folks are out there that depend on > internal representation of SUnit. I talked to some folks and identified > two > requirements, first that legacy tests should keep running and second that > contributions to other sunit forks should keep being mergeable. The first > seems feasible, the second sounds like it boils down to not cleaning > anything :) > > What do you think? > > cheers, > AA > > [1]: http://www.squeaksource.com/phexample.html > [2]: > http://smalltalkthoughts.blogspot.com/2009/11/phexample-because-examples-ex… > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- View this message in context: http://n4.nabble.com/SUnit-tp1297972p1752629.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 6, 2010

Re: [Pharo-project] Linux VM microbenchmarks

by laurent laffont

On Tue, Apr 6, 2010 at 11:45 AM, Hilaire Fernandes < hilaire.fernandes(a)gmail.com> wrote: > laurent laffont a Ã©crit : > > > btw, in all the version you provided there is no free type pluglin >> >> >> ? Should be here... What's the output of your ../unix/cmake/configure >> command ? >> > > -- checking for module 'freetype2' > -- package 'freetype2' not found Do you have packages libfreetype6-dev and libfreetype6 installed ? Laurent Laffont > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 6, 2010

Re: [Pharo-project] FFI tests

by Mariano Martinez Peck

Those tests never worked for me. However, FFI does work. so I guess it is a problem in the tests and probably in the libraries it uses and the current OS where you are running them. Cheers Mariano On Mon, Apr 5, 2010 at 9:33 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>wrote: > Hello all, > > Is anyone having success with the FFI tests on Linux? I have been having > some weird problems with an RC1 image and noted that many of the tests fail > in it. > > My image builder is almost ready for another attempt at making a newer > image, and I will prioritize the tests. I also have an idea or two on how > to try to reproduce the problems I am having. > > Bill > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 6, 2010

Re: [Pharo-project] Linux VM microbenchmarks

by Hilaire Fernandes

laurent laffont a Ã©crit : > btw, in all the version you provided there is no free type pluglin > > > ? Should be here... What's the output of your ../unix/cmake/configure > command ? -- checking for module 'freetype2' -- package 'freetype2' not found

April 6, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10517-rc4dev10.04.1

by StÃ©phane Ducasse

these are not show stoppers so they will be fixed in 1.1 Stef On Apr 6, 2010, at 11:06 AM, Stan Shepherd wrote: > > ...and http://code.google.com/p/pharo/issues/detail?id=2279 > -- > View this message in context: http://n4.nabble.com/BetaTesting-ANN-Pharo-1-0-10517-rc4dev10-04-1-tp174923… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 6, 2010