- Pharo-dev - lists.pharo.org

Re: [Pharo-project] System time

by Jimmie Houchin

I downloaded the latest Pharo 1.3 and Cog vm to my Vista server. I opened up a workspace and did the following at as precisely as my hand eye coordination allow at the top of the minute shown. The first time at the bottom shows exactly identical time with the OS clock. The second time above it, show a 5 second gain in time in a little over 24 hours. I am going to let this image keep going and see how it continues. DateAndTime now. 2011-05-01T23:45:05-05:00 lost 5 seconds since the below 2011-04-30T20:16:00-05:00 opened Pharo and checked time. For me, this is now verified on 2 Windows Vista computers. One a laptop, and the other a Desktop machine I use as a server. Both are reasonably current Dells. The laptop with a duo-core processor and the desktop a quad-core processor. I have not done any attempts on any other OS. Thanks. Jimmie On 4/30/2011 12:03 PM, Jimmie Houchin wrote: > 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. > > I have not been able to find where in Pharo I can call to update the > System clock to the correct time. > > Any help greatly appreciated. > > Jimmie

May 2, 2011

[Pharo-project] right click on PluggableTreeMorph doesn't select

by Guillermo Polito

Hi! Let's say I have a PluggableTreeMorph with some options(a,b and c). Each option may show a menu when I do a right click. Buuut, If I have selected item a, and do a right clic on c, the menu shown is for a, not for c :(. I expect the right click to work on the item the click is done, not in the selected one :(. Is there a way to have this tree morph working as I want? Thanks in advance! Guille

May 2, 2011

Re: [Pharo-project] System time

by Alexandre Bergel

Strange. I cannot produce this problem on OSX. Alexandre On 30 Apr 2011, at 22:15, Jimmie Houchin wrote: > Hello, > > My OS for this application is Windows. On a freshly opened image, the image and OS time are in sync. Over a period of time the image drifted 34 seconds away from OS time. I do not know how long I had this image open, but it has been a number of days, possibly a week plus. > > I saved the image and quit. I reopened the image and did DateAndTime now and it was in sync with the OS once again. Same image, vm and OS that was out of sync by 34 seconds only one minute before. > > I have opened an image on my server which is also running the latest cog vm, the current Pharo 1.3 and Windows Vista. I am going to periodically do a DateAndTime now to log the drift if any. Prior to opening this image I updated the OS system clock with time.nist.gov which is about 1000 miles away. > > I know that within a second or so it can be subject to my coordination of doing DateAndTime now while watching my OS system clocks seconds. But 34 seconds is beyond any subjective standards. > > The only reason I discovered this was while exploring how I want to retrieve my data, act upon my data and then pause (Delay wait) until time to repeat. > dtnow := DateAndTime now. > dtnext := DateAndTime year: 2011 month: 4 day: 30 hour: 11 minute: i second: 5. "The next minute in the future" > (Delay forDuration: (dtnext - dtnow)) wait. > > I got an error, that Duration cannot be a negative number. As I processed the debugger, I saw that dtnow was greater than dtnext. I watched the OS clock and manually selected the next minute before I executed. However, I was within that 34 second window. > > So now I am exploring the problem. > > Thanks. > > Jimmie > > On 4/30/2011 5:06 PM, Alexandre Bergel wrote: >> 'Time now' gives me the same result than OSX >> >> Alexandre >> >> >> On 30 Apr 2011, at 16:15, Jimmie Houchin wrote: >> >>> On 4/30/2011 11:50 AM, StÃ©phane Ducasse wrote: >>>>> 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. >>> Pharo 1.3 and the latest Cog. >>> >>>>> 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) >>> No, that's not the problem. The OS clock is right. It's Pharo that has drifted away from correct time. Regardless it would be nice if I have to correct the OS clock, it would still be nice to resync Pharo with the OS, keep both in sync and correct. What I am wanting is simply to resync the Pharo clock with the OS clock. >>> >>> It seems that when the Pharo image is started that it gets the OS System time, but keeps its own time after that. Now I do not know the consequences of Pharo adjusting its time backward. If this isn't possible, then I might have to do some workarounds to insure that I get my data in a timely manner. >>> >>> The image I have been developing in is currently about 30 seconds ahead of the OS clock. It is on my laptop. It might be due to the laptops sleep and hibernation. I have not tested this on my server. >>> >>> That is the situation as best I know it. >>> >>> Thanks. >>> >>> Jimmie >>> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 2, 2011

