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

Re: [Pharo-dev] Url deprecated

by phil＠highoctane.be

FTP is easy, and setting up a monticello repo like this takes no time. Especially on whatever shared hosting account, my NAS, on my own box where I can share the package-cache folder that way. And it can be browsed as well. I am not in the mood of maintaining an STH instance with mongo and friends. I tried filetree and gitfiletree but those weren't supporting my workflow easily enough (and for some reason, I got a corrupt something w/ Bitbucket which let me fight with it for a full damn day). Keep FTP alive. Phil

Oct. 28, 2013

Re: [Pharo-dev] Url deprecated

by Marcus Denker

On 28 Oct 2013, at 11:19, phil(a)highoctane.be wrote: > FWIW I also have serious issues with MetacelloToolBox against an FTP repository. We should remove FTP. FTP is evil: the passed is passed in the clear, it is old, it makes problems with NAT and firewalls. FTP should *not* be used in 2013! Marcus

Oct. 28, 2013

Re: [Pharo-dev] Url deprecated

by phil＠highoctane.be

FWIW I also have serious issues with MetacelloToolBox against an FTP repository. Monticello works, but not the automated stuff It is related to the same kind of situation (Pharo 2.0). *MetacelloToolBox * * createDevelopment: '0.1'* * for: 'ConfigurationOfXXX'* * importFromBaseline: '0.1-baseline'* * description: 'initial development version'.* * * *(ConfigurationOfXXX project version: '0.1') load.* * * *(MetacelloToolBox validateConfiguration: ConfigurationOfXXX) explore.* * * *MetacelloToolBox* * updateToLatestPackageVersionsIn: ConfigurationOfXXX* * description: 'Made spinner work for Ajax'.* * * *"Does not seem to work, even if logged int the repository from Monticello"* *Gofer new* * url: 'ftp://ftp.xxx.com/mc';* * package: 'ConfigurationOfXXX';* * commit: 'Gofer test'.* * * *"This one does not work"* *MetacelloToolBox* * saveConfigurationPackageFor: 'ConfigurationOfXXX' description: 'Added config'.* Phil On Mon, Oct 28, 2013 at 11:18 AM, Goubier Thierry <thierry.goubier(a)cea.fr>wrote: > Hi All, > > Url has been deprecated. What is to be done with the Monticello use of the > subclasses of Url? > > At the moment, ZnUrl has a hardcoded case switch to redirect on the right > type of repository [1], but... It's not extendable, and breaks > gitfiletree://. > > [1] https://github.com/pharo-**project/pharo-core/blob/** > e89b4ac70d5cef761667317d58a449**6d443d8a4e/Gofer-Core.package/** > extension/ZnUrl/instance/**mcRepositoryAsUser_**withPassword_.st<https://github.com/pharo-project/pharo-core/blob/e89b4ac70d5cef761667317d58…> > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > >

Oct. 28, 2013

Url deprecated

by Goubier Thierry

Hi All, Url has been deprecated. What is to be done with the Monticello use of the subclasses of Url? At the moment, ZnUrl has a hardcoded case switch to redirect on the right type of repository [1], but... It's not extendable, and breaks gitfiletree://. [1] https://github.com/pharo-project/pharo-core/blob/e89b4ac70d5cef761667317d58… Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Oct. 28, 2013

Re: [Pharo-dev] Url deprecated

by Sven Van Caekenberghe

Thierry, ZnUrl now implements #mcRepositoryAsUser:withPassword: though it is currently a hack. Do you have a suggestion how to make it extendable ? I will think about it as well, I do have some ideas. Sven On 28 Oct 2013, at 11:18, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > Hi All, > > Url has been deprecated. What is to be done with the Monticello use of the subclasses of Url? > > At the moment, ZnUrl has a hardcoded case switch to redirect on the right type of repository [1], but... It's not extendable, and breaks gitfiletree://. > > [1] https://github.com/pharo-project/pharo-core/blob/e89b4ac70d5cef761667317d58… > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

Oct. 28, 2013

github repository documentation

by Camillo Bruni

It would be nice to add a README.md file to the following github repositories: https://github.com/pharo-project/pharo-project-proposals https://github.com/pharo-project/pharo-ubuntu https://github.com/pharo-project/pharo-flyers https://github.com/pharo-project/pharo-ci I will take care of https://github.com/pharo-project/pharo-core I think as a rule of thumb we should point to the jenkins job that validates or generates the contents of the repository...

Oct. 28, 2013

Re: [Pharo-dev] SmalltalkHub red

by Manfred KrÃ¶hnert

