- Pharo-dev - lists.pharo.org

Re: [Pharo-project] cog and libSqueakSSL.so

by Igor Stasenko

On 6 April 2012 10:43, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > > On 06 Apr 2012, at 03:34, Sebastian Sastre wrote: > >> ok, I did. >> >> It fixed the undefined symbol problem (that isn't shown anymore) and SqueakSSL it's now listed among the list of loaded modules. >> >> At first the #testPlain didn't pass but after a couple of runs it started to pass. >> >> â¦but >> >> ZnEasy get: 'https://encrypted.google.com/search?q=Smalltalk'. >> >> is timming out the connection every time Â :( >> >> sounds familiar? ideas? > > No concrete idea, no, sorry. > > But I would suggest being more conservative on the vm side. > > Apparently, http://ci.lille.inria.fr/pharo/view/VM/job/Cog-Unix/lastSuccessfulBuild/art…, which I believe you used, is a bit too fresh and has incomplete SSL support. > Yes, Camillo just added SSL plugin into build, but its not yet even checked if it functional or not. > Maybe someone can suggest a link to an older pharo linux vm. The archive that I am using looks like this: > > $ ls -l cog-vm.zip > -rw-rw-r-- 1 ubuntu ubuntu 611334 2012-03-01 11:55 cog-vm.zip > > $ md5sum cog-vm.zip > 479ba1a66a91b10bdc2374a661771814 Â cog-vm.zip > > I could publish mine somewhere if that helps. > > Sven > -- Best regards, Igor Stasenko.

April 6, 2012

Re: [Pharo-project] CogVM and fn key

by Igor Stasenko

On 6 April 2012 10:38, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Hmm, strange...Â I fixed it on january > > https://gitorious.org/~gpolito/cogvm/gpolito-cogvm > > and then pushed it to > > https://gitorious.org/cogvm/blessed > > But looking at the sources from the CI server, my fix is not there... > strange.. it should be there if you pushed to master branch. and for sure, there's nobody who rejected/reverted your change(s) maybe by a mistake.. -- Best regards, Igor Stasenko.

April 6, 2012

Re: [Pharo-project] SUnit and TestCase

by Benjamin

On Apr 6, 2012, at 1:19 PM, Guillermo Polito wrote: > > > On Fri, Apr 6, 2012 at 1:12 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > > On Apr 5, 2012, at 3:37 PM, Guillermo Polito wrote: > >> >> On Thu, Apr 5, 2012 at 3:17 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> per instance ? >> I you wanna know when a test instance you run started, I think there are better solutions than announcement. >> >> Hehe, actually, if you are the one firing the test, then you do need nothing :). Also the tests instances are discarded to have independent state so what I said is nonsense :). >> >> >> For me the goal of announcement is to emit, and than everyone can catch this information. >> >> Hmm, that's one specific use for them... You can build for example a small application using announcements to decouple the UI from the model, and there you probably will not make the announcer accessible for everyone. > > It's not specific, I think it should be the default behavior. > > Because if you want to listen only the FooTestClass announcement, you can always record yourself as a listener for all TestAnnouncement, and then test if the announcement is relevant for you or not. > > > Because if you need to know which class emit the announcement to be able to register, then you create a strong dependency from your class to the test class. And this is wrong (and announcement have been introduced to break this pattern) > > But that way you are creating a strong dependency against another class like TestAnnouncement or just TestCase :P. And if you want to filter the announcements for a specific class, you will do it too! You create a dependency to the Announcer instead of the classes emitting announcement, I think this is the correct way to do it :) Of course if you filter you create a dependency to the test class. But you only create a strong dependency in the case you are really interested by this particular class. If you want to listen to every test classes, you do not have to create a strong dependency to all the classes Ben > Anyway, if you're metaprogramming, then for sure are other ways to get the class without having a static reference to it. > > > > > Ben > > >>> On Thu, Apr 5, 2012 at 2:57 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >>> Since there is an announcer per test class, you need to write something like >>> >>> MyClass>>#register >>> MyTestClass announcer >>> on: TestCaseStarted send: #foo to: self. >>> >>> It means than here you force a link from MyClass to MyTestClass. >>> And if you want to be aware of all test case started, you need something like >>> >>> TestCase withAllSubclasses do: [:e | e announcer >>> on: TestCaseStarted send: #foo to: self ]. >>> >>> Why not using only one Announcer (and TestAnnouncer already exists and is already integrated) for all test class ? >>> >> >> And then you lack the possibility to subscribe to a specific one... Maybe you can add a method in TestCase hiding the subscriptions to all the subclasses. >> >>> >>> Ben >>> >>> >>> On Apr 5, 2012, at 3:50 PM, Alexandre Bergel wrote: >>> >>> > I proposed this test announcement facilities some times ago to get notified when tests are being executed and when they are done. >>> > >>> > You said: "It means that you have to know which class to register to instead of which announcer." >>> > Which unit to register you mean? Yes, the one you are interested in. I do not see why it break the pattern. Consider TestCaseTest>>testAnnouncement. What is wrong with it? >>> > >>> > Cheers, >>> > Alexandre >>> > >>> > >>> > On 5 Apr 2012, at 06:14, Benjamin wrote: >>> > >>> >> Hello guys, >>> >> >>> >> I was implementing in Nautilus a listener to TestCaseStarted, and then I figured out that each TestCase subclasses have its own Announcer. >>> >> >>> >> It means that you have to know which class to register to instead of which announcer. In a way, it breaks the Observer pattern. >>> >> >>> >> Is there any good reason I am missing ? >>> >> >>> >> I think it has been done in a way you can spy a particular test class, but since you have this info in the announcement itself, you can always filter with this info. >>> >> Cause for me, replacing all those announcer by TestAnnouncer seems to be a better solution. >>> >> >>> >> >>> >> >>> >> Thanks in advance, >>> >> >>> >> Ben >>> > >>> > -- >>> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> > Alexandre Bergel http://www.bergel.eu >>> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> > >>> > >>> > >>> > >>> > >>> > >>> >>> >>> >> >> > >

