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

Re: [Pharo-dev] periodic auto actions on bug tracker

by Tim Mackinnon

Itâs a great idea - I too have a good look at what I previously reported and decide if itâs still relevant and whether it makes sense to still pursue it. Sent from my iPhone > On 9 Dec 2018, at 06:20, Ben Coman <btc(a)openinworld.com> wrote: > > I support the auto-closing of old tickets to avoid bug bankruptcy. Sometimes things seem more important at the time and when my own tickets come back around I get to be more analytical about the effort/reward balance. > > It would be useful to expand this a bit to have a quarterly mail out saying something like "Is this issue still important to you? Try socializing it on the pharo-dev mail list. Issues going twelve months without interaction will be auto-closed". Then its not a bad surprise to new users when their ticket is auto-closed. > > cheers -ben > >

Dec. 9, 2018

Calypso equivalent <nautilusGlobalPackageMenu>

by Ben Coman

What is the Calypso equivalent of <nautilusGlobalPackageMenu> ? I need to add an extra menu item to the Packages context menu. cheers -ben

Dec. 9, 2018

Fixed by reboot

by Ben Coman

Just reporting a strange occurrence in case anyone sees the same. I was using PharoLauncher fine, then it wasn't. When trying to launch an image it started reporting with "ProcessWrapper newProcess failed..." First time I've ever seen that, and fixed by a reboot, but still strange. There are a couple of other troubles that get fixed by reboot. Anyone have insight into an underlying cause? cheers -ben

Dec. 9, 2018

periodic auto actions on bug tracker

by Ben Coman

I support the auto-closing of old tickets to avoid bug bankruptcy. Sometimes things seem more important at the time and when my own tickets come back around I get to be more analytical about the effort/reward balance. It would be useful to expand this a bit to have a quarterly mail out saying something like "Is this issue still important to you? Try socializing it on the pharo-dev mail list. Issues going twelve months without interaction will be auto-closed". Then its not a bad surprise to new users when their ticket is auto-closed. cheers -ben

Dec. 9, 2018

Re: [Pharo-dev] Release candidate version numbers

by Ben Coman

> > Le sam. 8 dÃ©c. 2018 Ã 13:42, Ben Coman <btc(a)openinworld.com> a Ã©crit : > >> In PharoLauncher >> >> under "Pharo 7 (development version)" opening template >> Pharo7.0.0-rc1.build.1433.sha.8292c1f.arch.32bit >> then System > System Report shows... >> >> Pharo-7.0.0+rc1.build.1433.sha.8292c1f795527f5969a227d22bc32f1c4e93b710 (32 >> Bit) >> >> >> but under "Official distributions" I see >> Pharo 7.0 - 32bit (development version) >> then System > System Report shows... >> >> Pharo-7.0.0+rc1.build.24.sha.41c89eb7dd9f362ca1ba874f1d9a42602396e002 (32 >> Bit) >> >> Why using such a different and small number "24", >> and a long way from 1433 ? >> > > On Sun, 9 Dec 2018 at 02:00, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > i think it may come from the fact that this is a new branch (development got renamed into pharo7.0) Makes sense. Good to know. I understand there may be constraints on that being fixable, and that someone may be in the middle of working on this before any cleanup, but just an other oddity I observed... [image: build-dates.png] cheers -ben

Dec. 9, 2018

Re: [Pharo-dev] Playground "remote publish" feedback from discord

by Ben Coman

On Sun, 9 Dec 2018 at 00:56, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Ben, > > > On 8 Dec 2018, at 17:19, Ben Coman <btc(a)openinworld.com> wrote: > > > > On discord a user provided some feedback... > > > > when you post anything to ws.stfx.eu - e.g. here: > http://ws.stfx.eu/CJGVYTTQD3RY - the page says that I should use > "ZnWorkspace openUrl: 'http://ws.stfx.eu/CJGVYTTQD3RY'." to retrieve it. > However, there is no class called "ZnWorkspace" in Pharo 6.1 so this should > probably be updated. > > > > "Remote publish" button is located fairly prominently in the top right > corner of Pharo Playground window so Pharo beginners will probably see it > fairly soon after they start experimenting and try clicking on it. The text > should be updated so the instructions actually work. > > > > Also the footer of the page says copyright is 2013, and it would look > better to newcomers if the copyright date was more recent. > > > > ---------- > > cheers -ben > > The 'Shared Smalltalk Workspaces' [http://ws.stfx.eu] service is indeed > old (but has been working unattended for years). Quite impressive that. > It was later hijacked (in a good way) by the Playground. It should indeed > be upgraded a bit, I'll look into it but can't promise anything. > Since its been incorporated as a standard feature, is it time for it to move domain to ws.pharo.org. Maybe the Association/Consortium fund your time to assist with that? Do note that you can paste a SSW URL like http://ws.stfx.eu/CJGVYTTQD3RY > into Spotter to open it in a new Playground. A cool, but hidden feature. So > technically there is no need for more. > Nice, that worked well. cheers -ben > > You can also access a page with the following expression: > > ZnClient new > systemPolicy; > beOneShot; > accept: ZnMimeType textPlain; > url: 'http://ws.stfx.eu/CJGVYTTQD3RY'; > get. > > Maybe an additional menu item somewhere ? > > Sven > > >

