- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Some questions about omnibroser framework

by aizcorbe

Great, i'll post this issues there, thanks a lot. cheers HernÃ¡n Morales Durand wrote: > > http://groups.google.com/group/omnibrowser-dev > > -- View this message in context: http://forum.world.st/Some-questions-about-omnibroser-framework-tp3173047p3… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 4, 2011

Re: [Pharo-project] Some questions about omnibroser framework

by HernÃ¡n Morales Durand

http://groups.google.com/group/omnibrowser-dev 2011/1/4 aizcorbe <juansebastian.aizcorbe(a)gmail.com>: > > Not really, i couldn't find any OmniBrowser specific mailing list, i found > this http://mail.wiresong.ca/mailman/listinfo/ob-dev but seems to be > offline. Â If you know some other place where omnibrowser people are, please > tell me. > > Cheers > > > > > StÃ©phane Ducasse wrote: >> >> hi juan sebastien >> >> did you try to send this mail to the ob mailing-list? >> >> Stef >> On Jan 4, 2011, at 6:12 AM, aizcorbe wrote: >> >> > > -- > View this message in context: http://forum.world.st/Some-questions-about-omnibroser-framework-tp3173047p3… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- HernÃ¡n Morales Information Technology Manager, Institute of Veterinary Genetics. National Scientific and Technical Research Council (CONICET). La Plata (1900), Buenos Aires, Argentina. Telephone: +54 (0221) 421-1799. Internal: 422 Fax: 425-7980 or 421-1799.

Jan. 4, 2011

Re: [Pharo-project] Some questions about omnibroser framework

by aizcorbe

Not really, i couldn't find any OmniBrowser specific mailing list, i found this http://mail.wiresong.ca/mailman/listinfo/ob-dev but seems to be offline. If you know some other place where omnibrowser people are, please tell me. Cheers StÃ©phane Ducasse wrote: > > hi juan sebastien > > did you try to send this mail to the ob mailing-list? > > Stef > On Jan 4, 2011, at 6:12 AM, aizcorbe wrote: > > -- View this message in context: http://forum.world.st/Some-questions-about-omnibroser-framework-tp3173047p3… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 4, 2011

Re: [Pharo-project] Pharo and CommandShell on OSX ?

by Igor Stasenko

On 4 January 2011 17:34, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Jan 4, 2011, at 4:25 AM, David T. Lewis wrote: > >> On Mon, Jan 03, 2011 at 06:55:45PM -0800, Stef T wrote: >>> Hello Everyone, >>> Â So, long time squeaker, first time pharo(er ?). Please don't hold this against me ;) >>> >>> Â I am trying to get CommandShell loaded into Pharo (using the Seaside Image) via Monticello. I have tried this on Pharo 1.1/1.1.1/1.2 for the record (same thing). I skip past the MVC/Morphic errors about PluggableList etc, and I can get the command shell to pop-up, however, two things happen; >>> >> >> The CommandShell package on SqueakSource is also now broken down >> into sub-packages, so you can load the individual parts if you want. >> But just proceding through the MVC warnings as you did is harmless. >> >>> Â 1) CommandShell complains about AioPlugin not being present and that it will use the 'old slow' way. That's fine, it's merely a warning >> >> AFAIK, noone has tried building the AioPlugin for Mac, so you will get this >> warning when running on a Mac. But as you say, it's just a warning. > > I imagine that we will see that with igor and the automatic build too. > was this plugin included into standard vms once before? because currently its not and i don't remember if i built VMs it . -- Best regards, Igor Stasenko AKA sig.

Jan. 4, 2011

[Pharo-project] SqueakSSL Plugin for Mac OS X

by Sven Van Caekenberghe

Hi, Has anyone got the Squeak SSL plugin [1] to work on Mac OS X, more specifically for the Cog VM family, Pharo 1.1.1 or later and Mac OS X 10.6.5 ? If not, is there some how to guide on building plugins ? TIA, Sven [1] http://www.squeaksource.com/SqueakSSL

Jan. 4, 2011

