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

Re: [Pharo-project] System time

by StÃ©phane Ducasse

> I am developing a time sensitive application. I poll a server every minute for new data. The data is time sensitive and the sooner I can get the data to the release of the data the better. > > I have noticed that Pharo's system time drifts away from the OS system time. I would really like the Pharo system time to be the correct time. do you have a repeatable scenario? VM Image information. > I have not been able to find where in Pharo I can call to update the System clock to the correct time. you can use OSProcess (only mac and linux) > > Any help greatly appreciated. > > Jimmie >

April 30, 2011

Re: [Pharo-project] I am the only one who finds #assert:equals: oppostite to expected?

by Sean Allen

You are not alone on this. On Sat, Apr 30, 2011 at 10:20 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Hi guys. I always code my tests something like this: > > testBlah > | universalAnswer | > universalAnswer := 30. > universalAnswer := universalAnswer + 11. > self assert: universalAnswer equals: 42. > > In this case, 42 is the "expected" and "universalAnswer" is the "actual" > value. > I feel weird writing like this: > > self assert: 42 equals: universalAnswer. > > I don't know why...but I do..the same as when doing should: [] raise: > Error. > In that case you put the "actual" first and the "expected" at the end... > > ok....the "problem" is that assert:equals: is in fact: asserts: expected > equals: actual instead of > asserts: actual equals: expected > > So, with my test I would receive a description in the debugger that says > "'Expected 41 but was 42.'" > which is completely the opposite. Of course, if I write my tests in the way > I don't like, that is: > self assert: 42 equals: universalAnswer. > > then i got the correct message "'Expected 42 but was 41.'" > > I don't pretend pharo change this because I guess it is standard, and blah > blah blah. But senders of #assert:equals: should both, some written as mine > (so the message is incorrect for them) and some correct. > > In addition, I think it is a problem of the selector name. If we could make > it clearer, the won't be necessary to confuse "actual" with "expected". > > Cheers > > -- > Mariano > http://marianopeck.wordpress.com > >

April 30, 2011

Re: [Pharo-project] I am the only one who finds #assert:equals: oppostite to expected?

by StÃ©phane Ducasse

mariano since the API is the same I guess that we can change to get the behavior you expect. I'm still convinced that we should develop another testing framework because just to be compatible with SUnit we are bound to never change. At brest I discuss and gave a list of features to niall and I still do not know what happened to them.... Stef > Hi guys. I always code my tests something like this: > > testBlah > | universalAnswer | > universalAnswer := 30. > universalAnswer := universalAnswer + 11. > self assert: universalAnswer equals: 42. > > In this case, 42 is the "expected" and "universalAnswer" is the "actual" value. > I feel weird writing like this: > > self assert: 42 equals: universalAnswer. > > I don't know why...but I do..the same as when doing should: [] raise: Error. > In that case you put the "actual" first and the "expected" at the end... > > ok....the "problem" is that assert:equals: is in fact: asserts: expected equals: actual instead of > asserts: actual equals: expected > > So, with my test I would receive a description in the debugger that says "'Expected 41 but was 42.'" > which is completely the opposite. Of course, if I write my tests in the way I don't like, that is: > self assert: 42 equals: universalAnswer. > > then i got the correct message "'Expected 42 but was 41.'" > > I don't pretend pharo change this because I guess it is standard, and blah blah blah. But senders of #assert:equals: should both, some written as mine (so the message is incorrect for them) and some correct. > > In addition, I think it is a problem of the selector name. If we could make it clearer, the won't be necessary to confuse "actual" with "expected". > > Cheers > > -- > Mariano > http://marianopeck.wordpress.com >

April 30, 2011

Re: [Pharo-project] HelpBrowser takes too much time to open

by Alexandre Bergel

