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

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

by Sven Van Caekenberghe

On 07 Jan 2011, at 14:27, StÃ©phane Ducasse wrote: > 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 Name: Zinc-HTTP-SvenVanCaekenberghe.112 Author: SvenVanCaekenberghe Time: 7 January 2011, 7:52:57 pm UUID: 845f67f8-df1c-40cf-a644-4699f50bc3bb Ancestors: Zinc-HTTP-SvenVanCaekenberghe.111 split of ZnNetworkingUtils from ZnUtils to separate related functionality (Thx S.Ducasses)

Jan. 7, 2011

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

by Sven Van Caekenberghe

On 07 Jan 2011, at 14:14, StÃ©phane Ducasse wrote: > BTW it was thinking that the expected a JPEG should be more > inadequate mimetype or something else. > > Stef > > getImageOfType: mimeType usingParser: parserClass fromUrl: urlObject > | url stream request response | > url := urlObject asZnUrl. > stream := ZnUtils socketStreamToUrl: url. > (request := ZnRequest get: url) > setAccept: mimeType. > response := self executeOneShot: request on: stream. > response status = 200 ifFalse: [ > ^ self error: 'Expected OK response' ]. > response contentType = mimeType ifFalse: [ > ^ self error: 'Expected a JPEG' ]. Name: Zinc-HTTP-SvenVanCaekenberghe.111 Author: SvenVanCaekenberghe Time: 7 January 2011, 7:35:18 pm UUID: d633bf09-4617-4e34-b6c7-0260dc759817 Ancestors: Zinc-HTTP-SvenVanCaekenberghe.110 fixed ZnClient class>>#getImageOfType:usingParser:fromUrl: to correctly report responses with unexpected mime types (Thx S.Ducasses)

Jan. 7, 2011

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

by Tudor Girba

Currently, the link is here: http://pharo-project.org/community Cheers, Doru On 7 Jan 2011, at 19:22, Mariano Martinez Peck wrote: > 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 -- www.tudorgirba.com "The coherence of a trip is given by the clearness of the goal."

Jan. 7, 2011

[Pharo-project] Announcements in core images?

by Janko MivÅ¡ek

Hi both Squeakers and Pharoers, What is a status of Announcements package as part of core images? Are they already there and, are they compatible, and if not, what are the differences? Announcements are namely very important and elegant way of event notifications based on publish/subscribe pattern. And they are portable, which is very important for us, doing cross platform frameworks like Aida, Seaside, etc. Therefore I'd really like to see Announcements included in all Smalltalks by default and at least on API level as same as possible. Best regards Janko -- Janko MivÅ¡ek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si

Jan. 7, 2011

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

by pharo＠googlecode.com

Comment #19 on issue 3436 by step...(a)stack.nl: #copyFrom: is broken http://code.google.com/p/pharo/issues/detail?id=3436 Nicolas wrote: > All the other messages could have had the copy prepended if it was a > question of homogeneitty with existing API. > The fact is that they were added later than copy and copyFrom:to: > Of course, we can as well remove the copy prefix, but do we really care ? > Is it really what makes the message ambiguous ? It is one of the ambigueties. > If I wouldn't know about the message, my question would not be about > whether or not the message triggers a copy. > It would be whether the argument are elements or indices. - does it return a copy or change self - does it return a collection or an element - are arguments elements or indices should be reflected in the naming of the method, if one wants to avoid having to read the implementation/comments. Currently, every method having copy in its name has to be examined closely, to be able to decide what behavior should be expected. Overriding semantics is less than helpful, as that leads to more confusion. As long as there is no clear naming convention, it is better to add new method names than to overlay new behavior on existing ones.

Jan. 7, 2011

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