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

Re: [Pharo-project] Issue 3277 in pharo: [FIX] Replace #& in Socket with #and: to save #isConnected send

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3277 by marcus.denker: [FIX] Replace #& in Socket with #and: to save #isConnected send http://code.google.com/p/pharo/issues/detail?id=3277 12250

Nov. 21, 2010

Re: [Pharo-project] Issue 3270 in pharo: fix xor: to work with blocks and booleans

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3270 by marcus.denker: fix xor: to work with blocks and booleans http://code.google.com/p/pharo/issues/detail?id=3270 12250

Nov. 21, 2010

Re: [Pharo-project] Issue 3255 in pharo: It should be possible to print text from help browser to printer

by pharo＠googlecode.com

Comment #2 on issue 3255 by marcus.denker: It should be possible to print text from help browser to printer http://code.google.com/p/pharo/issues/detail?id=3255 pressing the button has no effect on MacOS

Nov. 21, 2010

[Pharo-project] [ENH] Better MCWorkingCopy description in PharoInbox

by Bernhard Pieber

Dear Pharo developers, I just put my first contribution to the PharoInbox: Name: Monticello-BernhardPieber.499 Author: BernhardPieber Time: 21 November 2010, 6:51:13 pm UUID: 8ffedd96-5c55-470b-a2a0-fe81da9dd12a Ancestors: Monticello-StephaneDucasse.498 - Changed MCWorkingCopy description so that the package name is not duplicated when, e.g. Kernel (StephaneDucasse.799) instead of Kernel (Kernel-StephaneDucasse.799). This makes the Monticello Browser easier to use. Enjoy, Bernhard P.S. I read http://pharo-project.org/community/issue-tracking but I am still not sure if adding an issue to the tracker is mandatory in such a case.

Nov. 21, 2010

Re: [Pharo-project] Ideas for CompiledMethod proxies?

by Igor Stasenko

Obviously you can't having a single object representation (a tagged machine word with lowest bit set) and have two different classes for it. On 21 November 2010 16:51, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Sun, Nov 21, 2010 at 12:13 AM, Levente Uzonyi <leves(a)elte.hu> wrote: >> >> On Sat, 20 Nov 2010, Mariano Martinez Peck wrote: >> >>> On Sat, Nov 20, 2010 at 5:41 PM, Levente Uzonyi <leves(a)elte.hu> wrote: >>>> >>>> The only problem is that you can't swap-out a method that's used by the >>>> swap-in code. >>>> >>>> >>> Yes, but that's easy to solve. Before swapping everything, I "simulate" >>> the >>> swapping of a dummy CompiledMethod. During that, I mark all the >>> CompiledMethods that were used to perform that. And then, I exclude those >>> objects from being swapped :) >> >> That won't work, because during the simulation you'll only try a single >> execution path. Swapping in a real method may invoke methods that weren't >> used during the simulation. For example my implementation uses #storeString >> to serialize the methods and Compiler >> #evaluate: to deserialize them. So >> during deserialization a lot of different methods may be invoked. > > Ahhh I got it.... > > Are you using Cog?Â because with the SmallInteger I have the problem I > described with #run:with:in: > > Last question....to use SmallIntegers, I need to put some methods in > SmallInteger, like #run:with:in:Â , #doesNotUnderstand: ,Â and all the > methods related to writing and loading back the original compiledMethod.Â Of > course I can put all those methods under a categoryÂ *MyProxyPackageÂ ... > but I was thinking if there is another way. I would love to have > MySmallIntegerProxy that extends from ProtoObject (because I want my proxy > to understand as less messages as possible) and that is threated by the VM > like a SmallInetger, I mean, that it directly stores the number value in the > address, and put the last bit in 1. > > Is this possible? how much work can it be? > > Thanks in advance, > > Mariano > > -- Best regards, Igor Stasenko AKA sig.

Nov. 21, 2010

Re: [Pharo-project] Issue 3266 in pharo: Clean TextEditor

by Juan Vuletich

Hi Stef, StÃ©phane Ducasse wrote: > On Nov 20, 2010, at 2:21 PM, Alain Plantec wrote: > > >> Le 20/11/2010 10:21, StÃ©phane Ducasse a Ã©crit : >> >>> We should get in the sophie events hierarchy. no ? >>> >> It depends of the amount of work it would requires... >> what about working on SimpleMorphic for that ? >> > > I do not think that we can build something on simpleMorphic, Why? That would be a huge disappointment. > what we can do is look at the kernel and see how the changes can be applied to Morphic. But may be I'm wrong. > Tell me what you think. > What is clear is that I would like to have the Sophie evtn hierarchy because we will start cleaning event soon internally. > Stef Cheers, Juan Vuletich

Nov. 21, 2010