Re: [Pharo-project] Issue 3499 in pharo: FixUnderscores (package & instructions) out of date

by pharo＠googlecode.com

Comment #12 on issue 3499 by sean.p.denigris: FixUnderscores (package & instructions) out of date http://code.google.com/p/pharo/issues/detail?id=3499 It seemed like the consensus is that FixUnderscores leads to code that's not properly versioned and should be removed from core. Why include instructions for something we don't want people to use?

Jan. 4, 2011

Re: [Pharo-project] Issue 3498 in pharo: remove:ifAbsent: in linked list leads to interruption/sync problems

by pharo＠googlecode.com

Comment #10 on issue 3498 by stephane.ducasse: remove:ifAbsent: in linked list leads to interruption/sync problems http://code.google.com/p/pharo/issues/detail?id=3498 adrian: I'll try that... But I still don't understand why the change in Pharo that makes LinkedList>>remove:ifAbsent: non thread safe can cause the problem since this code is executed by the timerEvent process, which runs at the highest priority. This process should never be suspended during the execution of remove:ifAbsent:. What do I miss? Andreas: The problem isn't thread-safety, at least in the classical definition. What happens is that if you're removing processes by using LinkedList>>remove: you are subject to a race condition where the semaphore gets signaled *while* you are removing the the process. Obviously, hillarity ensues at this point, which is why I made primitive suspend do the Right Thing (i.e., remove the process primitively). There are two parameters which affect if you're likely to see the effect or not: One is the number of suspension points (real sends) in the method. The more you have, the more likely you're affected. The second one is whether the method can tolerate having the process removed "underneith its feet". Both are far worse in Pharo.

Jan. 4, 2011

Re: [Pharo-project] Pharo and CommandShell on OSX ?

by StÃ©phane Ducasse

