April 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Shorter Pharo Launcher download link

by Sean P. DeNigris

Dmitri Zagidulin wrote > Unfortunately, as far as I know, the download link for it is: > > https://ci.inria.fr/pharo/view/Launcher/job/Launcher/PHARO=40,VERSION=stabl… The Launcher artifacts are mirrored at http://files.pharo.org/platform/launcher/. Maybe we should do the same with the book(s)? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Shorter-Pharo-Launcher-download-link-tp4818944p481896… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 10, 2015

Re: [Pharo-dev] Shorter Pharo Launcher download link

by Dmitri Zagidulin

Who would be the people to talk to? (Who set up or runs pharo.org, for example? Does it have Apache in front of whatever app is serving the website, or do web requests hit pharo directly?) On Fri, Apr 10, 2015 at 1:22 PM, stepharo <stepharo(a)free.fr> wrote: > Having launcher.pharo.org would be cool. > Now I do not know how to do such binding. > > > Le 10/4/15 18:41, Dmitri Zagidulin a Ã©crit : > > This is in the same vein as Sean's recent 'Clean up Download Instructions' > email. > > While updating the Pharo By Example chapter on installing Pharo, we > decided to mention the Pharo Launcher project as a convenient way to use > multiple images, etc. > > Unfortunately, as far as I know, the download link for it is: > > > https://ci.inria.fr/pharo/view/Launcher/job/Launcher/PHARO=40,VERSION=stabl… > > (And even then, you have to scroll down to the tiny 'Last Successful > Artifacts' section). > > That's a bit awkward to put in a book for people to type out, to say the > least. > > Is there any way we can either: > > 1) Use an existing URL shortener to link to that > 2) Have some Apache-redirected URLs off of pharo.org? Something like > pharo.org/launcher/ that would have the download links to the various > Launcher builds? > > > The same also goes for some of the books, by the way. In a later > chapter, we link to Pharo for the Enterprise, and we actually type out the > link: > > https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… > > Sub-optimal. :) > > > >

April 10, 2015

Re: [Pharo-dev] Shorter Pharo Launcher download link

by stepharo

Having launcher.pharo.org would be cool. Now I do not know how to do such binding. Le 10/4/15 18:41, Dmitri Zagidulin a Ã©crit : > This is in the same vein as Sean's recent 'Clean up Download > Instructions' email. > > While updating the Pharo By Example chapter on installing Pharo, we > decided to mention the Pharo Launcher project as a convenient way to > use multiple images, etc. > > Unfortunately, as far as I know, the download link for it is: > > https://ci.inria.fr/pharo/view/Launcher/job/Launcher/PHARO=40,VERSION=stabl… > > (And even then, you have to scroll down to the tiny 'Last Successful > Artifacts' section). > > That's a bit awkward to put in a book for people to type out, to say > the least. > > Is there any way we can either: > > 1) Use an existing URL shortener to link to that > 2) Have some Apache-redirected URLs off of pharo.org > <http://pharo.org>? Something like pharo.org/launcher/ > <http://pharo.org/launcher/> that would have the download links to the > various Launcher builds? > > > The same also goes for some of the books, by the way. In a later > chapter, we link to Pharo for the Enterprise, and we actually type out > the link: > https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… > > Sub-optimal. :) > >

April 10, 2015

Re: [Pharo-dev] [Urgent]: Clean up Download Instructions before 4.0 Release

by stepharo

super! Mega tx I will let esteban handle the access part :) Le 10/4/15 18:11, Sean P. DeNigris a Ã©crit : > Esteban A. Maringolo wrote >> This particular comment let me hanging though: >> https://news.ycombinator.com/item?id=5395496 >> >> We should pay special attention to those feedbacks, otherwise we'll be >> always "preaching to the choir". > We handled two out of three of the poster's difficulties: > 1. Nuke one-click in favor of platform-specific downloads > 2. Add a warning about the 32-bit lib requirement to the download to the > README > > However... I tried installing on Ubuntu and Debian from the perspective of a > new user based on the instructions at http://pharo.org/download and they are > a shambles! Very confusing and incomplete. > > Two requests: > - some clarifications and changes are straightforward and non-controversial. > Will someone give me access to edit the website directly? > - for the rest, and things I'm not sure about, I created > https://github.com/pharo-project/pharo-workingRoadmaps/blob/master/Download… > to keep track of things that need to be changed > > I also created Issue 15328: "Clean up Download Instructions before 4.0 > Release" https://pharo.fogbugz.com/default.asp?15328 which references the > roadmap > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Urgent-Clean-up-Download-Instructions-before-4-0-Rele… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

