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

[Pharo-project] Issue 3646 in pharo: Improve LowSpace handling

by pharo＠googlecode.com

Status: Accepted Owner: siguc...(a)gmail.com Labels: Type-RequestForEnhancement New issue 3646 by siguc...(a)gmail.com: Improve LowSpace handling http://code.google.com/p/pharo/issues/detail?id=3646 - Smalltalk memoryHogs should use weak container, to prevent hanging references. - add the way to hook into default low space condition handling, instead of unconditionally go invoke: UIManager default lowSpaceWatcherDefaultAction: preemptedProcess

Feb. 2, 2011

Re: [Pharo-project] how to use dejavu bitmap fonts

by Benjamin

On Feb 2, 2011, at 1:18 AM, Igor Stasenko wrote: > On 31 January 2011 22:00, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> The package should be updated to 1.2. >> >> It should declare fonts probably in one of the classVar of the TextConstant SharedPool. > > Why fonts can't just use a classvar in AbstractFont class , why > depending on something outside of package? Legacy and laziness I guess :) Ben > > >> Probably >> TextSharedInformation have a look. >> >> In 1.2 we cleaned the last global poolvar = textConstant which was used as a pool but also as a repository to plug anything inside >> instead of specific classVariable in adequate classes. It was a good plate of spaghettis code. >> >> I know that benjamin wants to take some times to do another pass and move the left over to the class they belongs to but it will >> take some time. >> >> Stef >> >> On Jan 31, 2011, at 9:52 PM, Tudor Girba wrote: >> >>> Hi, >>> >>> I am trying to use the DejaVuBitmapFonts, but I do not know how to install them. I tried the following: >>> >>> Gofer it >>> squeaksource: 'DejaVu'; >>> package: 'DejaVuBitmapFonts'; >>> load. >>> >>> DejaVuHolder installFull. >>> >>> However, this creates a problem in using TextConstants. Can anyone help? >>> >>> Cheers, >>> Doru >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "One cannot do more than one can do." >>> >>> >>> >>> >> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. >

Feb. 2, 2011

Re: [Pharo-project] Issue 3625 in pharo: MessageNames search field: MessageNotUnderstood: TextEditor>>caret

by pharo＠googlecode.com

Updates: Labels: Milestone-1.2-DevImage Comment #3 on issue 3625 by marcus.d...(a)gmail.com: MessageNames search field: MessageNotUnderstood: TextEditor>>caret http://code.google.com/p/pharo/issues/detail?id=3625 This is related to OCompletion and happens in the Dev 1.2 image

Feb. 2, 2011

Re: [Pharo-project] Issue 3520 in pharo: Workspaces do not recognize previously evaluated temps

by pharo＠googlecode.com

Comment #14 on issue 3520 by aplan...(a)gmail.com: Workspaces do not recognize previously evaluated temps http://code.google.com/p/pharo/issues/detail?id=3520 yes, I take it.

Feb. 2, 2011

Re: [Pharo-project] react on low space

by Max Leske

Bill, I agree that it is important to at least know that there has been a low space condition. But then again, if there is a low space watcher anyway, shouldn't there be a way to register as a listener or something? Igor, I haven't run your code yet but it looks exactly like what I was looking for! Thanks. Max On 01.02.2011, at 14:13, Igor Stasenko wrote: > On 1 February 2011 14:11, Igor Stasenko <siguctua(a)gmail.com> wrote: >> I think you can catch the OutOfMemory exception: >> > Oops. example was a bit wrong. something like that: > > [ | y x | y := x := Array new: 1000. > 1000000 timesRepeat: [ x at: 1 put: (Array new: 10000). x := x at: 1 ] > ] on: OutOfMemory do: [:ex | > .... > ] > > >> >> On 1 February 2011 12:00, Max Leske <maxleske(a)gmail.com> wrote: >>> I'm bumping this message. I think it's an important question and could help >>> other developers who might have the same problem one day. The low space >>> watcher is cool but if you don't get the chance to actually look at the >>> stack it's pretty useless. >>> Max >>> On 30.01.2011, at 13:10, Max Leske wrote: >>> >>> Hi guys >>> Is there an easy way to react on low space? Something like: >>> >>> SmalltalkImage isSpaceLow >>> ifTrue: [ <suspend my process> ] >>> >>> The reason I'm asking is that I have a background process running that >>> causes a low space condition but I never get around to opening the debugger >>> and the image crashes on me. So for debugging purposes I'd like to >>> periodically check the space that is left or alternatively be notified if >>> low space is signalled. >>> Any ideas? >>> Thanks, >>> Max >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > > > -- > Best regards, > Igor Stasenko AKA sig. >

Feb. 2, 2011

Re: [Pharo-project] Issue 3520 in pharo: Workspaces do not recognize previously evaluated temps

by pharo＠googlecode.com

Updates: Cc: -hilaire.fernandes aplantec Comment #13 on issue 3520 by marcus.d...(a)gmail.com: Workspaces do not recognize previously evaluated temps http://code.google.com/p/pharo/issues/detail?id=3520 Ups, not Hilaire... I meant Alain, sorry.

Feb. 2, 2011

[Pharo-project] Test - please ignore

by Torsten Bergmann

Just a test, please ignore this mail -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone

Feb. 2, 2011

Re: [Pharo-project] Issue 3520 in pharo: Workspaces do not recognize previously evaluated temps

by pharo＠googlecode.com

Updates: Cc: hilaire.fernandes Comment #12 on issue 3520 by marcus.d...(a)gmail.com: Workspaces do not recognize previously evaluated temps http://code.google.com/p/pharo/issues/detail?id=3520 Hilaire, can you check? Workspace is kind of unusable...

Feb. 2, 2011

Re: [Pharo-project] Issue 3484 in pharo: Windows VM in One click image for 1.2 not yet customized

by pharo＠googlecode.com

Comment #6 on issue 3484 by osel...(a)gmail.com: Windows VM in One click image for 1.2 not yet customized http://code.google.com/p/pharo/issues/detail?id=3484 Same thing for One Click Image Cog V1.1.1 on Windows: - not pharo icon - Croquet instead pharo

Feb. 2, 2011

Re: [Pharo-project] what do we do for OmniBrowser?

by StÃ©phane Ducasse

Ok so far no reaction. So may be we should remove OB from 1.2 dev? Stef > Lukas will not maintain OB for Pharo 1.2 and personnally I will not do it because I do not have the knowledge and the time. > So now this is time to know what do we do for OmniBrowser. I have all my ears open. > > > The first step I would do > - host OB for 1.1 in a repository where we have write access. > - create a configurationOf for OB and save it there > > > Stef

Feb. 2, 2011