- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3981 in pharo: #<= on SourcedMethodReference is very slow

by pharo＠googlecode.com

Updates: Labels: Milestone-1.3 Comment #7 on issue 3981 by marcus.d...(a)gmail.com: #<= on SourcedMethodReference is very slow http://code.google.com/p/pharo/issues/detail?id=3981 (No comment was entered for this change.)

April 15, 2011

[Pharo-project] Issue 4030 in pharo: defaultBackgroundColor should not use self theme

by pharo＠googlecode.com

Status: Accepted Owner: marianopeck New issue 4030 by marianopeck: defaultBackgroundColor should not use self theme http://code.google.com/p/pharo/issues/detail?id=4030 Object >> defaultBackgroundColor from *Tools-Base defaultBackgroundColor "Answer the color to be used as the base window color for a window whose model is an object of the receiver's class" ^ self theme windowColorFor: self But Object dnu #them. So...changed to: defaultBackgroundColor "Answer the color to be used as the base window color for a window whose model is an object of the receiver's class" "I don't want to do a self theme because otherwise I will need to implement it on Object" ^ UITheme current windowColorFor: self

April 15, 2011

[Pharo-project] Issue 4029 in pharo: DomainError and NaNException

by pharo＠googlecode.com

Status: New Owner: ---- New issue 4029 by sven.van...(a)gmail.com: DomainError and NaNException http://code.google.com/p/pharo/issues/detail?id=4029 PharoCore 1.3 Name: Kernel-SvenVanCaekenberghe.867 Author: SvenVanCaekenberghe Time: 15 April 2011, 5:02:31 pm UUID: 476ee577-2508-4d70-bba1-91ffd1d63592 Ancestors: Kernel-SvenCamillo.866 added DomainError and NaNException added signaler instance variable to Exception with initialization in signal refactored Exception method categories

April 15, 2011

[Pharo-project] Question on finder

by Alexandre Bergel

Hi! Maybe it has already been discussed. In a finder I entered: '*bcd*' . 'abcdef' . true I am surprised to not have obtained #match: Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 15, 2011

[Pharo-project] Error in the Recent Message List

by Veronica Isabel Uquillas Gomez

Hi, I got an error while exploring the recent messages list (by classes - default) and then switching to 'by version' DNU #isByteString in a DateAndTime object. Using: Pharo-1.3 the last update. regards, Veronica

April 15, 2011

Re: [Pharo-project] Issue 3662 in pharo: build of 1.3 Full fails on Hudson

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3662 by marcus.d...(a)gmail.com: build of 1.3 Full fails on Hudson http://code.google.com/p/pharo/issues/detail?id=3662 fixed

April 15, 2011

Re: [Pharo-project] Issue 3837 in pharo: Can not build Pharo Full 1.3

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3837 by marcus.d...(a)gmail.com: Can not build Pharo Full 1.3 http://code.google.com/p/pharo/issues/detail?id=3837 fixed

April 15, 2011

[Pharo-project] [ANN] First try for a PharoDev 1.3

by Mariano Martinez Peck

Hi guys. So...I have updated almost all configurations and at least now: - the image builds - I can open a OB browser - I have colors (shout) - I have OCompletion There may be A LOT of problems and things to improve, but this was the first step. Hudson has already built the image: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/94/artifact/Pharo-1.… If you want to try by yourself, take a PharoCore 1.3 and evaluate: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load. (ConfigurationOfPharo project version: '1.3-beta') load. Now...if you want a rock solid Dev image, you should start to HELP now. By Help I mean, reporting issues, fixing bugs, fixing red tests, updating your packages, etc. Cheers -- Mariano http://marianopeck.wordpress.com

April 15, 2011

Re: [Pharo-project] Issue 1915 in pharo: Making ToolSet more flexible

by pharo＠googlecode.com

Comment #12 on issue 1915 by siguc...(a)gmail.com: Making ToolSet more flexible http://code.google.com/p/pharo/issues/detail?id=1915 the above changesets are in 13156. more to come

April 15, 2011

Re: [Pharo-project] Issue 4028 in pharo: Possible infinite loop in ImageSegment >> #uniqueFileNameFor:

by pharo＠googlecode.com

Comment #2 on issue 4028 by marianopeck: Possible infinite loop in ImageSegment >> #uniqueFileNameFor: http://code.google.com/p/pharo/issues/detail?id=4028 hehehehehehheheh At least that only happens when yo DO NOT specify a fileName.... And I don't see any reason about that limit. Cannot we just remove this line? BiggestFileNumber > 99 ifTrue: [BiggestFileNumber := 1]. "wrap" And then an explicit message to reset it ? So that the developer that really understand the problem, can explicirtly and savely reset it?

April 15, 2011