> in fact cannot the cache be class side? beucase now each time you do HelpBrowser open, you compute again the cache....but I am not sure if they should change amont different opened browsers Could be. It is important to have a scenario. The problem is getting the pragmas from the whole system. If you put the cache on the class side, then you will indeed need to reset the cache, by registering to the system events. The reset has to be performed at each installation of a new help. This is a bit more work. Shall we do to that direction? I think it makes sense. Alexandre > > > On Sat, Apr 30, 2011 at 5:07 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Yes, but this depends what is the expected behavior of the browser. I like the Agile approach that says you're done when all the tests are green :-) > > Alexandre > > > On 30 Apr 2011, at 10:02, Mariano Martinez Peck wrote: > > > Yes, but I have no idea. Another thing is that now HelpBrowser should implement something like: > > > > HelpBrowser >> cleanUp > > self resetChache > > > > >> resetCache > > helpTopicCache := nil > > > > So that the class is automatically cleaned in #cleanUpForRelease and friends... right now since Smalltalk cleanUp sends to all classes which understand such method, just implemented that should be enough. > > > > Cheers > > > > Mariano > > > > > > On Sat, Apr 30, 2011 at 4:58 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > You're right Mariano. However, I do not know if the help browser gets updated if you have a browser opened and add a new help in the system. In any case, this is a requirement that is not formalized by the unit tests. > > > > I think that ideally, the reset cache should be done when receiving an event of a class creation that is a help. > > > > Alexandre > > > > > > On 30 Apr 2011, at 09:29, Mariano Martinez Peck wrote: > > > > > Cool! Thanks Alexandre. Now...the problem with the cache is always the same...when to invalidate them. > > > In this case, when do I need to set helpTopicCache to nil. I guess that if you create a help, then it is "automatically" detected when you open the browser. > > > Now, you have to explicitly flush the cache, haven't you? So...is there some documentation of HelpSystem that should be updated to reflect that ? > > > > > > Thanks > > > > > > On Sat, Apr 30, 2011 at 3:15 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > > > MessageTally time: [HelpBrowser open] between 2 seconds in Cog and with a regular VM between 6 and 8.... > > > > is there an easy way to improve it ? > > > > > > > > Alexandre, do you want another place where to put a cache like Metacello's currentVersion? ;) > > > > > > :-) > > > Sure. Easy. > > > > > > SystemHelp>>allSystemHelpPragmas takes time. When you open a browser, the method HelpBrowser>>open is called once and SystemHelp>>allSystemHelpPragmas twice. Easy to suspect that a cache is missing. > > > > > > So, if you define > > > -=-=-=-=-=-=-=-=-= > > > HelpBrowser>>helpTopic > > > ^ helpTopicCache ifNil: [ helpTopicCache := rootTopic asHelpTopic ] > > > -=-=-=-=-=-=-=-=-= > > > > > > and adapt HelpBrowser>>refresh you win 50% of execution time. > > > > > > Here is it: > > > > > > > > > http://code.google.com/p/pharo/issues/detail?id=4126 > > > > > > Before this fix, I have: > > > [HelpBrowser open] timeToRun > > > => 6099 > > > > > > After the fix I have: > > > [HelpBrowser open] timeToRun > > > => 3094 > > > > > > Naturally, tests are kept green. > > > > > > Cheers, > > > Alexandre > > > > > > -- > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > Alexandre Bergel http://www.bergel.eu > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Mariano > > > http://marianopeck.wordpress.com > > > > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 30, 2011

Re: [Pharo-project] HelpBrowser takes too much time to open

by laurent laffont