> > >> On Mon, Jan 03, 2011 at 06:55:45PM -0800, Stef T wrote: >>> 1) CommandShell complains about AioPlugin not being present and that it will use the 'old slow' way. That's fine, it's merely a warning >> >> AFAIK, noone has tried building the AioPlugin for Mac, so you will get this >> warning when running on a Mac. But as you say, it's just a warning. > > Is there a pointer for the source code ? I am pretty handy with Xcode and don't mind giving it a whirl ;) good there is a gitorious account for the vm and we would enjoy that people can contribute via there. http://gitorious.org/cogvm http://gitorious.org/squeak-vm > >> >>> but >>> 2) None of the commands get executed. If I try the stuff which will eval inside squeak/pharo, then that's fine (Eg; stdout nextPutAll: 'hello world'; cr.). However, if I try a command such as 'ls' or 'who', all hell breaks lose. stack trace follows :) >>> >>> If I am doing anything obviously wrong, please feel free to hit me over the head :) >> >> Nope, it's not you, it's the plugin included with your VM. Some >> of the Mac VMs in circulation were accidentally built with a very >> out of date version of the OSProcessPlugin. Apparently you have >> one of them, and it will definitely not work. But I think there >> is a newer version (4.2.5 IIRC) that has the up to date plugin >> that works properly on Mac. >> > > Hrm, I am using the OSProcess from squeaksource .59. The version history says > > Name: OSProcess-dtl.59 > Author: dtl > Time: 28 November 2010, 8:43:48.839 pm > UUID: bd5d2b4e-efbd-4091-ac0a-d0bd7af64b2c > > surely this is 'new enough' ? Is there a known 'stable' version you would suggest ? > > regards > S. > >> Dave >> >> >>> >>> Regards >>> S. >>> >>> >>> >>> >>> 3 January 2011 6:49:43 pm >>> >>> VM: Mac OS - intel - 1065 - Squeak3.8.1 of '28 Aug 2006' [latest update: #6747] Squeak VM 4.2.4b1 >>> Image: Pharo-1.1-11406-rc3 [Latest update: #11406] >>> >>> SecurityManager state: >>> Restricted: false >>> FileAccess: true >>> SocketAccess: true >>> Working Dir /Users/stef/squeak/SeaSide-3.0 >>> Trusted Dir /foobar/tooBar/forSqueak/bogus >>> Untrusted Dir /Users/stef/Library/Preferences/Squeak/Internet/My Squeak >>> >>> UndefinedObject(Object)>>mustBeBooleanIn: >>> Receiver: nil >>> Arguments and temporary variables: >>> context: BufferedAsyncFileReadStream>>moveAvailableDataFrom: >>> proceedValue: nil >>> Receiver's instance variables: >>> nil >>> >>> UndefinedObject(Object)>>mustBeBoolean >>> Receiver: nil >>> Arguments and temporary variables: >>> >>> Receiver's instance variables: >>> nil >>> >>> BufferedAsyncFileReadStream>>moveAvailableDataFrom: >>> Receiver: BufferedAsyncFileReadStream: 'pipeReader' >>> Arguments and temporary variables: >>> sqFile: #[48 205 236 155 72 91 120 160 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0] >>> bufferSize: 1000 >>> buffer: '...etc... >>> count: #(0) >>> Receiver's instance variables: >>> >>> >>> BufferedAsyncFileReadStream>>moveAvailableDataToBuffer >>> Receiver: BufferedAsyncFileReadStream: 'pipeReader' >>> Arguments and temporary variables: >>> >>> Receiver's instance variables: >>> >>> >>> BufferedAsyncFileReadStream>>update: >>> Receiver: BufferedAsyncFileReadStream: 'pipeReader' >>> Arguments and temporary variables: >>> aParameter: a PseudoAioEventHandler >>> Receiver's instance variables: >>> >>> >>> [] in PseudoAioEventHandler(Object)>>changed: >>> Receiver: a PseudoAioEventHandler >>> Arguments and temporary variables: >>> aParameter: BufferedAsyncFileReadStream: 'pipeReader' >>> aDependent: a PseudoAioEventHandler >>> Receiver's instance variables: >>> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >>> >>> DependentsArray>>do: >>> Receiver: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>> Arguments and temporary variables: >>> aBlock: [:aDependent | aDependent update: aParameter] >>> dep: BufferedAsyncFileReadStream: 'pipeReader' >>> i: 1 >>> iLimiT: 1 >>> Receiver's instance variables: >>> a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>> >>> PseudoAioEventHandler(Object)>>changed: >>> Receiver: a PseudoAioEventHandler >>> Arguments and temporary variables: >>> aParameter: a PseudoAioEventHandler >>> Receiver's instance variables: >>> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >>> >>> PseudoAioEventHandler(Object)>>changed >>> Receiver: a PseudoAioEventHandler >>> Arguments and temporary variables: >>> >>> Receiver's instance variables: >>> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >>> >>> [] in [] in PseudoAioEventHandler>>eventGeneratorProcess >>> Receiver: a PseudoAioEventHandler >>> Arguments and temporary variables: >>> d: a Delay(125 msecs) >>> Receiver's instance variables: >>> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >>> >>> BlockClosure>>repeat >>> Receiver: [self changed. >>> d wait] >>> Arguments and temporary variables: >>> >>> Receiver's instance variables: >>> outerContext: [] in PseudoAioEventHandler>>eventGeneratorProcess >>> startpc: 59 >>> numArgs: 0 >>> >>> [] in PseudoAioEventHandler>>eventGeneratorProcess >>> Receiver: a PseudoAioEventHandler >>> Arguments and temporary variables: >>> d: a Delay(125 msecs) >>> Receiver's instance variables: >>> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >>> >>> [] in BlockClosure>>newProcess >>> Receiver: [[self changed. >>> d wait] repeat] >>> Arguments and temporary variables: >>> >>> Receiver's instance variables: >>> outerContext: PseudoAioEventHandler>>eventGeneratorProcess >>> startpc: 54 >>> numArgs: 0 >>> >>> >>> --- The full stack --- >>> UndefinedObject(Object)>>mustBeBooleanIn: >>> UndefinedObject(Object)>>mustBeBoolean >>> BufferedAsyncFileReadStream>>moveAvailableDataFrom: >>> BufferedAsyncFileReadStream>>moveAvailableDataToBuffer >>> BufferedAsyncFileReadStream>>update: >>> [] in PseudoAioEventHandler(Object)>>changed: >>> DependentsArray>>do: >>> PseudoAioEventHandler(Object)>>changed: >>> PseudoAioEventHandler(Object)>>changed >>> [] in [] in PseudoAioEventHandler>>eventGeneratorProcess >>> BlockClosure>>repeat >>> [] in PseudoAioEventHandler>>eventGeneratorProcess >>> [] in BlockClosure>>newProcess >>> >> > >

