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

Re: [Pharo-project] Tracing bugs/corrections/regressions ... in Pharo

by StÃ©phane Ducasse

Ok so we should fix it. >> In a case like that, the changeset was just merged in the release. > > The test is failing, as you can see: > > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/lastCompleted… >

Feb. 1, 2011

Re: [Pharo-project] Issue 3640 in pharo: better systemVersion API

by pharo＠googlecode.com

Updates: Status: closed Comment #1 on issue 3640 by stephane...(a)gmail.com: better systemVersion API http://code.google.com/p/pharo/issues/detail?id=3640 in 13035....

Feb. 1, 2011

[Pharo-project] [update 1.3] #13035

by StÃ©phane Ducasse

13035 ----- - Issue 3234: fold: reduce: Merge. - Issue 3640: better systemVersion API

Feb. 1, 2011

Re: [Pharo-project] Issue 3641 in pharo: possible new implementation of reduce:

by pharo＠googlecode.com

Updates: Status: closed Comment #1 on issue 3641 by stephane...(a)gmail.com: possible new implementation of reduce: http://code.google.com/p/pharo/issues/detail?id=3641 in fact levente already analysed that version to propose the one in the other bug entry and that is in squeak.

Feb. 1, 2011

Re: [Pharo-project] Tracing bugs/corrections/regressions ... in Pharo

by Marcus Denker

> > Maybe I had some bad luck with > http://code.google.com/p/pharo/issues/detail?id=3468 > Or is there many examples of issues closed without a clue ? In a case like that, the changeset was just merged in the release. The test is failing, as you can see: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/lastCompleted… -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 1, 2011

[Pharo-project] Issue 3641 in pharo: possible new implementation of reduce:

by pharo＠googlecode.com

Status: Accepted Owner: stephane...(a)gmail.com Labels: Milestone-1.3 New issue 3641 by stephane...(a)gmail.com: possible new implementation of reduce: http://code.google.com/p/pharo/issues/detail?id=3641 there is already a version of reduce: made by lukas and I would like to know the difference with this one (proposed by eliot because squeak did not got reduce:) if people can comment on speed... and whatever it would be good. Collection>>reduce: binaryBlock "Apply the argument, binaryBlock cumulatively to the elements of the receiver. For sequenceable collections the elements will be used in order, for unordered collections the order is unspecified." | first nextValue | first := true. self do: [ :each | first ifTrue: [ nextValue := each. first := false ] ifFalse: [ nextValue := binaryBlock value: nextValue value: each ] ]. first ifTrue: [ self errorEmptyCollection ]. ^nextValue! !

Feb. 1, 2011

Re: [Pharo-project] Issue 3234 in pharo: fold: reduce: Merge

by pharo＠googlecode.com

Updates: Status: Closed Comment #3 on issue 3234 by stephane...(a)gmail.com: fold: reduce: Merge http://code.google.com/p/pharo/issues/detail?id=3234 in 13035

Feb. 1, 2011

Re: [Pharo-project] TODO 1.2

by Marcus Denker

On Jan 31, 2011, at 7:38 PM, Lukas Renggli wrote: >> Can I suggest that we really remove the non show stopper? >> and I'm sorry but we cannot maintain packages we do not know. >> >> Lukas could you integrate the fix I did for OB? > > I suggest that you publish the changes to your own repository. I would > like to keep the code in http://source.lukas-renggli.ch/omnibrowser/ > working in Pharo 1.1. > But it is clear that staying backward compatible forever will not make sense? I personally do not have energy for that. in 1.1, everyone used OB and was happy. So why would anyone using 1.1 (which will not be many people) would need to have an updated OB? I personally think energy should not be wasted for this. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 1, 2011

[Pharo-project] Issue 3640 in pharo: better systemVersion API

by pharo＠googlecode.com

Status: fixed Owner: stephane...(a)gmail.com Labels: Milestone-1.3 New issue 3640 by stephane...(a)gmail.com: better systemVersion API http://code.google.com/p/pharo/issues/detail?id=3640 So that we can use it for having different updates.list files

Feb. 1, 2011

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

by StÃ©phane Ducasse

> Hi Doru, > I've take a look and I think I've fixed it. > Unfortunately the network is much too slow here for this BIG package. > You can simply fix it by yourself locally (before it is uploaded on squeaksource). > Just edit DejaVuHolder class >> #installSizes: > and set it to: > > installSizes: aListOfInteger > "self installSizes: #(7 8 9 10 11 12 13 14 24)" > TextConstants TextSharedInformation > at: self fontName > put: (TextStyle fontArray: (self loadFromStructuresList: (self fontStructureNamesForSizes: aListOfInteger))). > StrikeFont useUnderscoreIfOver1bpp. Yes this should be it. Doru TextConstants was a dictionary containing poolVariables (old abstractions) AND values that people just added as global dictionary. What we did was to define the fixed part of TextConstant = the poolVariables as a real SharedPool and the rest the shitty part (where all the system register things in this nice global variables (instead of using adequate class variables)) is now in the classVariable TextSharedInformation of TextConstants Stef

Feb. 1, 2011