Dec. 9, 2018

Re: [Pharo-dev] Release candidate version numbers

by Guillermo Polito

Hi, i think it may come from the fact that this is a new branch (development got renamed into pharo7.0) guille Le sam. 8 dÃ©c. 2018 Ã 13:42, Ben Coman <btc(a)openinworld.com> a Ã©crit : > In PharoLauncher > > under "Pharo 7 (development version)" opening template > Pharo7.0.0-rc1.build.1433.sha.8292c1f.arch.32bit > then System > System Report shows... > > Pharo-7.0.0+rc1.build.1433.sha.8292c1f795527f5969a227d22bc32f1c4e93b710 (32 > Bit) > > > but under "Official distributions" I see > Pharo 7.0 - 32bit (development version) > then System > System Report shows... > > Pharo-7.0.0+rc1.build.24.sha.41c89eb7dd9f362ca1ba874f1d9a42602396e002 (32 > Bit) > > Why using such a different and small number "24", > and a long way from 1433 ? > > cheers -ben > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Dec. 8, 2018

Re: [Pharo-dev] Playground "remote publish" feedback from discord

by Sven Van Caekenberghe

Ben, > On 8 Dec 2018, at 17:19, Ben Coman <btc(a)openinworld.com> wrote: > > On discord a user provided some feedback... > > when you post anything to ws.stfx.eu - e.g. here: http://ws.stfx.eu/CJGVYTTQD3RY - the page says that I should use "ZnWorkspace openUrl: 'http://ws.stfx.eu/CJGVYTTQD3RY'." to retrieve it. However, there is no class called "ZnWorkspace" in Pharo 6.1 so this should probably be updated. > > "Remote publish" button is located fairly prominently in the top right corner of Pharo Playground window so Pharo beginners will probably see it fairly soon after they start experimenting and try clicking on it. The text should be updated so the instructions actually work. > > Also the footer of the page says copyright is 2013, and it would look better to newcomers if the copyright date was more recent. > > ---------- > cheers -ben The 'Shared Smalltalk Workspaces' [http://ws.stfx.eu] service is indeed old (but has been working unattended for years). It was later hijacked (in a good way) by the Playground. It should indeed be upgraded a bit, I'll look into it but can't promise anything. Do note that you can paste a SSW URL like http://ws.stfx.eu/CJGVYTTQD3RY into Spotter to open it in a new Playground. A cool, but hidden feature. So technically there is no need for more. You can also access a page with the following expression: ZnClient new systemPolicy; beOneShot; accept: ZnMimeType textPlain; url: 'http://ws.stfx.eu/CJGVYTTQD3RY'; get. Maybe an additional menu item somewhere ? Sven

Dec. 8, 2018

Release candidate version numbers

by Ben Coman

In PharoLauncher under "Pharo 7 (development version)" opening template Pharo7.0.0-rc1.build.1433.sha.8292c1f.arch.32bit then System > System Report shows... Pharo-7.0.0+rc1.build.1433.sha.8292c1f795527f5969a227d22bc32f1c4e93b710 (32 Bit) but under "Official distributions" I see Pharo 7.0 - 32bit (development version) then System > System Report shows... Pharo-7.0.0+rc1.build.24.sha.41c89eb7dd9f362ca1ba874f1d9a42602396e002 (32 Bit) Why using such a different and small number "24", and a long way from 1433 ? cheers -ben

Dec. 8, 2018

Playground "remote publish" feedback from discord

by Ben Coman

On discord a user provided some feedback... when you post anything to ws.stfx.eu - e.g. here: http://ws.stfx.eu/CJGVYTTQD3RY - the page says that I should use "ZnWorkspace openUrl: 'http://ws.stfx.eu/CJGVYTTQD3RY'." to retrieve it. However, there is no class called "ZnWorkspace" in Pharo 6.1 so this should probably be updated. "Remote publish" button is located fairly prominently in the top right corner of Pharo Playground window so Pharo beginners will probably see it fairly soon after they start experimenting and try clicking on it. The text should be updated so the instructions actually work. Also the footer of the page says copyright is 2013, and it would look better to newcomers if the copyright date was more recent. ---------- cheers -ben

Dec. 8, 2018