Note that HelpBrowser has a "Refresh" button so it should clear the cache. Laurent On Sat, Apr 30, 2011 at 4:27 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > in fact cannot the cache be class side? beucase now each time you do > HelpBrowser open, you compute again the cache....but I am not sure if they > should change amont different opened browsers > > cheers > > mariano > > > On Sat, Apr 30, 2011 at 5:07 PM, Alexandre Bergel <alexandre.bergel(a)me.com > > wrote: > >> Yes, but this depends what is the expected behavior of the browser. I like >> the Agile approach that says you're done when all the tests are green :-) >> >> Alexandre >> >> >> On 30 Apr 2011, at 10:02, Mariano Martinez Peck wrote: >> >> > Yes, but I have no idea. Another thing is that now HelpBrowser should >> implement something like: >> > >> > HelpBrowser >> cleanUp >> > self resetChache >> > >> > >> resetCache >> > helpTopicCache := nil >> > >> > So that the class is automatically cleaned in #cleanUpForRelease and >> friends... right now since Smalltalk cleanUp sends to all classes which >> understand such method, just implemented that should be enough. >> > >> > Cheers >> > >> > Mariano >> > >> > >> > On Sat, Apr 30, 2011 at 4:58 PM, Alexandre Bergel < >> alexandre.bergel(a)me.com> wrote: >> > You're right Mariano. However, I do not know if the help browser gets >> updated if you have a browser opened and add a new help in the system. In >> any case, this is a requirement that is not formalized by the unit tests. >> > >> > I think that ideally, the reset cache should be done when receiving an >> event of a class creation that is a help. >> > >> > Alexandre >> > >> > >> > On 30 Apr 2011, at 09:29, Mariano Martinez Peck wrote: >> > >> > > Cool! Thanks Alexandre. Now...the problem with the cache is always the >> same...when to invalidate them. >> > > In this case, when do I need to set helpTopicCache to nil. I guess >> that if you create a help, then it is "automatically" detected when you open >> the browser. >> > > Now, you have to explicitly flush the cache, haven't you? So...is >> there some documentation of HelpSystem that should be updated to reflect >> that ? >> > > >> > > Thanks >> > > >> > > On Sat, Apr 30, 2011 at 3:15 AM, Alexandre Bergel < >> alexandre.bergel(a)me.com> wrote: >> > > > MessageTally time: [HelpBrowser open] between 2 seconds in Cog and >> with a regular VM between 6 and 8.... >> > > > is there an easy way to improve it ? >> > > > >> > > > Alexandre, do you want another place where to put a cache like >> Metacello's currentVersion? ;) >> > > >> > > :-) >> > > Sure. Easy. >> > > >> > > SystemHelp>>allSystemHelpPragmas takes time. When you open a browser, >> the method HelpBrowser>>open is called once and >> SystemHelp>>allSystemHelpPragmas twice. Easy to suspect that a cache is >> missing. >> > > >> > > So, if you define >> > > -=-=-=-=-=-=-=-=-= >> > > HelpBrowser>>helpTopic >> > > ^ helpTopicCache ifNil: [ helpTopicCache := rootTopic >> asHelpTopic ] >> > > -=-=-=-=-=-=-=-=-= >> > > >> > > and adapt HelpBrowser>>refresh you win 50% of execution time. >> > > >> > > Here is it: >> > > >> > > >> > > http://code.google.com/p/pharo/issues/detail?id=4126 >> > > >> > > Before this fix, I have: >> > > [HelpBrowser open] timeToRun >> > > => 6099 >> > > >> > > After the fix I have: >> > > [HelpBrowser open] timeToRun >> > > => 3094 >> > > >> > > Naturally, tests are kept green. >> > > >> > > Cheers, >> > > Alexandre >> > > >> > > -- >> > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> > > Alexandre Bergel http://www.bergel.eu >> > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > -- >> > > Mariano >> > > http://marianopeck.wordpress.com >> > > >> > >> > -- >> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> > Alexandre Bergel http://www.bergel.eu >> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > -- >> > Mariano >> > http://marianopeck.wordpress.com >> > >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > >

April 30, 2011

Re: [Pharo-project] Tutorial on Announcements

by Alexandre Bergel

Excellent! We should see how to integrate this into PBE Alexandre On 29 Apr 2011, at 21:57, DougEdmunds wrote: > http://dougedmunds.com/pmwiki.php?n=Pharo.AnnouncementsTutorial > > What you can get out of this tutorial and sample code > > How to use Announcements > Ideas on building a GUI > Associating buttons with actions > Pulling text out of a text field morph. > Convert text to numbers using exception handling > How to create and exit an endless loop > Setting process priority > > -- > View this message in context: http://forum.world.st/Tutorial-on-Announcements-tp3485040p3485040.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 30, 2011

