October 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Bug in OCompletion

by Mariano Martinez Peck

Thanks to romain, he did a fix. I think it would be integrated in next Pharo dev. See details here: http://code.google.com/p/pharo/issues/detail?id=1236 cheers mariano On Sun, Oct 18, 2009 at 7:03 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > This bug has been closed but I can still reproduce it in 10479. Can someone > please test it and tell me if I am not > > the only one. > > Thanks > > mariano > > > > On Wed, Sep 23, 2009 at 4:29 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> >> >> Begin forwarded message: >> >> *From: *Mariano Martinez Peck <marianopeck(a)gmail.com> >> *Date: *September 23, 2009 8:20:40 PM CEDT >> *To: *Pharo Development <pharo-project(a)lists.gforge.inria.fr> >> *Subject: **[Pharo-project] Bug in OCompletion* >> *Reply-To: *Pharo-project(a)lists.gforge.inria.fr >> >> http://code.google.com/p/pharo/issues/detail?id=1236 >> >> Tested with OBSystemBrowserAdaptor in pharo1.0-10451-BETAdev09.09.3 on >> Windows. >> >> To reproduce: >> >> 1) Open a System Browser >> 2) Create a new class. When you do this, when you are changing >> "#NameOfSubclass" to "#YourClass", after doing this press the down arrow >> key >> 3) An empty pop up will be brought and the keyboard won't respond. To fix >> this, you must press "Esc" key. >> >> >> Best, >> >> Mariano >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> >

Oct. 20, 2009

[Pharo-project] scriptloader>>loadComanche

by Johan Brichau

Hi there, Scriptloader has lost its #loadComanche method, which means that #loadSeaside30 does not work anymore. What happened? ;-) ---------------------------- Johan Brichau johan.brichau(a)uclouvain.be

Oct. 19, 2009

Re: [Pharo-project] [ANN] Pharo Core 1.0rc1

by Michael Roberts

I don't use the polymorph merge tool. As discussed in a previous thread it's very limited for doing serious merging. It's the first thing I turn off in an update. Just hit the merge button. thanks, Mike On Mon, Oct 19, 2009 at 8:30 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > See also http://code.google.com/p/pharo/issues/detail?id=1214 > > 2009/10/19 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >> Don't know... >> Maybe the plan was to move it up in SequenceableCollection, like >> http://bugs.squeak.org/view.php?id=7242 ? >> >> Nicolas >> >> 2009/10/19 Niko Schwarz <niko.schwarz(a)googlemail.com>: >>> Then, why was sort: yanked from OrderedCollection? I'm confused. >>> >>> On Mon, Oct 19, 2009 at 9:17 PM, Nicolas Cellier >>> <nicolas.cellier.aka.nice(a)gmail.com> wrote: >>>> Implementation details: #sortBy: is not exactly #sort: >>>> #sort: does a fast inplace sort, when #sortBy: performs useless copy >>>> operations... >>>> >>>> Nicolas >>>> >>>> 2009/10/19 Niko Schwarz <niko.schwarz(a)googlemail.com>: >>>>> That was me, it comes from Squeak trunk. I didn't test it, because it >>>>> looked so harmless and works in Squeak â¦Â I'm sorry. It should be >>>>> "sortBy: rather than sort:" >>>>> >>>>> niko >>>>> >>>>> On Mon, Oct 19, 2009 at 7:06 PM, Michael Roberts <mike(a)mjr104.co.uk> wrote: >>>>>> MCMergeBrowser>>merger: >>>>>> Â Â Â Â conflicts := aMerger conflicts sort: [:a :b | a operation <= b operation]. >>>>>> >>>>>> OrderedCollection dnu sort: >>>>>> >>>>>> introduced I guess >>>>>> >>>>>> http://code.google.com/p/pharo/issues/detail?id=1320 >>>>>> >>>>>> how was this change tested? >>>>>> >>>>>> thanks, >>>>>> Mike >>>>>> >>>>>> On Mon, Oct 19, 2009 at 4:25 PM, Marcus Denker <denker(a)acm.org> wrote: >>>>>>> http://gforge.inria.fr/frs/download.php/24363/PharoCore-1.0-10491rc1.zip >>>>>>> >>>>>>> The zip contains a new sources file. >>>>>>> >>>>>>> Â Â Â Â Marcus >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Pharo-project mailing list >>>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 19, 2009