Re: [Pharo-project] System time

by Andres Valloud

Does the Windows VM depend on QueryPerformanceCounter()? On 5/1/11 16:53 , Alexandre Bergel wrote: > Strange. I cannot produce this problem on OSX. > > Alexandre > > > On 30 Apr 2011, at 22:15, Jimmie Houchin wrote: > >> Hello, >> >> My OS for this application is Windows. On a freshly opened image, the image and OS time are in sync. Over a period of time the image drifted 34 seconds away from OS time. I do not know how long I had this image open, but it has been a number of days, possibly a week plus. >> >> I saved the image and quit. I reopened the image and did DateAndTime now and it was in sync with the OS once again. Same image, vm and OS that was out of sync by 34 seconds only one minute before. >> >> I have opened an image on my server which is also running the latest cog vm, the current Pharo 1.3 and Windows Vista. I am going to periodically do a DateAndTime now to log the drift if any. Prior to opening this image I updated the OS system clock with time.nist.gov which is about 1000 miles away. >> >> I know that within a second or so it can be subject to my coordination of doing DateAndTime now while watching my OS system clocks seconds. But 34 seconds is beyond any subjective standards. >> >> The only reason I discovered this was while exploring how I want to retrieve my data, act upon my data and then pause (Delay wait) until time to repeat. >> dtnow := DateAndTime now. >> dtnext := DateAndTime year: 2011 month: 4 day: 30 hour: 11 minute: i second: 5. "The next minute in the future" >> (Delay forDuration: (dtnext - dtnow)) wait. >> >> I got an error, that Duration cannot be a negative number. As I processed the debugger, I saw that dtnow was greater than dtnext. I watched the OS clock and manually selected the next minute before I executed. However, I was within that 34 second window. >> >> So now I am exploring the problem. >> >> Thanks. >> >> Jimmie >> >> On 4/30/2011 5:06 PM, Alexandre Bergel wrote: >>> 'Time now' gives me the same result than OSX >>> >>> Alexandre >>> >>> >>> On 30 Apr 2011, at 16:15, Jimmie Houchin wrote: >>> >>>> On 4/30/2011 11:50 AM, StÃ©phane Ducasse wrote: >>>>>> 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. >>>> Pharo 1.3 and the latest Cog. >>>> >>>>>> 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) >>>> No, that's not the problem. The OS clock is right. It's Pharo that has drifted away from correct time. Regardless it would be nice if I have to correct the OS clock, it would still be nice to resync Pharo with the OS, keep both in sync and correct. What I am wanting is simply to resync the Pharo clock with the OS clock. >>>> >>>> It seems that when the Pharo image is started that it gets the OS System time, but keeps its own time after that. Now I do not know the consequences of Pharo adjusting its time backward. If this isn't possible, then I might have to do some workarounds to insure that I get my data in a timely manner. >>>> >>>> The image I have been developing in is currently about 30 seconds ahead of the OS clock. It is on my laptop. It might be due to the laptops sleep and hibernation. I have not tested this on my server. >>>> >>>> That is the situation as best I know it. >>>> >>>> Thanks. >>>> >>>> Jimmie >>>> >> >> >

May 2, 2011

Re: [Pharo-project] [Metacello] Best strategy for ConfigurationOfPharo using #stable

by Mariano Martinez Peck