April 6, 2012

Re: [Pharo-project] SUnit and TestCase

by Guillermo Polito

On Fri, Apr 6, 2012 at 1:12 PM, Benjamin < benjamin.vanryseghem.pharo(a)gmail.com> wrote: > > On Apr 5, 2012, at 3:37 PM, Guillermo Polito wrote: > > > On Thu, Apr 5, 2012 at 3:17 PM, Benjamin < > benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >> per instance ? >> I you wanna know when a test instance you run started, I think there are >> better solutions than announcement. >> > > Hehe, actually, if you are the one firing the test, then you do need > nothing :). Also the tests instances are discarded to have independent > state so what I said is nonsense :). > > >> >> For me the goal of announcement is to emit, and than everyone can catch >> this information. >> > > Hmm, that's one specific use for them... You can build for example a > small application using announcements to decouple the UI from the model, > and there you probably will not make the announcer accessible for everyone. > > > It's not specific, I think it should be the default behavior. > > Because if you want to listen only the FooTestClass announcement, you can > always record yourself as a listener for all TestAnnouncement, and then > test if the announcement is relevant for you or not. > > > Because if you need to know which class emit the announcement to be able > to register, then you create a strong dependency from your class to the > test class. And this is wrong (and announcement have been introduced to > break this pattern) > But that way you are creating a strong dependency against another class like TestAnnouncement or just TestCase :P. And if you want to filter the announcements for a specific class, you will do it too! Anyway, if you're metaprogramming, then for sure are other ways to get the class without having a static reference to it. > > > Ben > > > On Thu, Apr 5, 2012 at 2:57 PM, Benjamin < >> benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> >>> Since there is an announcer per test class, you need to write something >>> like >>> >>> MyClass>>#register >>> MyTestClass announcer >>> on: TestCaseStarted send: #foo to: self. >>> >>> It means than here you force a link from MyClass to MyTestClass. >>> And if you want to be aware of all test case started, you need something >>> like >>> >>> TestCase withAllSubclasses do: [:e | e announcer >>> >>> on: TestCaseStarted send: #foo to: self ]. >>> >>> Why not using only one Announcer (and TestAnnouncer already exists and >>> is already integrated) for all test class ? >>> >>> And then you lack the possibility to subscribe to a specific one... > Maybe you can add a method in TestCase hiding the subscriptions to all the > subclasses. > > >> >>> Ben >>> >>> >>> On Apr 5, 2012, at 3:50 PM, Alexandre Bergel wrote: >>> >>> > I proposed this test announcement facilities some times ago to get >>> notified when tests are being executed and when they are done. >>> > >>> > You said: "It means that you have to know which class to register to >>> instead of which announcer." >>> > Which unit to register you mean? Yes, the one you are interested in. I >>> do not see why it break the pattern. Consider >>> TestCaseTest>>testAnnouncement. What is wrong with it? >>> > >>> > Cheers, >>> > Alexandre >>> > >>> > >>> > On 5 Apr 2012, at 06:14, Benjamin wrote: >>> > >>> >> Hello guys, >>> >> >>> >> I was implementing in Nautilus a listener to TestCaseStarted, and >>> then I figured out that each TestCase subclasses have its own Announcer. >>> >> >>> >> It means that you have to know which class to register to instead of >>> which announcer. In a way, it breaks the Observer pattern. >>> >> >>> >> Is there any good reason I am missing ? >>> >> >>> >> I think it has been done in a way you can spy a particular test >>> class, but since you have this info in the announcement itself, you can >>> always filter with this info. >>> >> Cause for me, replacing all those announcer by TestAnnouncer seems to >>> be a better solution. >>> >> >>> >> >>> >> >>> >> Thanks in advance, >>> >> >>> >> Ben >>> > >>> > -- >>> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> > Alexandre Bergel http://www.bergel.eu >>> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> > >>> > >>> > >>> > >>> > >>> > >>> >>> >>> >> >> > >