April 10, 2015

Re: [Pharo-dev] [Urgent]: Clean up Download Instructions before 4.0 Release

by Peter UhnÃ¡k

> > However... I tried installing on Ubuntu and Debian from the perspective of > a > new user based on the instructions at http://pharo.org/download and they > are > a shambles! Very confusing and incomplete. > As a debian user I have to ask, why is there a separate zeroconf for debian downloading some "swing" vm? The normal zeroconf works just fine (provided you have 32bit support, but that is needed also for swing). So a sentence about what is different would be be nice (especially considering the build is 6 months old and unlike pharo-vm master branch I don't see any newer version). Also, why do we need separate VMs between ubuntu and debian? I compiled my VM (for reasons), but I compiled it on Ubuntu 32bit (in virtual machine), and am running it on 64bit debian, so it should be compatible. Probably even the ubuntu .deb works (as with many ubuntu "only" packages). Peter

April 10, 2015

Shorter Pharo Launcher download link

by Dmitri Zagidulin

This is in the same vein as Sean's recent 'Clean up Download Instructions' email. While updating the Pharo By Example chapter on installing Pharo, we decided to mention the Pharo Launcher project as a convenient way to use multiple images, etc. Unfortunately, as far as I know, the download link for it is: https://ci.inria.fr/pharo/view/Launcher/job/Launcher/PHARO=40,VERSION=stabl… (And even then, you have to scroll down to the tiny 'Last Successful Artifacts' section). That's a bit awkward to put in a book for people to type out, to say the least. Is there any way we can either: 1) Use an existing URL shortener to link to that 2) Have some Apache-redirected URLs off of pharo.org? Something like pharo.org/launcher/ that would have the download links to the various Launcher builds? The same also goes for some of the books, by the way. In a later chapter, we link to Pharo for the Enterprise, and we actually type out the link: https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… Sub-optimal. :)

April 10, 2015

[Urgent]: Clean up Download Instructions before 4.0 Release

by Sean P. DeNigris

Esteban A. Maringolo wrote > This particular comment let me hanging though: > https://news.ycombinator.com/item?id=5395496 > > We should pay special attention to those feedbacks, otherwise we'll be > always "preaching to the choir". We handled two out of three of the poster's difficulties: 1. Nuke one-click in favor of platform-specific downloads 2. Add a warning about the 32-bit lib requirement to the download to the README However... I tried installing on Ubuntu and Debian from the perspective of a new user based on the instructions at http://pharo.org/download and they are a shambles! Very confusing and incomplete. Two requests: - some clarifications and changes are straightforward and non-controversial. Will someone give me access to edit the website directly? - for the rest, and things I'm not sure about, I created https://github.com/pharo-project/pharo-workingRoadmaps/blob/master/Download… to keep track of things that need to be changed I also created Issue 15328: "Clean up Download Instructions before 4.0 Release" https://pharo.fogbugz.com/default.asp?15328 which references the roadmap ----- Cheers, Sean -- View this message in context: http://forum.world.st/Urgent-Clean-up-Download-Instructions-before-4-0-Rele… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 10, 2015

Fwd: [Moose-dev] Re: Wrong version loaded using Metacello

by stephan