So.... I will add versionString: #stable To all confs directly used by ConfigurationOfPharo. But that's not enough. I should do the same to each of them...and the whole tree...shouldn't I ? Maybe if we set up this, hudson can load the latest baseline instead of #lastVersion as it is doing now... Cheers On Fri, Apr 29, 2011 at 8:34 PM, Dale Henrichs <dhenrich(a)vmware.com> wrote: > On 04/29/2011 10:10 AM, StÃ©phane Ducasse wrote: > >> dale >> >> My rule of thumb for a literal version spec is that you should >>>> use the #stable symbolic version if the project is loosely >>>> coupled to your project and a specific version otherwise. >>>> OmniBrowser tends to be loosely coupled as you are interested in >>>> getting any old version of OmniBrowser as long as it functions on >>>> the platform. >>>> >>> >>> The rule of thumb for a baseline version spec is to use #stable for >>> all projects (as long as the #stable version is defined), even >>> "tightly coupled" projects. When the baseline version is loaded, >>> you normally don't want to load the "latest code" or all of the >>> projects that you depend upon. >>> >>> The #bleedingEdge symbolic version should be used only when the >>> referenced project is part of your project family. >>> >>> When I load the baseline version for Seaside30, >>> >> >> when you say that "load the baseline": do you mean that you will get >> all the latest versions of the seaside packages? >> > > Yes, I load the baseline version of Seaside30, to pick up the most > recent checkins by the Seaside developers, so I can update the > configuration, port the changes, to GemStone and make a release. > > And when I do that, I don't want the latest OmniBrowser packages:) > > >> >> I want to load the #bleedingEdge versions of Grease, Kom, and >>> Swazoo, because they are part of the project family. I absolutely >>> don't want to load the latest OmniBrowser code, because who knows >>> what you'd get... >>> >>> So for the ConfigurationOfPharo, if you followed my rule of thumb, >>> you would create a baseline version and use the #stable version for >>> all of the projects in the baseline. In the literal version you >>> would use the explicit version, so that you'd have an explicit >>> repeatable specification for a set of projects that were known to >>> work together. >>> >> >> ok you mean that if people want the latest they load the baseline >> else they can just use a literal version and access it via #stable >> > > > I'm not sure what you mean here.... > > The pharo 1.2.2-baseline would include specs that look like this: > > spec > project: 'OB Dev' with: [ > spec > className: 'ConfigurationOfOmniBrowser'; > versionString: #stable; > ...]; > project: 'ScriptManager' with: [ > spec > className: 'ConfigurationOfScriptManager'; > versionString: #stable; > ...]; > project: 'Shout' with: [ > spec > className: 'ConfigurationOfShout'; > versionString: #stable; > ...]; > ....]. > > Loading Pharo 1.2.2-baseline would cause the #stable version for each of > those projects to be loaded ... but remember over time the #stable version > will change and incompatibilities between packages can creep in. By using > #stable versions you will be in better shape than using #bleedingEdge > because the #stable version is known to work. > > Pharo 1.2.2 (literal version) will have corresponding specs that look like > this: > > spec > project: 'OB Dev' with: '1.2.4'; > project: 'ScriptManager' with: '1.2'; > project: 'Shout' with: '1.2.2'; > ....]. > > So that you have driven a stake into the ground stating that these versions > are known to work together (have passed tests as a unit). 5 years in the > future, you will be able ot load Pharo 1.2.2 and get exactly the same > packages every time ... whereas the #stable versions may have drifted over > time ... > > If I am just bringing up a PharoCore1.2 image and I'd like to load the > Pharo dev code, I should load the #stable version of Pharo (which may be > 1.2.2 today and 1.2.3 tomorrow). > > If I want to duplicate the environment that someone is working in I will > ask them for th version of Pharo and load that explicit version to reproduce > the bug or whatever ... > > Dale > -- Mariano http://marianopeck.wordpress.com

May 2, 2011

Re: [Pharo-project] [Metacello] Best strategy for ConfigurationOfPharo using #stable

by Mariano Martinez Peck