Re: [Pharo-project] HelpBrowser takes too much time to open

by Alexandre Bergel

Yes, but this depends what is the expected behavior of the browser. I like the Agile approach that says you're done when all the tests are green :-) Alexandre On 30 Apr 2011, at 10:02, Mariano Martinez Peck wrote: > Yes, but I have no idea. Another thing is that now HelpBrowser should implement something like: > > HelpBrowser >> cleanUp > self resetChache > > >> resetCache > helpTopicCache := nil > > So that the class is automatically cleaned in #cleanUpForRelease and friends... right now since Smalltalk cleanUp sends to all classes which understand such method, just implemented that should be enough. > > Cheers > > Mariano > > > On Sat, Apr 30, 2011 at 4:58 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > You're right Mariano. However, I do not know if the help browser gets updated if you have a browser opened and add a new help in the system. In any case, this is a requirement that is not formalized by the unit tests. > > I think that ideally, the reset cache should be done when receiving an event of a class creation that is a help. > > Alexandre > > > On 30 Apr 2011, at 09:29, Mariano Martinez Peck wrote: > > > Cool! Thanks Alexandre. Now...the problem with the cache is always the same...when to invalidate them. > > In this case, when do I need to set helpTopicCache to nil. I guess that if you create a help, then it is "automatically" detected when you open the browser. > > Now, you have to explicitly flush the cache, haven't you? So...is there some documentation of HelpSystem that should be updated to reflect that ? > > > > Thanks > > > > On Sat, Apr 30, 2011 at 3:15 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > > MessageTally time: [HelpBrowser open] between 2 seconds in Cog and with a regular VM between 6 and 8.... > > > is there an easy way to improve it ? > > > > > > Alexandre, do you want another place where to put a cache like Metacello's currentVersion? ;) > > > > :-) > > Sure. Easy. > > > > SystemHelp>>allSystemHelpPragmas takes time. When you open a browser, the method HelpBrowser>>open is called once and SystemHelp>>allSystemHelpPragmas twice. Easy to suspect that a cache is missing. > > > > So, if you define > > -=-=-=-=-=-=-=-=-= > > HelpBrowser>>helpTopic > > ^ helpTopicCache ifNil: [ helpTopicCache := rootTopic asHelpTopic ] > > -=-=-=-=-=-=-=-=-= > > > > and adapt HelpBrowser>>refresh you win 50% of execution time. > > > > Here is it: > > > > > > http://code.google.com/p/pharo/issues/detail?id=4126 > > > > Before this fix, I have: > > [HelpBrowser open] timeToRun > > => 6099 > > > > After the fix I have: > > [HelpBrowser open] timeToRun > > => 3094 > > > > Naturally, tests are kept green. > > > > Cheers, > > Alexandre > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 30, 2011

Re: [Pharo-project] I am the only one who finds #assert:equals: oppostite to expected?

by Peter Hugosson-Miller

It feels backwards to me too, in the same way that "one plus one equals two" feels more natural than "two equals one plus one". -- Cheers, Peter. On 30 apr 2011, at 16:20, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi guys. I always code my tests something like this: > > testBlah > | universalAnswer | > universalAnswer := 30. > universalAnswer := universalAnswer + 11. > self assert: universalAnswer equals: 42. > > In this case, 42 is the "expected" and "universalAnswer" is the "actual" value. > I feel weird writing like this: > > self assert: 42 equals: universalAnswer. > > I don't know why...but I do..the same as when doing should: [] raise: Error. > In that case you put the "actual" first and the "expected" at the end... > > ok....the "problem" is that assert:equals: is in fact: asserts: expected equals: actual instead of > asserts: actual equals: expected > > So, with my test I would receive a description in the debugger that says "'Expected 41 but was 42.'" > which is completely the opposite. Of course, if I write my tests in the way I don't like, that is: > self assert: 42 equals: universalAnswer. > > then i got the correct message "'Expected 42 but was 41.'" > > I don't pretend pharo change this because I guess it is standard, and blah blah blah. But senders of #assert:equals: should both, some written as mine (so the message is incorrect for them) and some correct. > > In addition, I think it is a problem of the selector name. If we could make it clearer, the won't be necessary to confuse "actual" with "expected". > > Cheers > > -- > Mariano > http://marianopeck.wordpress.com >

