July 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Memory limit problems on Windows VM

by Andres Valloud

/LARGEADDRESSAWARE?... I don't think /3GB is even recognized in 64 bit Windows... http://support.microsoft.com/default.aspx?scid=889654 On 7/16/14 14:49 , Eliot Miranda wrote: > > > > On Wed, Jul 16, 2014 at 2:21 PM, Oscar E. A. CallaÃº > <oscar.apollo(a)gmail.com <mailto:oscar.apollo@gmail.com>> wrote: > > Hi, > > I'm using Windows 8.1 (update1) 64bits with 4GB of physical RAM. I > only need 1.5GB of RAM, so I think I don't need to configure my > OS to take /3GB of RAM. > > > Well my experience (and others) is that one can't grow the heap much > above 1.1 Gb without using the /3Gb switch on Windows XP. I can't talk > for 8.1. But if 8.x also limits memory to 2Gb/process unless the /3Gb > switch is in effect then yes, you'll need to use the /3Gb switch. > > HTH > Eliot > > > Cheers > > On Wednesday, July 16, 2014, Eliot Miranda wrote: > > Hi Oscar, > > > On Wed, Jul 16, 2014 at 9:11 AM, Oscar E. A. CallaÃº > <oscar.apollo(a)gmail.com> wrote: > > Hi guys, > > I'm running some experiments in Pharo. My data is > aprox. 1.3GB. When I load my image on Mac, everything works > perfectly. But, when I try to load the same image on > Windows, I get this error: > > Unable to commit memory (1326649344 bytes requested) > > I tried the Pharo VM, cogMT and NBcog with and without the > option > > AddressSpaceLimit = 2048 > > in the ini file > > Please help. > > What OS are you using? Have you read e.g. > http://msdn.microsoft.com/en-us/library/windows/hardware/dn613959(v=vs.85).… > > > -- > best, > Eliot > > > > > -- > best, > Eliot

July 17, 2014

Re: [Pharo-dev] Memory limit problems on Windows VM

by btc＠openinworld.com

July 17, 2014

Re: [Pharo-dev] Memory limit problems on Windows VM

by Eliot Miranda

On Wed, Jul 16, 2014 at 2:21 PM, Oscar E. A. CallaÃº <oscar.apollo(a)gmail.com> wrote: > Hi, > > I'm using Windows 8.1 (update1) 64bits with 4GB of physical RAM. I only > need 1.5GB of RAM, so I think I don't need to configure my OS to take /3GB > of RAM. > Well my experience (and others) is that one can't grow the heap much above 1.1 Gb without using the /3Gb switch on Windows XP. I can't talk for 8.1. But if 8.x also limits memory to 2Gb/process unless the /3Gb switch is in effect then yes, you'll need to use the /3Gb switch. HTH Eliot > Cheers > > On Wednesday, July 16, 2014, Eliot Miranda wrote: > >> Hi Oscar, >> >> >> On Wed, Jul 16, 2014 at 9:11 AM, Oscar E. A. CallaÃº < >> oscar.apollo(a)gmail.com> wrote: >> >>> Hi guys, >>> >>> I'm running some experiments in Pharo. My data is aprox. 1.3GB. >>> When I load my image on Mac, everything works perfectly. But, when I try to >>> load the same image on Windows, I get this error: >>> >>> Unable to commit memory (1326649344 bytes requested) >>> >>> I tried the Pharo VM, cogMT and NBcog with and without the option >>> >>> AddressSpaceLimit = 2048 >>> >>> in the ini file >>> >>> Please help. >>> >> >> What OS are you using? Have you read e.g. >> http://msdn.microsoft.com/en-us/library/windows/hardware/dn613959(v=vs.85).… >> ? >> >> -- >> best, >> Eliot >> > -- best, Eliot

July 16, 2014

Re: [Pharo-dev] Memory limit problems on Windows VM

by Oscar E. A. CallaÃº

