- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Including Zinc HTTP Components in Pharo 1.2 Dev ?

by csrabak＠bol.com.br

;-) I was going to comment on this apparent 'counterpoint' asap! I think this shows Pharo is ripe for having something similar another Open Source project has called "Zip Picker"Â¹. We could have a simpler dev image which would have in a Welcome or similar space a picker (buttons or radio buttons) which select preconfigured Metacello scripts to download the complimentary packages for what the developer is interested in. my 0.01999... -- Cesar Rabak [1] DJGPP http://www.delorie.com/djgpp/zip-picker.html Em 07/01/2011 11:27, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr > escreveu: Another one :) We were looking at the users of ZnUtils and I have the impression that it would be good to split it so that we get several groups of coherent users. there are the groups for - networking + constants - http ... so this way people could reuse the networking + constants parts for others protocols. Stef

Jan. 7, 2011

[Pharo-project] Adding hudson links from pharo webpage?

by Mariano Martinez Peck

Now that hudson seems to be working fine, I think it is a good moment to link hudson links from the pharo website. cheers mariano

Jan. 7, 2011

Re: [Pharo-project] Issue 3516 in pharo: Failing tests in MetaCello

by pharo＠googlecode.com

Comment #3 on issue 3516 by marianopeck: Failing tests in MetaCello http://code.google.com/p/pharo/issues/detail?id=3516 Dale, yes, they are failing in the image you can get from hudson: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/…

Jan. 7, 2011

Re: [Pharo-project] Issue 3224 in pharo: Migrating MethodReference to MethodReferenceWithSource

by pharo＠googlecode.com

Comment #12 on issue 3224 by stephane.ducasse: Migrating MethodReference to MethodReferenceWithSource http://code.google.com/p/pharo/issues/detail?id=3224 Here are new changeset breaking the tests but that should be used to make progress Attachments: FixingMethodReference.1.cs 43.1 KB FixingMethodReference-AddOns.1.cs 1.7 KB

Jan. 7, 2011

Re: [Pharo-project] Issue 3516 in pharo: Failing tests in MetaCello

by pharo＠googlecode.com

Comment #2 on issue 3516 by da...(a)teleport.com: Failing tests in MetaCello http://code.google.com/p/pharo/issues/detail?id=3516 Before I get too far into trying to reproduce this problem ... is there a particular version of Pharo1.2 in which this is failing and does it fail in the core or only in the dev image? if in the dev image, is there a pre-built dev image available? If no dev image is available which version of Pharo1.2 core image is the basis for building a dev image? Right now I will go on the assumption that it's failing in an updated version of PharoCore1.2 and will see if the error reproduces there...

Jan. 7, 2011

Re: [Pharo-project] Origins [poll]

by Guillermo Polito

Jan. 7, 2011

Re: [Pharo-project] Origins [poll]

by Diogenes Moreira

Jan. 7, 2011

Re: [Pharo-project] Issue 3436 in pharo: #copyFrom: is broken

by pharo＠googlecode.com

Comment #18 on issue 3436 by cesar.rabak: #copyFrom: is broken http://code.google.com/p/pharo/issues/detail?id=3436 Your comments show consistency with your vision stated above about the need of an overhaul on the design of the interface (a.k.a. "API"), if you take the bulk of it. In order to sustain a civilized dialog, I need to concede you with this doubt. However, it seems to me this is flaring the judgment of proposal here: The method name has *copy* in it, hasn't? I _does_ return a *copy* of the object, doesn't? This issue #3436 is about: is it more adequate that a method called "copyFrom:" copies the state of an object or a part of one when it is a SequenceableCollection? Your other points have to be addressed elsewhere, be it in the mailing list as a preliminary discussion or as proposal here via a well formed issue. In order to avoid any doubts, my stance is that we adopt copyFrom: as an alias (or 'short cut') to "#copyFrom: start to: (self size)" in the most appropriate point of the Pharo object's hierarchy.

Jan. 7, 2011

Re: [Pharo-project] Issue 3516 in pharo: Failing tests in MetaCello

by pharo＠googlecode.com

Updates: Cc: da...(a)teleport.com Comment #1 on issue 3516 by marianopeck: Failing tests in MetaCello http://code.google.com/p/pharo/issues/detail?id=3516 (No comment was entered for this change.)

Jan. 7, 2011

Re: [Pharo-project] Issue 3516 in pharo: Failing tests in MetaCello

by Mariano Martinez Peck

I cc'ed metacello On Fri, Jan 7, 2011 at 3:34 PM, <pharo(a)googlecode.com> wrote: > Status: Accepted > Owner: marcus.denker > Labels: Milestone-1.2-DevImage > > New issue 3516 by marcus.denker: Failing tests in MetaCello > http://code.google.com/p/pharo/issues/detail?id=3516 > > Metacello.TestsReference.MetacelloReferenceTestCase.testReferenceConfig >>>> 0.0020 9 >>>> Metacello.TestsReference.MetacelloReferenceTestCase.testReferenceConfigPrintString >>>> 0.0060 9 >>>> >>> > >

Jan. 7, 2011