> > Mariano, > > My rule of thumb for a literal version spec is that you should use the > #stable symbolic version if the project is loosely coupled to your project > and a specific version otherwise. OmniBrowser tends to be loosely coupled as > you are interested in getting any old version of OmniBrowser as long as it > functions on the platform. > > The rule of thumb for a baseline version spec is to use #stable for all > projects (as long as the #stable version is defined), even "tightly coupled" > projects. When the baseline version is loaded, you normally don't want to > load the "latest code" or all of the projects that you depend upon. > > The #bleedingEdge symbolic version should be used only when the referenced > project is part of your project family. > > When I load the baseline version for Seaside30, I want to load the > #bleedingEdge versions of Grease, Kom, and Swazoo, because they are part of > the project family. I absolutely don't want to load the latest OmniBrowser > code, because who knows what you'd get... > > So for the ConfigurationOfPharo, if you followed my rule of thumb, you > would create a baseline version and use the #stable version for all of the > projects in the baseline. In the literal version you would use the explicit > version, so that you'd have an explicit repeatable specification for a set > of projects that were known to work together. > Thanks Dale for the answer....Now, putting #stable in the versionString of a baseline make sense ONLY because the default is not #stable, isn't it ? I mean, if ConfigurationOfPharo >> baseline13: I am doing: project: 'OB Dev' with: [ spec className: 'ConfigurationOfOmniBrowser'; loads: #('Dev'); file: 'ConfigurationOfOmniBrowser'; repository: ' http://www.squeaksource.com/MetacelloRepository' ]; as you can see, in any baseline of ConfigurationOfPharo I set a version. Hence, if someone does ConfigurationOfPharo project version: '1.3-baseline', then Metacello will load the DEFAULT for 'ConfigurationOfOmniBrowser' which I guess it is not #stable becuase otherwise what you told me doesn't have sense. So, I guess it is #bleedingEdge? I think I have already asked this...sorry I couldn't find it in my gmail... > Developers interested in getting the "latest released version for all > projects" in ConfigurationOfPharo would load the baseline version and then > get the #stable version of all the projects for their platform ... each of > the projects was know to work by itself in an image (that's what the #stable > designation means), but the unknown is whether all of the projects work > together in image ... When you know that, you create a literal version of > ConfigurationOfPharo to commemorate that set of versions.... > > Without looking at the list of projects, it might still make sense to use > #stable in the literal version, but it would be the exception to the rule > ... > > Does this make sense to you? > > Totally :) > Dale > > -- Mariano http://marianopeck.wordpress.com

May 2, 2011

Re: [Pharo-project] I need help with 13380

by Mariano Martinez Peck

On Sun, May 1, 2011 at 10:17 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > 1.3- 13380 latest update. > This cannot be possible. The latest PharoCore 1.3 seems to be 13179 So...I guess you tried to create 13180 and you confuse 13380 with 13180 ? cheers mariano > Now I think that this is because my vm has a bug with the refresh of the > screen. if I resize it the system > looks ok. > > Stef > > > On May 1, 2011, at 11:12 PM, Igor Stasenko wrote: > > > On 1 May 2011 22:02, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Hi guys > >> > >> I need help. > >> I do not know why the image is so slow at startup and also why I cannot > really bring an interrupt. > >> Tomorrow I'm traveling. So no time to look at that. > >> > > > > It would help to help you, if you elaborate, what 13380 means :) > > > >> Stef > >> > > > > > > > > -- > > Best regards, > > Igor Stasenko AKA sig. > > > > > -- Mariano http://marianopeck.wordpress.com

May 2, 2011

Re: [Pharo-project] strange loop

by Igor Stasenko

