March 2018 - Pharo-dev - lists.pharo.org

New ConfigurationOfZincHTTPComponents

by Sven Van Caekenberghe

Just a quick heads up: there is a new ConfigurationOfZincHTTPComponents with a version 2.9.1 (based on a new baseline 2.9), not yet declared stable. [ In the Zn MC repos ] This version contains the changes made recently by Guille to streams in Pharo 7. It should be possible to load this version in various Pharo versions without breaking anything fundamental. However, the CI is not yet happy and I don't yet know why, hence I hesitate to declare this a stable version. I will try to figure this out tomorrow. === Name: ConfigurationOfZincHTTPComponents-SvenVanCaekenberghe.113 Author: SvenVanCaekenberghe Time: 14 March 2018, 8:55:19.156462 pm UUID: ebb9d97d-c623-0d00-bd15-c17e09f900fd Ancestors: ConfigurationOfZincHTTPComponents-SvenVanCaekenberghe.112 new 2.9 baseline and 2.9.1 version, not yet declared stable incorporates pharo 7 stream changes by Guille ter === Sven

March 14, 2018

[Pharo 7.0-dev] Build #696: 21575-Method-classCommentBlank-should-not-return-actual-class-comment

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #696 was: FAILURE. The Pull Request #1092 was integrated: "21575-Method-classCommentBlank-should-not-return-actual-class-comment" Pull request url: https://github.com/pharo-project/pharo/pull/1092 Issue Url: https://pharo.fogbugz.com/f/cases/21575 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 14, 2018

[Pharo 7.0-dev] Build #695: Fixed mc writing

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #695 was: SUCCESS. The Pull Request #1091 was integrated: "Fixed mc writing" Pull request url: https://github.com/pharo-project/pharo/pull/1091 Issue Url: https://pharo.fogbugz.com/f/cases/21574 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 14, 2018

Re: [Pharo-dev] [Pharo-users] Something is happening...

by Esteban A. Maringolo

Do we have any metrics on the number of visits we get on the pharo.org website, which parts are the most visited, etc? The same regarding web downloads, and so on. I understand that CI can distort download count if using only access logs, but certainly if we count a download through the webpage as a "conversion" (and track it somehow) we would have a better idea how big this is becoming. But back to your point and as a bystander these days, it is very hard to be aware of everything that's going on in the Pharo world, and not because of the associated noise, because there is actually a lot of things going on. :) Regards, Esteban A. Maringolo 2018-03-13 4:27 GMT-03:00 Marcus Denker <marcus.denker(a)inria.fr>: > Hi, > > There is something odd happeningâ¦ or better: There is *a lot* happening. > > Just one example: for the Newsletter, the original idea was to send out once > a month a post with 3 things, some of them recycled (e.g. pointers to > existing projects, re-use âsuccess storiesâ, things like that. > > Now already some months ago I had to add âand here are some other > interesting announcements, blog posts, videosâ. > > But this month, the list of things for the newsletter TODO list contains > over 60 entries. With the exception of maybe 5, these are just things that > happened between sending the February newsletter and today. > > Newsletter March should be ready till this thursday, I hope, subscribe or > read the oder ones here: http://newsletter.pharo.org > > Marcus

March 14, 2018

Re: [Pharo-dev] Experiment: New Download page based on Pharo Launcher

by Marcus Denker

Ok, I will fix that in the next pass. > On 9 Mar 2018, at 18:10, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Marcus Denker-4 wrote >> comments welcomeâ¦ > > IHMO the structure is a little confusing because the first heading "Usage" > (Launcher implied) is on the same level as other methods like "Linux > Packages". I think there needs to be something like a header one level > higher like "Other Options" between these two sections. > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

March 14, 2018

Re: [Pharo-dev] Experiment: New Download page based on Pharo Launcher

by Marcus Denker

> On 9 Mar 2018, at 23:34, Torsten Bergmann <astares(a)gmx.de> wrote: > > Additional portable versions would be nice too (based on a simple ZIP) instead of only the installable apps > Is there a deeper reason for this? If I look at âother systemsâ, they manage to have *one* download, *one* way of installing. For me, offering *a lot* of possible different ways means that the user has to choose without knowing why there is even the option to chooseâ¦ Marcus

March 14, 2018

Re: [Pharo-dev] Idea to manager package comment in better way

by Marcus Denker

> On 14 Mar 2018, at 16:40, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi. > > I look at hierarchy of PackageManifest and I was wondering that all these classes are commented but most of packages which they describe are not. > > Also interesting that most of manifest comments are same. > > Then I found that package comment is managed as special class side method #description which is generated when you call "aPackage packageComment: 'test'". > > Now the idea: will not it be better to manage package comment as manifest class comment? > > Manifest is already responsible to describe the package. So it looks logical to have "manifest comment = package comment". > Also it will simplify code and remove duplication of texts. > In addition it will add extra place indicating that package needs to be commented because uncommented classes are marked in the browser. > > What you think? > I would say yesâ¦ this would save actually space: lots of methods removed, and the string would be stored on disk instead of inside the image. Marcus

March 14, 2018

Re: [Pharo-dev] Idea to manager package comment in better way

by Denis Kudriashov

And I found that manifest classes are already commented as package comment. 2018-03-14 16:40 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > Hi. > > I look at hierarchy of PackageManifest and I was wondering that all these > classes are commented but most of packages which they describe are not. > > Also interesting that most of manifest comments are same. > > Then I found that package comment is managed as special class side method > #description which is generated when you call "aPackage packageComment: > 'test'". > > Now the idea: will not it be better to manage package comment as manifest > class comment? > > Manifest is already responsible to describe the package. So it looks > logical to have "manifest comment = package comment". > Also it will simplify code and remove duplication of texts. > In addition it will add extra place indicating that package needs to be > commented because uncommented classes are marked in the browser. > > What you think? > >

March 14, 2018

Idea to manager package comment in better way

by Denis Kudriashov

Hi. I look at hierarchy of PackageManifest and I was wondering that all these classes are commented but most of packages which they describe are not. Also interesting that most of manifest comments are same. Then I found that package comment is managed as special class side method #description which is generated when you call "aPackage packageComment: 'test'". Now the idea: will not it be better to manage package comment as manifest class comment? Manifest is already responsible to describe the package. So it looks logical to have "manifest comment = package comment". Also it will simplify code and remove duplication of texts. In addition it will add extra place indicating that package needs to be commented because uncommented classes are marked in the browser. What you think?

March 14, 2018

Re: [Pharo-dev] Getting IP address of machine from Pharo

by Henrik Sperre Johansen

We don't really, hence things like http://forum.world.st/Pharo-user-Does-SSDP-package-supposed-to-work-on-Phar… ;) Cheers, Henry -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

March 14, 2018