Jan. 4, 2011

Re: [Pharo-project] Pharo and CommandShell on OSX ?

by StÃ©phane Ducasse

On Jan 4, 2011, at 4:25 AM, David T. Lewis wrote: > On Mon, Jan 03, 2011 at 06:55:45PM -0800, Stef T wrote: >> Hello Everyone, >> So, long time squeaker, first time pharo(er ?). Please don't hold this against me ;) >> >> I am trying to get CommandShell loaded into Pharo (using the Seaside Image) via Monticello. I have tried this on Pharo 1.1/1.1.1/1.2 for the record (same thing). I skip past the MVC/Morphic errors about PluggableList etc, and I can get the command shell to pop-up, however, two things happen; >> > > The CommandShell package on SqueakSource is also now broken down > into sub-packages, so you can load the individual parts if you want. > But just proceding through the MVC warnings as you did is harmless. > >> 1) CommandShell complains about AioPlugin not being present and that it will use the 'old slow' way. That's fine, it's merely a warning > > AFAIK, noone has tried building the AioPlugin for Mac, so you will get this > warning when running on a Mac. But as you say, it's just a warning. I imagine that we will see that with igor and the automatic build too. > >> but >> 2) None of the commands get executed. If I try the stuff which will eval inside squeak/pharo, then that's fine (Eg; stdout nextPutAll: 'hello world'; cr.). However, if I try a command such as 'ls' or 'who', all hell breaks lose. stack trace follows :) >> >> If I am doing anything obviously wrong, please feel free to hit me over the head :) > > Nope, it's not you, it's the plugin included with your VM. Some > of the Mac VMs in circulation were accidentally built with a very > out of date version of the OSProcessPlugin. Apparently you have > one of them, and it will definitely not work. But I think there > is a newer version (4.2.5 IIRC) that has the up to date plugin > that works properly on Mac. > > Dave > > >> >> Regards >> S. >> >> >> >> >> 3 January 2011 6:49:43 pm >> >> VM: Mac OS - intel - 1065 - Squeak3.8.1 of '28 Aug 2006' [latest update: #6747] Squeak VM 4.2.4b1 >> Image: Pharo-1.1-11406-rc3 [Latest update: #11406] >> >> SecurityManager state: >> Restricted: false >> FileAccess: true >> SocketAccess: true >> Working Dir /Users/stef/squeak/SeaSide-3.0 >> Trusted Dir /foobar/tooBar/forSqueak/bogus >> Untrusted Dir /Users/stef/Library/Preferences/Squeak/Internet/My Squeak >> >> UndefinedObject(Object)>>mustBeBooleanIn: >> Receiver: nil >> Arguments and temporary variables: >> context: BufferedAsyncFileReadStream>>moveAvailableDataFrom: >> proceedValue: nil >> Receiver's instance variables: >> nil >> >> UndefinedObject(Object)>>mustBeBoolean >> Receiver: nil >> Arguments and temporary variables: >> >> Receiver's instance variables: >> nil >> >> BufferedAsyncFileReadStream>>moveAvailableDataFrom: >> Receiver: BufferedAsyncFileReadStream: 'pipeReader' >> Arguments and temporary variables: >> sqFile: #[48 205 236 155 72 91 120 160 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0] >> bufferSize: 1000 >> buffer: '...etc... >> count: #(0) >> Receiver's instance variables: >> >> >> BufferedAsyncFileReadStream>>moveAvailableDataToBuffer >> Receiver: BufferedAsyncFileReadStream: 'pipeReader' >> Arguments and temporary variables: >> >> Receiver's instance variables: >> >> >> BufferedAsyncFileReadStream>>update: >> Receiver: BufferedAsyncFileReadStream: 'pipeReader' >> Arguments and temporary variables: >> aParameter: a PseudoAioEventHandler >> Receiver's instance variables: >> >> >> [] in PseudoAioEventHandler(Object)>>changed: >> Receiver: a PseudoAioEventHandler >> Arguments and temporary variables: >> aParameter: BufferedAsyncFileReadStream: 'pipeReader' >> aDependent: a PseudoAioEventHandler >> Receiver's instance variables: >> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >> >> DependentsArray>>do: >> Receiver: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> Arguments and temporary variables: >> aBlock: [:aDependent | aDependent update: aParameter] >> dep: BufferedAsyncFileReadStream: 'pipeReader' >> i: 1 >> iLimiT: 1 >> Receiver's instance variables: >> a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> >> PseudoAioEventHandler(Object)>>changed: >> Receiver: a PseudoAioEventHandler >> Arguments and temporary variables: >> aParameter: a PseudoAioEventHandler >> Receiver's instance variables: >> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >> >> PseudoAioEventHandler(Object)>>changed >> Receiver: a PseudoAioEventHandler >> Arguments and temporary variables: >> >> Receiver's instance variables: >> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >> >> [] in [] in PseudoAioEventHandler>>eventGeneratorProcess >> Receiver: a PseudoAioEventHandler >> Arguments and temporary variables: >> d: a Delay(125 msecs) >> Receiver's instance variables: >> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >> >> BlockClosure>>repeat >> Receiver: [self changed. >> d wait] >> Arguments and temporary variables: >> >> Receiver's instance variables: >> outerContext: [] in PseudoAioEventHandler>>eventGeneratorProcess >> startpc: 59 >> numArgs: 0 >> >> [] in PseudoAioEventHandler>>eventGeneratorProcess >> Receiver: a PseudoAioEventHandler >> Arguments and temporary variables: >> d: a Delay(125 msecs) >> Receiver's instance variables: >> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >> >> [] in BlockClosure>>newProcess >> Receiver: [[self changed. >> d wait] repeat] >> Arguments and temporary variables: >> >> Receiver's instance variables: >> outerContext: PseudoAioEventHandler>>eventGeneratorProcess >> startpc: 54 >> numArgs: 0 >> >> >> --- The full stack --- >> UndefinedObject(Object)>>mustBeBooleanIn: >> UndefinedObject(Object)>>mustBeBoolean >> BufferedAsyncFileReadStream>>moveAvailableDataFrom: >> BufferedAsyncFileReadStream>>moveAvailableDataToBuffer >> BufferedAsyncFileReadStream>>update: >> [] in PseudoAioEventHandler(Object)>>changed: >> DependentsArray>>do: >> PseudoAioEventHandler(Object)>>changed: >> PseudoAioEventHandler(Object)>>changed >> [] in [] in PseudoAioEventHandler>>eventGeneratorProcess >> BlockClosure>>repeat >> [] in PseudoAioEventHandler>>eventGeneratorProcess >> [] in BlockClosure>>newProcess >> >

Jan. 4, 2011

Re: [Pharo-project] Issue 3505 in pharo: 1.2 Build fails: MetacelloProjectSpecLoadError: No version found for '1.0.2' of ConfigurationOfMemoryMonitor

by pharo＠googlecode.com

Comment #3 on issue 3505 by marianopeck: 1.2 Build fails: MetacelloProjectSpecLoadError: No version found for '1.0.2' of ConfigurationOfMemoryMonitor http://code.google.com/p/pharo/issues/detail?id=3505 yes, or point to the conf of MetacelloRepository and not the one of MemoryMonitor repo

Jan. 4, 2011