On 1 May 2011 22:16, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On May 1, 2011, at 11:06 PM, Igor Stasenko wrote: > >> On 1 May 2011 21:38, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> this is strange >>> >>> I was trying to code a simple list of method browser and my browser seems to >>> >>> MorphExtension>>valueOfProperty: aSymbol >>> Â Â Â Â "answer the value of the receiver's property named aSymbol" >>> Â Â Â Â ^ extension ifNotNil: [extension valueOfProperty: aSymbol] >>> >> hmm.. i have different implementation here: >> >> valueOfProperty: aSymbol >> "answer the value of the receiver's property named aSymbol" >> Â Â Â ^ self >> Â Â Â Â Â Â Â valueOfProperty: aSymbol >> Â Â Â Â Â Â Â ifAbsent: [] >> >> and there is no 'extension' ivar in MorphExtension class. >> Or you changed something there? > > > Not that I know. > I was just in plain 13380 > [OT].. wow.. my image is already 300 updates behind.. What the ...! 300 updates. I mean 300. updates!!! And that is in scope of 1.3 development. :))) > >> >>> I end up in a endless loop >>> >>> update: aParameter >>> >>> Â Â Â Â |state| >>> Â Â Â Â aParameter Â ifNil: [^self]. >>> Â Â Â Â getLabelSelector ifNotNil: [ >>> Â Â Â Â Â Â Â Â aParameter == getLabelSelector ifTrue: [ >>> Â Â Â Â Â Â Â Â Â Â Â Â (self labelMorph respondsTo: #font) >>> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ifTrue: [self label: (model perform: getLabelSelector) font: self labelMorph font] >>> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ifFalse: [self label: (model perform: getLabelSelector)]]]. >>> Â Â Â Â state := self getModelState. >>> Â Â Â Â (state ~= (self valueOfProperty: #lastState) or: [ >>> Â Â Â Â Â Â Â Â Â Â Â Â ^^^ >>> >>> when I inspect self I get a PluggableButtonMorph >>> but the method shown in the debugger is MoprhExtension?????? >>> >>> Â Â Â Â getStateSelector isNil and: [aParameter == #onOffColor]]) >>> Â Â Â Â Â Â Â Â ifTrue: [self color: self colorToUse. >>> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â self setProperty: #lastState toValue: state]. >>> Â Â Â Â aParameter == getEnabledSelector ifTrue: [^self enabled: (model perform: getEnabledSelector)]. >>> Â Â Â Â getColorSelector ifNotNil: [ | cc | >>> Â Â Â Â Â Â Â Â color = (cc := model perform: getColorSelector) >>> Â Â Â Â Â Â Â Â Â Â Â Â ifFalse: [ >>> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â color := cc. >>> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â self onColor: color offColor: color. >>> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â self changed ]]. >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. > > > -- Best regards, Igor Stasenko AKA sig.

May 1, 2011

Re: [Pharo-project] I need help with 13380

by Igor Stasenko

On 1 May 2011 22:02, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I need help. > I do not know why the image is so slow at startup and also why I cannot really bring an interrupt. > Tomorrow I'm traveling. So no time to look at that. > It would help to help you, if you elaborate, what 13380 means :) > Stef > -- Best regards, Igor Stasenko AKA sig.

May 1, 2011

Re: [Pharo-project] suspicion update: method in MorphExtension

by Igor Stasenko

Hey, where you got that? In my image ( Pharo1.3a Latest update: #13097 ) there is no such method (MorphExtension>>#update: ) at all. On 1 May 2011 21:20, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I have a problem with a PluggableButtonMorph and I end up in this > > MorpExtension>>update: aParameter > > Â Â Â Â |state| > Â Â Â Â aParameter Â ifNil: [^self]. > Â Â Â Â getLabelSelector ifNotNil: [ > Â Â Â Â Â Â Â Â aParameter == getLabelSelector ifTrue: [ > Â Â Â Â Â Â Â Â Â Â Â Â (self labelMorph respondsTo: #font) > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ifTrue: [self label: (model perform: getLabelSelector) font: self labelMorph font] > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ifFalse: [self label: (model perform: getLabelSelector)]]]. > Â Â Â Â state := self getModelState. > Â Â Â Â (state ~= (self valueOfProperty: #lastState) or: [ > Â Â Â Â getStateSelector isNil and: [aParameter == #onOffColor]]) > Â Â Â Â Â Â Â Â ifTrue: [self color: self colorToUse. > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â self setProperty: #lastState toValue: state]. > Â Â Â Â aParameter == getEnabledSelector ifTrue: [^self enabled: (model perform: getEnabledSelector)]. > Â Â Â Â getColorSelector ifNotNil: [ | cc | > Â Â Â Â Â Â Â Â color = (cc := model perform: getColorSelector) > Â Â Â Â Â Â Â Â Â Â Â Â ifFalse: [ > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â color := cc. > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â self onColor: color offColor: color. > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â self changed ]]. > > To me it looks suspicious that MorphExtension does that for all the morph.... > > Stef > -- Best regards, Igor Stasenko AKA sig.

May 1, 2011