April 30, 2011

Re: [Pharo-project] HelpBrowser takes too much time to open

by Alexandre Bergel

You're right Mariano. However, I do not know if the help browser gets updated if you have a browser opened and add a new help in the system. In any case, this is a requirement that is not formalized by the unit tests. I think that ideally, the reset cache should be done when receiving an event of a class creation that is a help. Alexandre On 30 Apr 2011, at 09:29, Mariano Martinez Peck wrote: > Cool! Thanks Alexandre. Now...the problem with the cache is always the same...when to invalidate them. > In this case, when do I need to set helpTopicCache to nil. I guess that if you create a help, then it is "automatically" detected when you open the browser. > Now, you have to explicitly flush the cache, haven't you? So...is there some documentation of HelpSystem that should be updated to reflect that ? > > Thanks > > On Sat, Apr 30, 2011 at 3:15 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > MessageTally time: [HelpBrowser open] between 2 seconds in Cog and with a regular VM between 6 and 8.... > > is there an easy way to improve it ? > > > > Alexandre, do you want another place where to put a cache like Metacello's currentVersion? ;) > > :-) > Sure. Easy. > > SystemHelp>>allSystemHelpPragmas takes time. When you open a browser, the method HelpBrowser>>open is called once and SystemHelp>>allSystemHelpPragmas twice. Easy to suspect that a cache is missing. > > So, if you define > -=-=-=-=-=-=-=-=-= > HelpBrowser>>helpTopic > ^ helpTopicCache ifNil: [ helpTopicCache := rootTopic asHelpTopic ] > -=-=-=-=-=-=-=-=-= > > and adapt HelpBrowser>>refresh you win 50% of execution time. > > Here is it: > > > http://code.google.com/p/pharo/issues/detail?id=4126 > > Before this fix, I have: > [HelpBrowser open] timeToRun > => 6099 > > After the fix I have: > [HelpBrowser open] timeToRun > => 3094 > > Naturally, tests are kept green. > > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 30, 2011

Re: [Pharo-project] squeaksource Seaside30 repo out of sync

by Dale Henrichs

Yanni, We have had a bit of a dance lately with packages in the Seaside30 repo and the configuration. I don't know the actual details, but at various points in time over the last month those "mystery packages" have appeared, disappeared, reappeared, then disappeared again and I was lucky enough to be updating the config for 3.0.5 work at each of those points? The "mystery packages" are not intended to go into the 3.0.5 release, so they can be safely ignored. I think the can be found in the SeasideWIP (not sure of name) repo, but I haven't looked. Since the Seaside builds load the latest packages so they pick up whatever is in the repository ... Dale On Apr 29, 2011, at 5:18 PM, Yanni Chiu wrote: > When I look at the latest version of Seaside-Tests-Core at > squeaksource.com, and when I look at the repo in-image in a Metacello > browser, the latest version is: > Seaside-Tests-Core-lr.219 > > However, version 305 of ConfigurationOfSeaside30 lists the version as: > Seaside-Tests-Core-as.220 > > I cannot see the "as.220" version. > > Also, the build at http://jenkins.lukas-renggli.ch/job/Seaside%203.0/ > seems to have picked up the "as.220" version. But I don't see > ConfigurationOfSeaside30 being used to build that image. > > Does anyone else see the same thing, or know what's going on? > >

April 30, 2011