Hi everyone, are there any news on this issue? I tried to load SmalltalkHub into a new Pharo 2.0 image yesterday and was hit by this. Best, Manfred On Wed, Oct 9, 2013 at 9:33 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Yes, running the Grease/Seaside tests works fine. But, you will only see > the "packages" problems when you do something with packages. So you will > have to trigger RPackage tests to notice the issue. > > After all, you spotted the issue by running the Pharo regression tests > after loading Moose/Grease/Seaside. > > Doru > > > On Wed, Oct 9, 2013 at 9:28 PM, Camillo Bruni <camillobruni(a)gmail.com>wrote: > >> so is seaside: https://ci.inria.fr/pharo-contribution/job/Seaside/ >> >> On 2013-10-09, at 17:48, Damien Cassou <damien.cassou(a)gmail.com> wrote: >> > On Wed, Oct 9, 2013 at 4:47 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >> wrote: >> >> Do you know who is working with grease? It doesn't sound too hard to >> solve this. >> > >> > >> > and Grease seems to be ok: >> https://ci.inria.fr/pharo-contribution/job/Grease/ >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Oct. 28, 2013

Re: [Pharo-dev] About SqNumberParser

by Yuriy Tymchuk

So what we decide to do with this? I can work on that case, but I have 2 questions: - do we care to provide parsing of numbers in other notations as Pharo one? - what is the number syntax that we want to support? Cheers! Uko On 19 Aug 2013, at 10:05, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > thanks! > > Stef > >> I think just because 1.0s was explicitely not supported in Squeak? >> There should be some related tests... >> It should be rather simple to change. >> >> >> 2013/8/13 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> Hi nicolas >> >> We would really like to have only one number parser in Pharo as well as handling the 1.0s syntax >> marcus raised a question that I could not answer. >> Do you habve nfrmation to share with us so that we can take a decision? >> >> Stef >> >> >> so the strange thing is that this is *explicitly* implemented in SqNumberParser to not allow 2.0s >> >> - do not allow single s without following digits as ScaledDecimal >> >> It is not explained why this is a good idea. >> >> In general, we need to merge the whole NumberParser hierarchy into one class, i don't understand why we have three classes now. >> >

Oct. 28, 2013

[pharo-project/pharo-core] 492feb: 30531

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 492febd8938e9297e738a96d75911521f9eee5e0 https://github.com/pharo-project/pharo-core/commit/492febd8938e9297e738a96d… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-28 (Mon, 28 Oct 2013) Changed paths: M CollectionsTests.package/StringTest.class/instance/tests - converting/testUnescapePercentsWithTextEncoding.st M FileSystem-Core.package/AbstractFileReference.class/instance/accessing/uri.st M Monticello.package/MCHttpRepository.class/instance/actions/parseFileNamesFromStream_.st M Monticello.package/MCHttpRepository.class/instance/actions/urlForFileNamed_.st M MonticelloFileTree-Core.package/extension/String/instance/cypressEscape.st M MonticelloFileTree-Core.package/extension/String/instance/cypressUnescape.st A Multilingual-OtherLanguages.package/extension/HTTPEncodingTest/instance/testPercentEncodingHiragana.st R Multilingual-OtherLanguages.package/extension/HTTPEncodingTest/instance/testPercentEncodingJa.st M Multilingual-OtherLanguages.package/extension/StringTest/instance/testUnescapePercents.st M Multilingual-TextConversion.package/extension/String/instance/unescapePercents.st M Multilingual-TextConversion.package/extension/String/instance/unescapePercentsWithTextEncoding_.st M Network-Protocols.package/extension/String/instance/encodeForHTTP.st M Network-Protocols.package/extension/String/instance/encodeForHTTPWithTextEncoding_.st M Network-Protocols.package/extension/String/instance/encodeForHTTPWithTextEncoding_conditionBlock_.st M Network-Url.package/FileUrl.class/instance/paths/pathString.st M Network-Url.package/FileUrl.class/instance/printing/printOn_.st M Network-Url.package/FileUrl.class/instance/private-initialization/initializeFromPathString_.st M Network-Url.package/FileUrl.class/instance/private-initialization/privateInitializeFromText_relativeTo_.st M Network-Url.package/HierarchicalUrl.class/instance/parsing/privateInitializeFromText_.st M Network-Url.package/HierarchicalUrl.class/instance/parsing/privateParsePath_relativeTo_.st M Network-Url.package/HierarchicalUrl.class/instance/printing/fullPath.st M Network-Url.package/HierarchicalUrl.class/instance/printing/printOn_.st M NetworkTests.package/HTTPEncodingTest.class/instance/as yet unclassified/testEncodeForHTTP.st M NetworkTests.package/UrlTest.class/instance/tests/testUsernamePasswordEncoded2.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script186.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30531.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tools.package/MethodFinder.class/instance/initialize/initialize2.st Log Message: ----------- 30531 6368 deprecate unescapePercents and encodeForHTTP https://pharo.fogbugz.com/f/cases/6368 http://files.pharo.org/image/30/30531.zip

Oct. 28, 2013

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30531 Home: https://github.com/pharo-project/pharo-core

Oct. 28, 2013