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

Re: [Pharo-dev] LibC system pops up a CMD.exe window in Windows 10 (Pharo 6.1)

by Christopher Fuhrman

Thanks Peter. That looks like a cool package. I guess I will live with it for now, because I don't want to code too much of a platform-specific solution (yet). On Mon, 10 Dec 2018 at 21:16, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > This is normal (and much lamented) behavior of cmd. There's > https://github.com/astares/Pharo-OS-Windows which implements parts of the > WinAPI... with which one can create headless windows. (I think it should be > also available in the catalog). > > Peter > > On Mon, Dec 10, 2018 at 11:47 AM Christopher Fuhrman < > christopher.fuhrman(a)inria.fr> wrote: > >> Hello, >> >> My Git data mining API in Pharo 6.1 uses "LibC uniqueInstance system: >> 'some commands'" which has an annoying side effect of popping up a window >> (which steals the GUI focus in Windows 10). Maybe it's the same on MacOS >> and Linux? >> >> As such, I can't use my Windows PC to do anything else when the mining >> process is running (it can take several minutes). I'm not able to use >> Pharo's OSProcess or OSSubprocess because they don't support Windows (yet?). >> >> I tried creating a separate Windows Desktop (feature of Windows 10), but >> the CMD.EXE window manages to pop up there, too - almost seems like a >> windows bug. >> >> Does anyone know of a way to have the LibC window not pop up? >> >> Cheers, >> >> Christopher >> >

Dec. 11, 2018

Re: [Pharo-dev] Tonel>>sourceDir

by Alistair Grant

Hi Ben, On Sun, 9 Dec 2018 at 16:06, Ben Coman <btc(a)openinworld.com> wrote: > > > For Exercism we are using Tonel in Pharo 6.1. > We are getting an error "Instance of TonelWriter did not understand #sourceDir:" > but the same code works fine on Pharo 7. > > The 6.1 image had been updated to latest Iceberg per https://github.com/pharo-vcs/iceberg#for-pharo-61, so I used ICeberg to updated to latest "master" of pharo-vcs/tonel but no avail. > > In Pharo 7 I see TonelWriter>>sourceDir in protocol "accessing" > but if I search for "sourceDir" in the pharo-vcs/tonel repo it doesn't find it... > https://github.com/pharo-vcs/tonel/search?q=sourcedir&unscoped_q=sourcedir > > I'm having trouble understanding where the #sourceDir method comes from in Pharo 7. > Which repo/branch can I load that from into another system? It seems like v1.0.9 has it and master doesn't, see: https://github.com/pharo-vcs/tonel/tree/v1.0.9/MonticelloTonel-Core.package… (based on just hunting around my Pharo 7 image, I don't really understand the code :-)) HTH, Alistair

Dec. 11, 2018

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

by Sven Van Caekenberghe

https://github.com/pharo-project/pharo/pull/2057 https://pharo.fogbugz.com/f/cases/22750/Add-GTPlayground-class-openUrl Note that this is actually more universal than the specific website/webservice we are currently using. It works for any web resource that is returning text/plain documents. For example, try GTPlayground openUrl: 'http://zn.stfx.eu/zn/numbers.txt'. (Apart from the fact that that server is currently down ;-) > On 9 Dec 2018, at 13:13, Ben Coman <btc(a)openinworld.com> wrote: > > > > On Sun, 9 Dec 2018 at 18:31, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > On 8 Dec 2018, at 17:55, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > Maybe an additional menu item somewhere ? > > Or a little bit more API. > > Right now with the standard GT infrastructure in Pharo 7 (and Pharo 6.1 also I guess), you can do > > GTPlayground openOn: (GTPlayPage loadFromPublishUrl: 'http://ws.stfx.eu/1WS4U'). > > We could add one of the following > > GTPlayground loadFromPublishUrl: 'http://ws.stfx.eu/1WS4U'. "keeps the same selector" > GTPlayground openPublishUrl: 'http://ws.stfx.eu/1WS4U'. "shorter, more in line with the opening action" > GTPlayground openUrl: 'http://ws.stfx.eu/1WS4U'. "the original on ZnWorkspace, shortest" > > The last is easiest to remember - composed of just two words rather than three or four.. > > > If we agree, I can change the default instructions on the web page as seen in a browser. > > There is little point in wanting to keep the ZnWorkspace code, as it is no longer needed. > > okay. > > cheers -ben