Hi, I'm using Windows 8.1 (update1) 64bits with 4GB of physical RAM. I only need 1.5GB of RAM, so I think I don't need to configure my OS to take /3GB of RAM. Cheers On Wednesday, July 16, 2014, Eliot Miranda wrote: > Hi Oscar, > > > On Wed, Jul 16, 2014 at 9:11 AM, Oscar E. A. CallaÃº < > oscar.apollo(a)gmail.com > <javascript:_e(%7B%7D,'cvml','oscar.apollo(a)gmail.com');>> wrote: > >> Hi guys, >> >> I'm running some experiments in Pharo. My data is aprox. 1.3GB. >> When I load my image on Mac, everything works perfectly. But, when I try to >> load the same image on Windows, I get this error: >> >> Unable to commit memory (1326649344 bytes requested) >> >> I tried the Pharo VM, cogMT and NBcog with and without the option >> >> AddressSpaceLimit = 2048 >> >> in the ini file >> >> Please help. >> > > What OS are you using? Have you read e.g. > http://msdn.microsoft.com/en-us/library/windows/hardware/dn613959(v=vs.85).… > ? > > -- > best, > Eliot >

July 16, 2014

[pharo-project/pharo-core] bf4d12: 40092

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: bf4d12d670e9885783929f9f43b915924c0a21b3 https://github.com/pharo-project/pharo-core/commit/bf4d12d670e9885783929f9f… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-07-16 (Wed, 16 Jul 2014) Changed paths: A Graphics-Primitives.package/EllipseMidpointTracer.class/README.md A Graphics-Primitives.package/EllipseMidpointTracer.class/definition.st A Graphics-Primitives.package/EllipseMidpointTracer.class/instance/computing/stepInY.st A Graphics-Primitives.package/EllipseMidpointTracer.class/instance/initialize/on_.st A Graphics-Primitives.package/GrafPort.class/README.md A Graphics-Primitives.package/GrafPort.class/definition.st A Graphics-Primitives.package/GrafPort.class/instance/accessing/alphaBits_.st A Graphics-Primitives.package/GrafPort.class/instance/accessing/contentsOfArea_into_.st A Graphics-Primitives.package/GrafPort.class/instance/accessing/fillPattern_.st A Graphics-Primitives.package/GrafPort.class/instance/accessing/lastFontForegroundColor.st A Graphics-Primitives.package/GrafPort.class/instance/copying/clippedBy_.st A Graphics-Primitives.package/GrafPort.class/instance/copying/copyBits.st A Graphics-Primitives.package/GrafPort.class/instance/drawing support/fillOval_.st A Graphics-Primitives.package/GrafPort.class/instance/drawing support/fillRect_offset_.st A Graphics-Primitives.package/GrafPort.class/instance/drawing support/frameOval_borderWidth_.st A Graphics-Primitives.package/GrafPort.class/instance/drawing support/frameRectBottom_height_.st A Graphics-Primitives.package/GrafPort.class/instance/drawing support/frameRectRight_width_.st A Graphics-Primitives.package/GrafPort.class/instance/drawing support/frameRect_borderWidth_.st A Graphics-Primitives.package/GrafPort.class/instance/drawing support/image_at_sourceRect_rule_.st A Graphics-Primitives.package/GrafPort.class/instance/drawing support/image_at_sourceRect_rule_alpha_.st A Graphics-Primitives.package/GrafPort.class/instance/drawing support/stencil_at_sourceRect_.st A Graphics-Primitives.package/GrafPort.class/instance/private/installStrikeFont_.st A Graphics-Primitives.package/GrafPort.class/instance/private/installStrikeFont_foregroundColor_backgroundColor_.st A Graphics-Primitives.package/GrafPort.class/instance/private/lastFont.st R Morphic-Core.package/EllipseMidpointTracer.class/README.md R Morphic-Core.package/EllipseMidpointTracer.class/definition.st R Morphic-Core.package/EllipseMidpointTracer.class/instance/computing/stepInY.st R Morphic-Core.package/EllipseMidpointTracer.class/instance/initialize/on_.st R Morphic-Core.package/GrafPort.class/README.md R Morphic-Core.package/GrafPort.class/definition.st R Morphic-Core.package/GrafPort.class/instance/accessing/alphaBits_.st R Morphic-Core.package/GrafPort.class/instance/accessing/contentsOfArea_into_.st R Morphic-Core.package/GrafPort.class/instance/accessing/fillPattern_.st R Morphic-Core.package/GrafPort.class/instance/accessing/lastFontForegroundColor.st R Morphic-Core.package/GrafPort.class/instance/copying/clippedBy_.st R Morphic-Core.package/GrafPort.class/instance/copying/copyBits.st R Morphic-Core.package/GrafPort.class/instance/drawing support/fillOval_.st R Morphic-Core.package/GrafPort.class/instance/drawing support/fillRect_offset_.st R Morphic-Core.package/GrafPort.class/instance/drawing support/frameOval_borderWidth_.st R Morphic-Core.package/GrafPort.class/instance/drawing support/frameRectBottom_height_.st R Morphic-Core.package/GrafPort.class/instance/drawing support/frameRectRight_width_.st R Morphic-Core.package/GrafPort.class/instance/drawing support/frameRect_borderWidth_.st R Morphic-Core.package/GrafPort.class/instance/drawing support/image_at_sourceRect_rule_.st R Morphic-Core.package/GrafPort.class/instance/drawing support/image_at_sourceRect_rule_alpha_.st R Morphic-Core.package/GrafPort.class/instance/drawing support/stencil_at_sourceRect_.st R Morphic-Core.package/GrafPort.class/instance/private/installStrikeFont_.st R Morphic-Core.package/GrafPort.class/instance/private/installStrikeFont_foregroundColor_backgroundColor_.st R Morphic-Core.package/GrafPort.class/instance/private/lastFont.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script92.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40092.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tools.package/AbstractTool.class/instance/private/renamePackage_.st Log Message: ----------- 40092 13515 GrafPort and EllipseMidpointTracer should not be in Morphic package https://pharo.fogbugz.com/f/cases/13515 13563 Fix sender of deprecated RPackageOrganizer>>#renamePackage:in: method https://pharo.fogbugz.com/f/cases/13563 http://files.pharo.org/image/40/40092.zip