-------- Forwarded Message -------- Subject: [Moose-dev] Re: Wrong version loaded using Metacello Date: Fri, 10 Apr 2015 17:10:54 +0200 From: Jan KurÅ¡ <kurs.jan(a)gmail.com> Reply-To: Moose-related development <moose-dev(a)iam.unibe.ch> To: Moose-related development <moose-dev(a)iam.unibe.ch> Hi Dale, That works for me! Do you have any idea, when will this fix appear in Pharo? Thank you for fixing this! Cheers, Jan On 9 April 2015 at 04:33, Dale Henrichs <dale.henrichs(a)gemtalksystems.com <mailto:dale.henrichs@gemtalksystems.com>> wrote: Jan, I believe that I've fixed the bug [1], but of course the proof will be in the pudding:) So If you could run the following Metacello update script in your image (this will work in pharo3.0 or pharo4.0) and make sure it works for you: Metacello new Ã baseline: 'Metacello'; Ã repository: 'github://dalehenrich/metacello-work:master/repository'; Ã get. Metacello new Ã baseline: 'Metacello'; Ã repository: 'github://dalehenrich/metacello-work:master/repository'; Ã onConflict: [:ex | ex allow]; Ã load The proper package was loaded for me in my test in Pharo3.0: Ã Ã Ã Loaded -> PetitIndent-JanKurs.1 --- http://smalltalkhub.com/mc/Moose/PetitParser/main/ --- cache Dale [1] https://github.com/dalehenrich/metacello-work/issues/339 On 04/08/2015 12:14 AM, Jan KurÃÂ¡ wrote: > Dale, Thank you for the information and your help. And honestly, I > am surprised as well :) > > Cheers, > Jan > > On 7 April 2015 at 23:21, Dale Henrichs > <dale.henrichs(a)gemtalksystems.com > <mailto:dale.henrichs@gemtalksystems.com>> wrote: > > Jan, > > This looks like a bug in MetacelloGoferPackage>>matches: ...Ã > I've submitted a bug[1] and will work on getting a patch out > as soon as I can ... I am a bit surprised that this particular > bug has remained hidden (or unreported) for so long, but it is > a good find ... thanks for provided the details I needed to > identify the problem ... > > Dale > > [1] https://github.com/dalehenrich/metacello-work/issues/339 > > > On 04/07/2015 09:08 AM, Jan KurÃÂ¡ wrote: >> Hi Dale, >> >> One can reproduce the behaviour by evaluating this in Pharo 3 >> or Pharo 4 image: >> >> Gofer new smalltalkhubUser: 'Moose' project: 'PetitParser'; >> Ã Ã Ã configurationOf: #PetitParser; load. >> >> (ConfigurationOfPetitParser project version: '1.10') load. >> >> The first command loads (in my case) >> ConfigurationOfPetitParser (JanKurs.68) >> >> When I evaluate: >> (ConfigurationOfPetitParser project version: '1.10') record >> asString. >> >> I get: >> a MetacelloNullRecordingMCSpecLoader(linear load : >> Ã Ã Ã linear load : 1.10 [ConfigurationOfPetitParser] >> Ã Ã Ã Ã Ã Ã load : ConfigurationOfGlamour >> Ã Ã Ã atomic load : 1.10 [ConfigurationOfPetitParser] >> Ã Ã Ã Ã Ã Ã load : PetitParser-JanKurs.262 >> Ã Ã Ã Ã Ã Ã load : PetitTests-JanKurs.67 >> Ã Ã Ã Ã Ã Ã Ã ... >> Ã Ã Ã Ã Ã Ã Ã ... >> Ã Ã Ã Ã Ã Ã load : PetitIslands-JanKurs.18 >> Ã Ã Ã Ã Ã Ã load : PetitIndent-JanKurs.1 >> Ã Ã Ã Ã Ã Ã load : Factorial-Language-lr.6 >> Ã Ã Ã Ã Ã Ã explicit load : Glamour >> Ã Ã Ã Ã Ã Ã Ã Ã Ã load : ConfigurationOfGlamour-AndreiChis.203 >> Ã Ã Ã Ã Ã Ã linear load : 3.0.6 [ConfigurationOfGlamour] >> Ã Ã Ã Ã Ã Ã Ã ... >> >> >> Yet if I really load, the transcript shows (see the full >> transcript in the attachement): >> >> >> Loading 1.10 of ConfigurationOfPetitParser... >> Fetched -> ConfigurationOfGlamour-AndreiChis.203 --- >> http://smalltalkhub.com/mc/Moose/Glamour/main/ --- >> http://smalltalkhub.com/mc/Moose/Glamour/main/ >> Loaded -> ConfigurationOfGlamour-AndreiChis.203 --- >> http://smalltalkhub.com/mc/Moose/Glamour/main/ --- >> /home/kursjan/tmp/pharo16/package-cache >> Fetched -> PetitParser-JanKurs.262 --- >> http://smalltalkhub.com/mc/Moose/PetitParser/main/ --- >> http://smalltalkhub.com/mc/Moose/PetitParser/main/ >> Fetched -> PetitTests-JanKurs.67 --- >> http://smalltalkhub.com/mc/Moose/PetitParser/main/ --- >> http://smalltalkhub.com/mc/Moose/PetitParser/main/ >> ... >> ... >> Fetched -> PetitIndent-JanKurs.11 --- >> http://smalltalkhub.com/mc/Moose/PetitParser/main/ --- >> http://smalltalkhub.com/mc/Moose/PetitParser/main/ >> ... >> ... >> >> >> >> Cheers, >> Jan >> >> On 6 April 2015 at 23:23, Dale Henrichs >> <dale.henrichs(a)gemtalksystems.com >> <mailto:dale.henrichs@gemtalksystems.com>> wrote: >> >> Jan, >> >> I would really like to see the Transcript output for this >> load .... also I'd like to know which mcz version of >> ConfigurationOfPetitParser you are using ... I can guess, >> but there are often a number of different versions of >> configurations floating around and I don't want to waste >> time on a version that does not match the one that you >> are having trouble with ... >> >> Dale >> >> >> On 04/04/2015 03:01 AM, Jan KurÃÂ¡ wrote: >>> Hi All, >>> >>> In ConfigurationOfPetitParser, there is a stable version >>> 1.10 for Pharo 3.0 which says to load version >>> PetitIndent.JanKurs.1. >>> >>> version110: spec >>> Ã Ã Ã <version: '1.10' imports: #('1.6-baseline' )> >>> >>> Ã Ã Ã spec for: #'common' do: [ >>> >>> Ã Ã Ã .. >>> Ã Ã Ã package: 'PetitIndent' with: 'PetitIndent-JanKurs.1'; >>> Ã Ã Ã .. >>> >>> Yet, if I load the stable version from Pharo 3.0: >>> >>> Gofer new smalltalkhubUser: 'Moose' project: 'PetitParser'; >>> Ã Ã Ã configurationOf: #PetitParser; load. >>> (ConfigurationOfPetitParser project version: '1.10') load. >>> >>> >>> >>> I got PetitIndent.JanKurs.11 loaded, which is very >>> unfortunate, since other packages are kept old. >>> >>> Does anyone knows why is this? >>> >>> Cheers, >>> Jan >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