Re: [Pharo-project] Trying SimpleMorph crashes

by Juan Vuletich

Hi Robert, Robert Hawley wrote: > I have installed SimpleMorphic from a file browser into Pharo1.2a @12241 but when I try something like: > x := SMxStarMorph new openInHand > > the system hangs with a eventual crash-out saying: > > ***System error handling failed*** > Original error: Error: MessageNotUnderstood: SMxStarMorph>>ownerChanged. > Debugger error: MessageNotUnderstood: SMxStarMorph>>wantsToBeCachedByHand: > MorphicUIManager>>onPrimitiveError: > ...... > etc. > > There are similar problems when trying this in the one-click Pharo image. > The new morphs are part of SimpleMorphic and will not run in old Morphic. To start SimpleMorphic do 'SimpleMorphicUIManager start'. To go back, evaluate 'SimpleMorphicUIManager stop'. Cheers, Juan Vuletich

Nov. 21, 2010

Re: [Pharo-project] problems trying to run headless

by Yanni Chiu

On 21/11/10 2:03 AM, sergio_101 wrote: >> >> 4.0.3-2202 is a non-Cog VM. Did you develop the image that you're trying to >> run on a machine that was running Cog. If so, then you must use Cog on your >> headless server too; or, rebuild your image without using Cog. >> >> > > hmmm.. i am just using the one click image i got from the pier site: It's not the image, it's the VM's that you use. Currently, once you run an image with a Cog VM, and save it, then you must continue using a Cog VM to run that image.

Nov. 21, 2010

[Pharo-project] Cannot upgrade my pharo-core 1.2 'tracking' image to #12234

by Sven Van Caekenberghe

This is probably not very important, but I cannot upgrade my pharo-core 1.2 'tracking' image to #12234. This image started a long time ago as #12123. THERE_BE_DRAGONS_HERE MessageNotUnderstood: receiver of "characterBlockForIndex:" is nil 21 November 2010 4:03:32 pm VM: Mac OS - intel - 1065 - Croquet Closure Cog VM [CoInterpreter VMMaker-oscog.35] 30.0 Image: Pharo1.2a [Latest update: #12242] SecurityManager state: Restricted: false FileAccess: true SocketAccess: true Working Dir /Users/sven/apps/Smalltalk/Pharo/Pharo-1.2 Trusted Dir /foobar/tooBar/forSqueak/bogus/ Untrusted Dir /foobar/tooBar/forSqueak/bogus/ UndefinedObject(Object)>>doesNotUnderstand: #characterBlockForIndex: Receiver: nil Arguments and temporary variables: aMessage: characterBlockForIndex: 17441 exception: MessageNotUnderstood: receiver of "characterBlockForIndex:" is nil resumeValue: nil Receiver's instance variables: nil SmalltalkEditor(TextEditor)>>markIndex: Receiver: a SmalltalkEditor Arguments and temporary variables: Anybody else seen this ? I guess I will have to start over now ? Sven

Nov. 21, 2010

Re: [Pharo-project] Ideas for CompiledMethod proxies?

by Mariano Martinez Peck

On Sun, Nov 21, 2010 at 12:13 AM, Levente Uzonyi <leves(a)elte.hu> wrote: > On Sat, 20 Nov 2010, Mariano Martinez Peck wrote: > > On Sat, Nov 20, 2010 at 5:41 PM, Levente Uzonyi <leves(a)elte.hu> wrote: >> >>> The only problem is that you can't swap-out a method that's used by the >>> swap-in code. >>> >>> >>> Yes, but that's easy to solve. Before swapping everything, I "simulate" >> the >> swapping of a dummy CompiledMethod. During that, I mark all the >> CompiledMethods that were used to perform that. And then, I exclude those >> objects from being swapped :) >> > > That won't work, because during the simulation you'll only try a single > execution path. Swapping in a real method may invoke methods that weren't > used during the simulation. For example my implementation uses #storeString > to serialize the methods and Compiler >> #evaluate: to deserialize them. So > during deserialization a lot of different methods may be invoked. > Ahhh I got it.... Are you using Cog? because with the SmallInteger I have the problem I described with #run:with:in: Last question....to use SmallIntegers, I need to put some methods in SmallInteger, like #run:with:in: , #doesNotUnderstand: , and all the methods related to writing and loading back the original compiledMethod. Of course I can put all those methods under a category *MyProxyPackage ... but I was thinking if there is another way. I would love to have MySmallIntegerProxy that extends from ProtoObject (because I want my proxy to understand as less messages as possible) and that is threated by the VM like a SmallInetger, I mean, that it directly stores the number value in the address, and put the last bit in 1. Is this possible? how much work can it be? Thanks in advance, Mariano

Nov. 21, 2010