July 16, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40092 Home: https://github.com/pharo-project/pharo-core

July 16, 2014

Re: [Pharo-dev] About Cocoa delegate

by stepharo

tx mark. I know now I found strange that they push that. Now apparently this is not in the new doc. On 16/7/14 16:56, Mark Bestley wrote: > > You don't have to write the check it is just defensive programming > you can just do > > -(void)someMethod { > if ( [delegate operationShouldProceed] ) { > // do something appropriate > > } } > > then if the delegate does not have operationShouldProceed you get a > selector not found error - which will crash the program. So similar to > smalltalk except that would get a debugger here. > > So depends how certain you have a good delegate or if there is > something you can do if you don't. > > Mark > > On 16/07/2014 09:58, stepharo wrote: >> I found strange to force user to write >> >> Before invoking a delegation method, make sure the delegate implements >> it by sending it a >> >> respondsToSelector: message. >> >> Cocoa Fundamentals Guide (TP40002974 6.0.0) >> >> - (void)someMethod { >> >> if ( [delegate respondsToSelector:@selector(operationShouldProceed)] ){ >> >> if ( [delegate operationShouldProceed] ) { >> // do something appropriate >> >> } } >> >> } >> >> I'm reading also on bindings (could be like valueHolder) and >> targetAction. >> I think that I will have to read that several times :) >> >> https://developer.apple.com/legacy/library/documentation/Cocoa/Conceptual/C… >> >> >> Stef >> >> Cocoa Fundamentals Guide (TP40002974 6.0.0) >> On 16/7/14 10:48, stepharo wrote: >>> Hi >>> >>> In the quest for a better UI framework :), I was re rereading about >>> delegate in Cocoa. >>> A delegating object will delegate certain operations to a delegate >>> object (check the attachment). >>> Now I was wondering why this is not a simple delegation they wrote: >>> >>> The delegating object sends a message only if the delegate implements >>> the method. It makes this discovery by invoking the NSObject method >>> respondsToSelector: in the delegate first. >>> >>> Cocoa Fundamentals Guide (TP40002974 6.0.0) >>> >> > >

July 16, 2014

Re: [Pharo-dev] About Cocoa delegate

by stepharo

:) I was not even at this level. Many people confuses delegation and forwarding. I remember that I helped removing some errors in books I reviewed. Stef On 16/7/14 20:07, Eliot Miranda wrote: > > > > On Wed, Jul 16, 2014 at 1:48 AM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Hi > > In the quest for a better UI framework :), I was re rereading > about delegate in Cocoa. > A delegating object will delegate certain operations to a delegate > object (check the attachment). > Now I was wondering why this is not a simple delegation they wrote: > > The delegating object sends a message only if the delegate > implements the method. It makes this discovery by invoking the > NSObject method respondsToSelector: in the delegate first. > > Sad that this framework confuses delegation and forwarding. What it > describes as delegation is merely forwarding. Delegation is quite > different; self is bound to the delegator when running delegated > methods. When (as in Self) one object delegates to another, sends to > self in the second object bind to methods in the first object, the > delegator. In forwarding, self is bound to the object the message is > forwarded to (i.e. normal Smalltalk & ObjectiveC semantics). > > -- > best, > Eliot

July 16, 2014

Re: [Pharo-dev] About Cocoa delegate

by stepharo

I checked and the new doc does not refer to delegate. I will read the target action and others Stef On 16/7/14 11:04, Esteban Lorenzano wrote: > btwâ¦ while I think cocoa fundamentals is good reading, it is marked as > a retired document. > I think the replace doc is this one: > > https://developer.apple.com/library/mac/documentation/general/conceptual/Co… > > (but since I still do not read it, I donât know if is a good replacement) > > Esteban > > On 16 Jul 2014, at 10:58, stepharo <stepharo(a)free.fr> wrote: > >> I found strange to force user to write >> >> Before invoking a delegation method, make sure the delegate >> implements it by sending it a >> >> respondsToSelector: message. >> >> Cocoa Fundamentals Guide (TP40002974 6.0.0) >> - (void)someMethod { >> >> if ( [delegate respondsToSelector:@selector(operationShouldProceed)] ){ >> >> if ( [delegate operationShouldProceed] ) { >> // do something appropriate >> >> } } >> >> } >> >> I'm reading also on bindings (could be like valueHolder) and >> targetAction. >> I think that I will have to read that several times :) >> >> https://developer.apple.com/legacy/library/documentation/Cocoa/Conceptual/C… >> >> Stef >> >> Cocoa Fundamentals Guide (TP40002974 6.0.0) >> On 16/7/14 10:48, stepharo wrote: >>> Hi >>> >>> In the quest for a better UI framework :), I was re rereading about >>> delegate in Cocoa. >>> A delegating object will delegate certain operations to a delegate >>> object (check the attachment). >>> Now I was wondering why this is not a simple delegation they wrote: >>> >>> The delegating object sends a message only if the delegate >>> implements the method. It makes this discovery by invoking the >>> NSObject method respondsToSelector: in the delegate first. >>> >>> Cocoa Fundamentals Guide (TP40002974 6.0.0) >>> >> >

July 16, 2014

Re: [Pharo-dev] [ANN] Ephestos - Using and Coding Blender from inside Pharo

by Sebastian Sastre

On Jul 16, 2014, at 12:27 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > One suggestion about the edition of the video. Show some of the > results during the first 30 seconds, and then explain the whole > process to get there. > It's like the cooking shows, where they show the cake already made, > and then the whole process to make it. +1 about using that format. First and quick you show the what, then you take your time to show the how in all its details Congratulations for achieving that, youâre doing a great job and there is huge potential in it! sebastian o/ blog: http://sebastianconcept.com LinkedIn: http://www.linkedin.com/in/sebastiansastre github: https://github.com/sebastianconcept

July 16, 2014