Dec. 10, 2018

stfx.eu down

by Sven Van Caekenberghe

Hi, This evening I somehow broke my stfx.eu server while doing an ubuntu dist upgrade (an old AWS EC2 machine). This means several websites / web services hosted by that machine are down, most notably mc.stfx.eu (hosting several of my packages) and ws.stfx.eu (used for shared smalltalk workspaces). A couple of Zinc tests will also fail. For source code access, all my public repos exist both in an up to date form on GitHub (http://github.com/svenvc) as well in the original form in SmalltalkHub (http://smalltalkhub.com/#!/~SvenVanCaekenberghe) or SS3. The main problem there is that the distributed ConfigurationsOf and Catalog entries will still point to the original. This is not a problem with git's BaselineOf definitions. Although the machine will no longer boot, I managed to mount the original volume on another instance so I can still access the whole filesystem. This will make it possible to eventually recover most services. But this will take time as these things never happen when it is convenient. It will give me an opportunity to modernise the setup though, which is good. Sorry for the inconvenience. Sven

Dec. 10, 2018

Re: [Pharo-dev] LibC system pops up a CMD.exe window in Windows 10 (Pharo 6.1)

by Peter Uhnak

This is normal (and much lamented) behavior of cmd. There's https://github.com/astares/Pharo-OS-Windows which implements parts of the WinAPI... with which one can create headless windows. (I think it should be also available in the catalog). Peter On Mon, Dec 10, 2018 at 11:47 AM Christopher Fuhrman < christopher.fuhrman(a)inria.fr> wrote: > Hello, > > My Git data mining API in Pharo 6.1 uses "LibC uniqueInstance system: > 'some commands'" which has an annoying side effect of popping up a window > (which steals the GUI focus in Windows 10). Maybe it's the same on MacOS > and Linux? > > As such, I can't use my Windows PC to do anything else when the mining > process is running (it can take several minutes). I'm not able to use > Pharo's OSProcess or OSSubprocess because they don't support Windows (yet?). > > I tried creating a separate Windows Desktop (feature of Windows 10), but > the CMD.EXE window manages to pop up there, too - almost seems like a > windows bug. > > Does anyone know of a way to have the LibC window not pop up? > > Cheers, > > Christopher >

Dec. 10, 2018

Re: [Pharo-dev] Multiline method definition in Tonel

by Mariano Martinez Peck

On Sun, Dec 9, 2018 at 6:28 PM Peter Uhnak <i.uhnak(a)gmail.com> wrote: > That's just whitespace... or more specifically any of these are fine > (TonelParser>>extractSelector:) > > ``` > separators := { > Character space. > Character tab. > Character lf. > Character newPage. > Character cr. > $: "not me though"}. > ``` > > You can also try to parse it directly and see the result: > > ``` > def := 'Class { > #name : #Whatever, > #superclass : #Object, > #category : ''Wherever'' > } > > { #category : #protocol } > Whatever >> testWith: arg1 > with: arg2 > with: arg3 [ > ^ 42 > ] > '. > TonelParser parseStream: def readStream. > ``` > > Thanks Peter! I was afraid that TonelParser would break if tried to parse multiline method declarations. > Note that exporting it will result in a "normalized" format, so if you > keep it in git you will see a change (this also applies to the ordering of > methods and some optional stuff) > OK. Thanks for letting me know. And for "normalized" you mean a classical oneliner right? Thanks! > > Peter > > On Fri, Dec 7, 2018 at 5:57 PM Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> Hi guys, >> >> I was reading the Tonel spec here [1] but it is not clear to me the case >> of the multiline method definitions. Are those allowed or not? Say I have >> a method like this: >> >> testWith: arg1 >> with: arg2 >> with: arg3 >> >> ^ 42 >> >> Is that valid as Tonel format? Or tonel expects to have method definition >> in a one liner like: >> >> testWith: arg1 with: arg2 with: arg3 >> >> ^ 42 >> >> >> Thanks in advance, >> >> >> [1] https://github.com/pharo-vcs/tonel >> >> -- >> Mariano >> https://twitter.com/MartinezPeck >> http://marianopeck.wordpress.com >> > -- Mariano https://twitter.com/MartinezPeck http://marianopeck.wordpress.com

Dec. 10, 2018

[Pharo 7.0] Build #25: 22735-ZipArchive-classisZipArchive-is-broken-in-P7

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

There is a new Pharo build available! The status of the build #25 was: SUCCESS. The Pull Request #2046 was integrated: "22735-ZipArchive-classisZipArchive-is-broken-in-P7" Pull request url: https://github.com/pharo-project/pharo/pull/2046 Issue Url: https://pharo.fogbugz.com/f/cases/22735 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 10, 2018

Re: halos

by John Kimber

shift-control click works for me on 1384. HTH, john -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 10, 2018

Re: [Pharo-dev] Fwd: Tonel sourceDir

by Torsten Bergmann

Hi Ben, in Pharo 7 Iceberg works different - the source dir is part of the metadata in the repo (right click on a repo and say "Repair" so it offers you to add metadata). So for instance https://github.com/astares/Pharo-OS-Windows is already converted to the "latest and greates" and has a .project file with { 'srcDirectory' : 'src' } So you just can load it without giving the source dir explicitly. Also note that the src file directory has .properties file depicting the format: { #format : #tonel } Tonel is now recommended. Hope that helps a little bit. Thanks T.

Dec. 10, 2018

Re: [Pharo-dev] Fwd: Tonel sourceDir

by Guillermo Polito

Hi Ben, I'm going to check emails on wednesday. I'm about to be on planes for 16~20 hours :) Le lun. 10 dÃ©c. 2018 Ã 08:29, Ben Coman <btc(a)openinworld.com> a Ã©crit : > > Okay, that was 13 hours ago. Once again... > (CCing Esteban & Guille. Can you guys let me know if its at least getting > out) > > ---------- Forwarded message --------- > From: Ben Coman <btc(a)openinworld.com> > Date: Mon, 10 Dec 2018 at 06:18 > Subject: Tonel sourceDir > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > This did make it through the mail list in 8 hours, so mabe the double > arrow in the subject line confused things. > > Trying again... > > ---------- Forwarded message --------- > From: Ben Coman <btc(a)openinworld.com> > Date: Sun, 9 Dec 2018 at 23:05 > Subject: Tonel>>sourceDir > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > > For Exercism we are using Tonel in Pharo 6.1. > We are getting an error "Instance of TonelWriter did not understand > #sourceDir:" > but the same code works fine on Pharo 7. > > The 6.1 image had been updated to latest Iceberg per > https://github.com/pharo-vcs/iceberg#for-pharo-61, so I used ICeberg to > updated to latest "master" of pharo-vcs/tonel but no avail. > > In Pharo 7 I see TonelWriter>>sourceDir in protocol "accessing" > but if I search for "sourceDir" in the pharo-vcs/tonel repo it doesn't > find it... > https://github.com/pharo-vcs/tonel/search?q=sourcedir&unscoped_q=sourcedir > > I'm having trouble understanding where the #sourceDir method comes from in > Pharo 7. > Which repo/branch can I load that from into another system? > > 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. 10, 2018