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

Re: [Pharo-project] [ANN 1.2.1Core] pre-build 1.2.1 Core image
by Marcus Denker March 30, 2011

March 30, 2011

On Mar 29, 2011, at 10:18 PM, StÃ©phane Ducasse wrote: >> Pharo 1.2.1 looks good so far, except for the GLMOrangeUITheme that is >> still in a circular dependency. >> >> Lukas > > Can you open a ticket? We can do a 1.2.2... and add the TextContstants at:put: fix, too. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] [COTDC] 37 - MCPatcher
by laurent laffont March 30, 2011

March 30, 2011

Today: MCPatcher Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

3 8

Re: [Pharo-project] [ANN 1.2.1Core] pre-build 1.2.1 Core image
by Marcus Denker March 29, 2011

March 29, 2011

On Mar 29, 2011, at 10:14 PM, Lukas Renggli wrote: > Pharo 1.2.1 looks good so far, except for the GLMOrangeUITheme that is > still in a circular dependency. > There was no bug report filed. I nearly asked when you sent the mail if this was meant to be a bug report... but I thought you would do it if you would think that it's a show stopper. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

Re: [Pharo-project] [ANN 1.2.1Core] pre-build 1.2.1 Core image
by Marcus Denker March 29, 2011

March 29, 2011

On Mar 29, 2011, at 10:29 PM, Igor Stasenko wrote: > On 29 March 2011 22:18, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> Pharo 1.2.1 looks good so far, except for the GLMOrangeUITheme that is >>> still in a circular dependency. >>> >>> Lukas >> >> Can you open a ticket? >> I want to clean all the themes soon in 1.3 >> >> > > i wonder how it is happen that this bug not eliminated before > switching to 1.3 line? > i remember that we fixed it few updates later. Since 3 Months, we just fix "absolute horrible show stopping bugs" in 1.2. And that is a very subjective thing... -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] Migration morph objects from 1.1 to 1.2
by Marcus Denker March 29, 2011

March 29, 2011

On Mar 29, 2011, at 10:26 PM, Denis Kudriashov wrote: > > But I really want ask where I can read about morphic changes between 1.1 and 1.2 pharo. http://code.google.com/p/pharo/issues/list?can=1&q=Milestone%3D1.2 too much to be useful, I fear. We need to a) automatize releases so we can release more often b) automaize change reporting of releases. Marucs -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Migration morph objects from 1.1 to 1.2
by Denis Kudriashov March 29, 2011

March 29, 2011

Hello I have many morphs saved in files by smartReferenceStream. I doing it in pharo1.1 image. Now I want to load this objects to pharo1.2. When I doing this I have exception about absent TextConstants stuff. My saved Morph containes textMorph. I know pharo1.2 has textMorph refactored and TextConstants was removed. How old object can be migrated to new stuff? Is some rules exists? For example, when I import morph from file (created in pharo1.1) I see in debugger "TextConstants class at: index" where "index=#DefaultTabsArray" Best regards, Denis

2 4

Re: [Pharo-project] [ANN 1.2.1Core] pre-build 1.2.1 Core image
by Marcus Denker March 29, 2011

March 29, 2011

On Mar 29, 2011, at 9:38 PM, Lukas Renggli wrote: > Is this intentional that the image was saved with a newer VM than > previous builds? > > This interpreter (vers. 6502) cannot read image file (vers. 6505). > Oh, yes... I have a new VM on my system (one compiled by our build system). And on the build server use right now Ian's latest unix vm that can read these images, too. This shows that 1.2 should have been released weeks ago. The world is moving on and it gets really difficult to go back to the past just to relase 1.2. So what do we do? The shity gforge means that we would need to generate a new link. Maybe named "1.2.1 this time really final?". I am getting tired of 1.2... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

4 6

Re: [Pharo-project] Migration morph objects from 1.1 to 1.2
by Marcus Denker March 29, 2011

March 29, 2011

On Mar 29, 2011, at 9:58 PM, Denis Kudriashov wrote: > Hello > > I have many morphs saved in files by smartReferenceStream. I doing it in pharo1.1 image. > Now I want to load this objects to pharo1.2. > When I doing this I have exception about absent TextConstants stuff. My saved Morph containes textMorph. > I know pharo1.2 has textMorph refactored and TextConstants was removed. > > How old object can be migrated to new stuff? Is some rules exists? No, I don't think so... keeping the system compatibel at that level is *really* difficult... simple refactoring can be done (e.g. etoys did that for years), but complex changes in the image will be nearly impossible if you require serializability compatibility at that level. (especially when using image segment style low-level serialization). Being compatible on that level was religion for Squeak (and it's even today). I personally don't think that what we have is valuable enough to define compatibility on that level to be more impotant than being able to evolve the system. The system as it is now is just not good enough to have any form of future with it, so trading "improve it" vs. "be backward compatible on a binary level" is selection between having the past and having a future... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

March 29, 2011

13118 ----- - Issue 3429: Better Number performance. Thanks Levente and Nicolas Cellier. - Issue 3845: Polymorph extension shortSummary is not programmed the object way. Thanks Nicolas Cellier. - Issue 3902: Text field converter refactoring. Thanks Gary Chambers. - Issue 3713: Additional obsolete methods. Thanks Edmond - Issue 3878: #enableTextChange selector name is misleading, i propose changing the name to #canChangeText. Thanks Fernando Olivero. Thanks guys..... More tomorrow