April 6, 2012

Re: [Pharo-project] SUnit and TestCase

by Benjamin

On Apr 5, 2012, at 3:37 PM, Guillermo Polito wrote: > > On Thu, Apr 5, 2012 at 3:17 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > per instance ? > I you wanna know when a test instance you run started, I think there are better solutions than announcement. > > Hehe, actually, if you are the one firing the test, then you do need nothing :). Also the tests instances are discarded to have independent state so what I said is nonsense :). > > > For me the goal of announcement is to emit, and than everyone can catch this information. > > Hmm, that's one specific use for them... You can build for example a small application using announcements to decouple the UI from the model, and there you probably will not make the announcer accessible for everyone. It's not specific, I think it should be the default behavior. Because if you want to listen only the FooTestClass announcement, you can always record yourself as a listener for all TestAnnouncement, and then test if the announcement is relevant for you or not. Because if you need to know which class emit the announcement to be able to register, then you create a strong dependency from your class to the test class. And this is wrong (and announcement have been introduced to break this pattern) Ben >> On Thu, Apr 5, 2012 at 2:57 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> Since there is an announcer per test class, you need to write something like >> >> MyClass>>#register >> MyTestClass announcer >> on: TestCaseStarted send: #foo to: self. >> >> It means than here you force a link from MyClass to MyTestClass. >> And if you want to be aware of all test case started, you need something like >> >> TestCase withAllSubclasses do: [:e | e announcer >> on: TestCaseStarted send: #foo to: self ]. >> >> Why not using only one Announcer (and TestAnnouncer already exists and is already integrated) for all test class ? >> > > And then you lack the possibility to subscribe to a specific one... Maybe you can add a method in TestCase hiding the subscriptions to all the subclasses. > >> >> Ben >> >> >> On Apr 5, 2012, at 3:50 PM, Alexandre Bergel wrote: >> >> > I proposed this test announcement facilities some times ago to get notified when tests are being executed and when they are done. >> > >> > You said: "It means that you have to know which class to register to instead of which announcer." >> > Which unit to register you mean? Yes, the one you are interested in. I do not see why it break the pattern. Consider TestCaseTest>>testAnnouncement. What is wrong with it? >> > >> > Cheers, >> > Alexandre >> > >> > >> > On 5 Apr 2012, at 06:14, Benjamin wrote: >> > >> >> Hello guys, >> >> >> >> I was implementing in Nautilus a listener to TestCaseStarted, and then I figured out that each TestCase subclasses have its own Announcer. >> >> >> >> It means that you have to know which class to register to instead of which announcer. In a way, it breaks the Observer pattern. >> >> >> >> Is there any good reason I am missing ? >> >> >> >> I think it has been done in a way you can spy a particular test class, but since you have this info in the announcement itself, you can always filter with this info. >> >> Cause for me, replacing all those announcer by TestAnnouncer seems to be a better solution. >> >> >> >> >> >> >> >> Thanks in advance, >> >> >> >> Ben >> > >> > -- >> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> > Alexandre Bergel http://www.bergel.eu >> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> > >> > >> > >> > >> > >> > >> >> >> > >