Re: [Pharo-project] HostWindowTests>>testOne is failing in Windows

by Mariano Martinez Peck

Thanks everybody. There is a fix in the inbox. See http://code.google.com/p/pharo/issues/detail?id=1338 for details. On Mon, Oct 19, 2009 at 2:57 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Hi adrian: I run all Pharo core tests in a Windows box and I get only one > failure and 18 expected failures :) > > The only failure is HostWindowTests>>testOne. The assert with problem is: > > self > shouldnt: [ hwindow open ] > raise: Error. > > > And the error raised is 'My subclass should have overridden > #defaultWindowType' > > This is because in DisplayHostWindow>>open > > windowProxy is a HostWindowProxy and this class, the implementation of > defaultWindowType is: > > defaultWindowType > "set up my attributes to be a default window - a titlebar, usual > decorations etc" > ^self subclassResponsibility > > I opened a bug ticket: > http://code.google.com/p/pharo/issues/detail?id=1338 > > Best, > > Mariano >

Oct. 19, 2009

Re: [Pharo-project] [update] #10487

by Lukas Renggli

> I think that there are different scenarios (dev my app vs changing the > system) > Â and I can tell you that they are change like cleaning image segment > for which I would > love to have tests because I would be more Â confortable with fixing it. Yeah definitely, I completely agree. The tests are very valuable and should be run regularly. It is just for me as a normal user/developer (of Seaside) is not really interested in running the collection tests all the time. I am more interested in what tests pass (to chose the right image, to know the limitations) than in the tests themselves. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Oct. 19, 2009

Re: [Pharo-project] Fwd: [squeak-dev] The Trunk: Collections-nice.167.mcz

by Nicolas Cellier

This one is already in Pharo (md 7/24/2009) 2009/10/19 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > > Begin forwarded message: > >> From: Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> >> Date: October 19, 2009 3:00:19 PM GMT+02:00 >> To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>, stephane ducasse <stephane.ducasse(a)gmail.com >> > >> Subject: Fwd: [squeak-dev] The Trunk: Collections-nice.167.mcz >> >> Salut bis, >> >> Minor change to be integrated in pharo... >> >> Nicolas >> >> ---------- Forwarded message ---------- >> From: Â <commits(a)source.squeak.org> >> Date: 2009/10/19 >> Subject: [squeak-dev] The Trunk: Collections-nice.167.mcz >> To: squeak-dev(a)lists.squeakfoundation.org >> >> >> Nicolas Cellier uploaded a new version of Collections to project The >> Trunk: >> http://source.squeak.org/trunk/Collections-nice.167.mcz >> >> ==================== Summary ==================== >> >> Name: Collections-nice.167 >> Author: nice >> Time: 19 October 2009, 12:32:29 pm >> UUID: 95819d6c-2419-0244-bce5-75e402e44ec3 >> Ancestors: Collections-ar.166 >> >> http://bugs.squeak.org/view.php?id=7362 >> use self class instead of Text, so that we can subclass Text >> >> =============== Diff against Collections-ar.166 =============== >> >> Item was changed: >> Â ----- Method: Text>>reversed (in category 'converting') ----- >> Â reversed >> >> Â Â Â Â "Answer a copy of the receiver with element order reversed." >> >> Â Â Â Â ^ self class string: string reversed runs: runs reversed. >> >> Â Â " Â It is assumed that Â self size = runs size Â holds. "! >> >> Item was changed: >> Â ----- Method: Text>>copyFrom:to: (in category 'copying') ----- >> Â copyFrom: start to: stop >> Â Â Â Â "Answer a copied subrange of the receiver." >> >> Â Â Â Â | realStart realStop | >> Â Â Â Â stop > self size >> Â Â Â Â Â Â Â Â ifTrue: [realStop := self size] Â Â Â Â "handle >> selection at end of string" >> Â Â Â Â Â Â Â Â ifFalse: [realStop := stop]. >> Â Â Â Â start < 1 >> Â Â Â Â Â Â Â Â ifTrue: [realStart := 1] Â Â Â Â Â Â Â Â Â Â Â Â "handle >> selection before start of string" >> Â Â Â Â Â Â Â Â ifFalse: [realStart := start]. >> + Â Â Â ^self class >> - Â Â Â ^Text >> Â Â Â Â Â Â Â Â string: (string copyFrom: realStart to: realStop) >> Â Â Â Â Â Â Â Â runs: (runs copyFrom: realStart to: realStop)! > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 19, 2009