1 0

[Pharo-project] Issue 3429 in pharo: Better Number performance
by pharo＠googlecode.com March 29, 2011

March 29, 2011

Status: FixedWaitingToBePharoed Owner: stephane.ducasse Labels: Milestone-1.3 New issue 3429 by stephane.ducasse: Better Number performance http://code.google.com/p/pharo/issues/detail?id=3429 Name: Kernel-ul.522 Author: ul Time: 8 December 2010, 4:08:19.384 am UUID: 6927b03c-21df-1746-9a0d-115b717a5e40 Ancestors: Kernel-ul.521 - implemented Fraction >> #negative and ScaledDecimal >> #negative for better performance. These methods don't allocate new objects. - reimplemented SmallInteger printing methods (printOn:base:*) without String allocation. They are as fast as the previous versions were for base 10. - reimplemented ScaledDecimal printing. It avoids object allocations and has better performance than the previous version. ScaledDecimals can also be printed without the scale part by using #printFractionAsDecimalOn:. =============== Diff against Kernel-ul.521 =============== Item was added: + ----- Method: Fraction>>negative (in category 'testing') ----- + negative + + ^numerator negative! Item was added: + ----- Method: ScaledDecimal>>negative (in category 'testing') ----- + negative + + ^fraction negative! Item was added: + ----- Method: ScaledDecimal>>printFractionAsDecimalOn: (in category 'printing') ----- + printFractionAsDecimalOn: stream + + | aFraction integerPart fractionPart | + fraction negative + ifFalse: [ aFraction := fraction ] + ifTrue: [ + aFraction := fraction negated. + stream nextPut: $- ]. + integerPart := aFraction truncated. + integerPart printOn: stream. + scale = 0 ifTrue: [ ^self ]. + stream nextPut: $.. + fractionPart := ((aFraction - integerPart) * (10 raisedToInteger: scale)) truncated. + fractionPart + printOn: stream + base: 10 + length: scale + padded: true! Item was changed: ----- Method: ScaledDecimal>>printOn: (in category 'printing') ----- + printOn: stream + + self + printFractionAsDecimalOn: stream; + printScaleOn: stream! - printOn: aStream - "Reimplementation - Object 'printing' method." - | aFraction tmpFractionPart | - self < 0 ifTrue: [aStream nextPut: $-]. - aFraction := fraction abs. - aStream nextPutAll: aFraction truncated printString. - scale = 0 ifTrue: [^ aStream nextPutAll: 's0']. - aStream nextPut: $.. - tmpFractionPart := aFraction fractionPart. - 1 to: scale - do: - [:dummy | - tmpFractionPart := tmpFractionPart * 10. - aStream nextPut: (Character digitValue: tmpFractionPart truncated). - tmpFractionPart := tmpFractionPart fractionPart]. - aStream nextPut: $s. - scale printOn: aStream! Item was added: + ----- Method: ScaledDecimal>>printScaleOn: (in category 'printing') ----- + printScaleOn: stream + + stream nextPut: $s. + scale printOn: stream! Item was changed: ----- Method: SmallInteger>>printOn:base: (in category 'printing') ----- + printOn: stream base: base - printOn: aStream base: b "Append a representation of this number in base b on aStream." + self printOn: stream base: base length: 0 padded: false! - self < 0 - ifTrue: [aStream nextPut: $-. - aStream nextPutAll: (self negated printStringBase: b). - ^self]. - - "allocating a String seems faster than streaming for SmallInteger" - aStream nextPutAll: (self printStringBase: b)! Item was added: + ----- Method: SmallInteger>>printOn:base:length:padded: (in category 'printing') ----- + printOn: stream base: base length: minimumLength padded: padWithZeroes + + | n numberOfDigits totalLength divisor | + self < 0 + ifTrue: [ + n := self negated. + totalLength := 1 ] + ifFalse: [ + n := self. + totalLength := 0 ]. + numberOfDigits := n numberOfDigitsInBase: base. + totalLength := totalLength + numberOfDigits. + padWithZeroes ifFalse: [ + [ totalLength < minimumLength ] whileTrue: [ + stream space. + totalLength := totalLength + 1 ] ]. + n = self ifFalse: [ stream nextPut: $- ]. + padWithZeroes ifTrue: [ + [ totalLength < minimumLength ] whileTrue: [ + stream nextPut: $0. + totalLength := totalLength + 1 ] ]. + divisor := (base raisedToInteger: numberOfDigits - 1). + [ divisor > 0 ] whileTrue: [ + | digit | + digit := n // divisor. + stream nextPut: ('0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ' at: digit + 1). + n := n - (digit * divisor). + divisor := divisor // base ]! Item was changed: ----- Method: SmallInteger>>printOn:base:nDigits: (in category 'printing') ----- printOn: aStream base: b nDigits: n "Append a representation of this number in base b on aStream using nDigits. self must be positive." + self printOn: aStream base: b length: n padded: true! - "allocating a String seems faster than streaming for SmallInteger" - aStream nextPutAll: (self printStringBase: b nDigits: n)!

3 6