April 10, 2015

Re: [Pharo-dev] why we removed debugTest from nautilus?

by ClÃ©ment Bera

Well I guess I used to click proceed and not close the debugger... 2015-04-10 1:24 GMT-07:00 Max Leske <maxleske(a)gmail.com>: > For a little more context: the issue was originally raised by Clara in the > thread titled "MNU: receiver of "stepToCallee:" is nilâ. IIRC the issue > was easily reproducible when debugging a test, then closing the debugger > (via the close icon). Clicking âProceedâ on the other hand gracefully > terminated the process. > > Cheers, > Max > > > On 10 Apr 2015, at 09:56, Nicolai Hess <nicolaihess(a)web.de> wrote: > > 2015-04-10 2:37 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: > >> I was using it frequently too and I have never experienced any issues... >> > > Ok, can you describe a use case, what test case you can start and > close the debugger without image freeze? > > Maybe we can find what is the difference between that > test case and those that freeze the image, and than find a fix. > > >> >> 2015-04-09 14:58 GMT-07:00 Nicolai Hess <nicolaihess(a)web.de>: >> >> >>> 2015-04-09 23:38 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: >>> >>>> No Debug Tests? >>>> >>>> Geez, I am using that all the time. >>>> >>> >>> And you're never encountered this issue 14689 >>> <https://pharo.fogbugz.com/default.asp?14689>? >>> Or did this work in older versions? >>> >>> >>> >>> >>>> >>>> Phil >>>> >>>> >>>> On Thu, Apr 9, 2015 at 10:21 PM, Marcus Denker <marcus.denker(a)inria.fr> >>>> wrote: >>>> >>>>> >>>>> > On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean(a)clipperadams.com> >>>>> wrote: >>>>> > >>>>> > Nicolai Hess wrote >>>>> >> >>>>> http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-… >>>>> > >>>>> > Ah, I miss that too! From that thread, it seems it was removed >>>>> temporarily >>>>> > until we have real breakpoints. Is there an issue for its return? >>>>> > >>>>> >>>>> Not yet. >>>>> >>>>> Marcus >>>>> >>>> >>>> >>> >> > >

April 10, 2015

Problem during the loading of setting on Pharo 4

by Ferlicot D. Cyril

Hi ! I use Pharo Launcher and each time I open a new Pharo 4 image, this image load my Pharo 4 settings. But since the version 40601 when Pharo load the settings i've an error: "MessageNotUnderstood: GTPlayBook class>> customDirectory:". If others have the same problem i'll open a bug repport.

April 10, 2015