Re: [Pharo-project] [update] #10487

by StÃ©phane Ducasse

Lukas What I would like ideally is that I get a miniimage + a configuration + a **FAST** package loading so that we could load all the tests each time we integrate then we could have the tests not in the image. I think that there are different scenarios (dev my app vs changing the system) and I can tell you that they are change like cleaning image segment for which I would love to have tests because I would be more confortable with fixing it. Stef >>> Personally I would like to download an image *without* any tests, no >>> matter if this is a core or a dev image. And have included a >>> detailed >>> report on the results of running all the tests in that particular >>> image. >> >> But why, apart from the tiny image disk usage reduction. The test >> sometimes show how to use the, most times underdocumented, package. > > IMHO, that's a myth. Did a single test case ever in your entire life > help you to understand a piece of code? It never happened to me so far > :-) > > The rational behind my opinion is that I do not care about the tests > of the other packages when I develop software. Did you ever (other > than by accident) run the Collection or Compiler tests when you > developed some of your code? > > Btw, the same is true for the Monticello working copies. I frankly do > not care what version of Collection or Compiler is loaded in my image. > Sometimes I just drop all this information before I load my code. This > greatly reduces clutter. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 19, 2009

Re: [Pharo-project] [ANN] Pharo Core 1.0rc1

by Nicolas Cellier

See also http://code.google.com/p/pharo/issues/detail?id=1214 2009/10/19 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > Don't know... > Maybe the plan was to move it up in SequenceableCollection, like > http://bugs.squeak.org/view.php?id=7242 ? > > Nicolas > > 2009/10/19 Niko Schwarz <niko.schwarz(a)googlemail.com>: >> Then, why was sort: yanked from OrderedCollection? I'm confused. >> >> On Mon, Oct 19, 2009 at 9:17 PM, Nicolas Cellier >> <nicolas.cellier.aka.nice(a)gmail.com> wrote: >>> Implementation details: #sortBy: is not exactly #sort: >>> #sort: does a fast inplace sort, when #sortBy: performs useless copy >>> operations... >>> >>> Nicolas >>> >>> 2009/10/19 Niko Schwarz <niko.schwarz(a)googlemail.com>: >>>> That was me, it comes from Squeak trunk. I didn't test it, because it >>>> looked so harmless and works in Squeak â¦Â I'm sorry. It should be >>>> "sortBy: rather than sort:" >>>> >>>> niko >>>> >>>> On Mon, Oct 19, 2009 at 7:06 PM, Michael Roberts <mike(a)mjr104.co.uk> wrote: >>>>> MCMergeBrowser>>merger: >>>>> Â Â Â Â conflicts := aMerger conflicts sort: [:a :b | a operation <= b operation]. >>>>> >>>>> OrderedCollection dnu sort: >>>>> >>>>> introduced I guess >>>>> >>>>> http://code.google.com/p/pharo/issues/detail?id=1320 >>>>> >>>>> how was this change tested? >>>>> >>>>> thanks, >>>>> Mike >>>>> >>>>> On Mon, Oct 19, 2009 at 4:25 PM, Marcus Denker <denker(a)acm.org> wrote: >>>>>> http://gforge.inria.fr/frs/download.php/24363/PharoCore-1.0-10491rc1.zip >>>>>> >>>>>> The zip contains a new sources file. >>>>>> >>>>>> Â Â Â Â Marcus >>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >

Oct. 19, 2009

Re: [Pharo-project] [ANN] Pharo Core 1.0rc1

by Nicolas Cellier

Don't know... Maybe the plan was to move it up in SequenceableCollection, like http://bugs.squeak.org/view.php?id=7242 ? Nicolas 2009/10/19 Niko Schwarz <niko.schwarz(a)googlemail.com>: > Then, why was sort: yanked from OrderedCollection? I'm confused. > > On Mon, Oct 19, 2009 at 9:17 PM, Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> Implementation details: #sortBy: is not exactly #sort: >> #sort: does a fast inplace sort, when #sortBy: performs useless copy >> operations... >> >> Nicolas >> >> 2009/10/19 Niko Schwarz <niko.schwarz(a)googlemail.com>: >>> That was me, it comes from Squeak trunk. I didn't test it, because it >>> looked so harmless and works in Squeak â¦Â I'm sorry. It should be >>> "sortBy: rather than sort:" >>> >>> niko >>> >>> On Mon, Oct 19, 2009 at 7:06 PM, Michael Roberts <mike(a)mjr104.co.uk> wrote: >>>> MCMergeBrowser>>merger: >>>> Â Â Â Â conflicts := aMerger conflicts sort: [:a :b | a operation <= b operation]. >>>> >>>> OrderedCollection dnu sort: >>>> >>>> introduced I guess >>>> >>>> http://code.google.com/p/pharo/issues/detail?id=1320 >>>> >>>> how was this change tested? >>>> >>>> thanks, >>>> Mike >>>> >>>> On Mon, Oct 19, 2009 at 4:25 PM, Marcus Denker <denker(a)acm.org> wrote: >>>>> http://gforge.inria.fr/frs/download.php/24363/PharoCore-1.0-10491rc1.zip >>>>> >>>>> The zip contains a new sources file. >>>>> >>>>> Â Â Â Â Marcus >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 19, 2009

Re: [Pharo-project] [ANN] Pharo Core 1.0rc1

by Niko Schwarz

Then, why was sort: yanked from OrderedCollection? I'm confused. On Mon, Oct 19, 2009 at 9:17 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > Implementation details: #sortBy: is not exactly #sort: > #sort: does a fast inplace sort, when #sortBy: performs useless copy > operations... > > Nicolas > > 2009/10/19 Niko Schwarz <niko.schwarz(a)googlemail.com>: >> That was me, it comes from Squeak trunk. I didn't test it, because it >> looked so harmless and works in Squeak â¦Â I'm sorry. It should be >> "sortBy: rather than sort:" >> >> niko >> >> On Mon, Oct 19, 2009 at 7:06 PM, Michael Roberts <mike(a)mjr104.co.uk> wrote: >>> MCMergeBrowser>>merger: >>> Â Â Â Â conflicts := aMerger conflicts sort: [:a :b | a operation <= b operation]. >>> >>> OrderedCollection dnu sort: >>> >>> introduced I guess >>> >>> http://code.google.com/p/pharo/issues/detail?id=1320 >>> >>> how was this change tested? >>> >>> thanks, >>> Mike >>> >>> On Mon, Oct 19, 2009 at 4:25 PM, Marcus Denker <denker(a)acm.org> wrote: >>>> http://gforge.inria.fr/frs/download.php/24363/PharoCore-1.0-10491rc1.zip >>>> >>>> The zip contains a new sources file. >>>> >>>> Â Â Â Â Marcus >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 19, 2009