April 6, 2012

[Pharo-project] Docking windows

by Guillermo Polito

I wanted docking windows, so I did a little change over the MorphFrameGhost to support it. If anyone wants to try, filein the attached the changeset and then evaluate: UITheme currentSettings fastDragging: true. Guille

April 6, 2012

[Pharo-project] How should we tag new issues

by Guillermo Polito

I have this issue: http://code.google.com/p/pharo/issues/detail?id=5584&thanks=5584&ts=1333709… I should not tag it as critical, but it is important to newcomers who are learning to use changesets and fileouts to have this working nicely :). how should we handle the new issues tagging? - critical/showstoppers for 1.4 - non critical for 1.5 ? Guille

April 6, 2012

[Pharo-project] Pharo Kernel Reload Tests-Unix - Build # 57 - Still Unstable!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

April 6, 2012

Re: [Pharo-project] tail-like

by drush66

It kind of depends on the OS, but all of them let you subscribe to events on the files in some way. So you would subscribe with os to notify you when some file is changed in some way, keep some internal house keeping information like position up to which you have displayed info, verify that file has indeed changed, read and display new stuff, update internal info. In essence nothing substantially complicated, but windows and unix interface differs, and at least windows (never investigated unix api in more detail) requires you to dance a bit before you get some results. Such pieces of code is also often used by text editors to notify user that the file in editor has been changed from the outside. (maybe moose already has something like that?) Davorin Rusevljan http://www.cloud208.com/ ----- http://www.cloud208.com/ -- View this message in context: http://forum.world.st/tail-like-tp4535899p4537087.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 6, 2012

Re: [Pharo-project] Fwd: using the system applied proxy in unix

by Marcus Denker

On Apr 6, 2012, at 11:36 AM, Guillermo Polito wrote: > > On Apr 6, 2012, at 11:26 AM, Guillermo Polito wrote: > > > Hi, > > > > I have configured the proxy for the whole system in my ubuntu 11.10, but pharo does not want to recognize it :). If i configure the proxy again in my pharo image it works, but I don't want to have the configurations duplicated... > > > The plugin that does the detection was nover portet to Linux and Windows... so automatic proxy setting only works on the mac for now. > > Which plugin is it? > InternetConfigPlugin, the class in the image is InternetConfiguration Marcus -- Marcus Denker -- http://marcusdenker.de

April 6, 2012