February 2019 - Pharo-users

Re: [Pharo-users] About Iceberg

by Tim Mackinnon

Yes I agree - when there is so much discussion and debate going on, its easy to lose sight of the hard work and determination that went into getting us to this brave new world. I too want to shout a big thank you for the tooling and also the support that goes along with that. I love been able to think a bit more polyglot, and use tools/languages more easily side by side - although of course I want to hold on to what makes Smalltalk special (which is tons of stuff). I particularly love being able to feel like its easier to contribute - updating readmeâs and docs is trivial in a web browser now - just correct them and submit a PR. And on the receiving side - GitHub makes it easy to discuss the fix, alter it, or simply approve it. Equally - modern build tools easily detect the change, pull the code and rebuild and package it (and cheap scalable infrastructure). Its also getting easier and easier to submit code fixes too - and the VCS skills you learn doing this are transferable beyond Smalltalk - so its a big win win. So yes guys - thanks for hanging in for us! Tim > On 19 Feb 2019, at 08:50, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > This is a thank you note about Iceberg. > > I have been moving all my external and internal Pharo code to git/tonel/7 and on multiple occasions I have been pleasantly surprised about the functionality and performance of Iceberg. Basically, it just works. > > Finally, Pharo code lives in standard open source and commercial repositories (git, GitHub, Bitbucket, ...), without losing anything. > > I know that it took years to get here and that lots of code and community battles had to be fought. So thank you, to the whole team, you did a great job ! > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > >

Feb. 19, 2019

Re: [Pharo-users] Pier3 & content management

by Albrecht Baur

thanks for the info - I will give it a try next weeks. On 19.02.19 12:41, Esteban Lorenzano wrote: > Hello, > > Not many people are using it, but it should be not much problem make > it run in Pharo 7 (and with current version of Seaside). > > Esteban > >> On 19 Feb 2019, at 12:03, Albrecht Baur via Pharo-users >> <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>> wrote: >> >> >> *From: *Albrecht Baur <baur.albrecht(a)googlemail.com >> <mailto:baur.albrecht@googlemail.com>> >> *Subject: **Pier3 & content management* >> *Date: *19 February 2019 at 12:03:27 CET >> *To: *Any question about pharo is welcome >> <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>> >> >> >> Hey, >> >> what is the status of Pier3 + Pier3AddOns ? >> >> -> Seems to me that it is discontinued since Pharo 5, right ? >> >> I'm asking because I look around to see if there is a project usable >> as a starting point of a small web content management module for >> seaside (nothing too complicated / fancy). >> >> Is there something besides Pier that goes into this direction ? >> >> Thanks for hints, >> Albrecht >> >> >

Feb. 19, 2019

Re: [Pharo-users] How do you avoid loading master code which is indirectly referenced by a version in the baseline?

by phil＠highoctane.be

Same boat here. Phil On Tue, Feb 19, 2019, 13:05 Tim Mackinnon <tim(a)testit.works wrote: > Hi Sabine - you raise an important point, and I am interested in us > getting better answers to this too. Hopefully Dale seeâs this and is > thinking about this in Rowen. Repeatable loading is an important enterprise > feature. > > Tim > > > On 18 Feb 2019, at 15:46, Sabine Manaa <manaa.sabine(a)gmail.com> wrote: > > > > For test and deployment, I have to be sure that I know exactly which > versions > > I load and I have to be sure to be able to load exactly the same code > again. > > I do not speak from my projects but from the projects I use. > > > > I found myself asking people again and again to set tags in their > projects > > and being surprised again and again by changed code even though I am > trying > > to load versions (with versions I mean NOT #stable or #master but like > > v2.2.2). > > > > The reason for this problem I then have, is that often in baselines with > > version numbers (e.g. v2.2.2) other projects are referenced but as > master. > > So in consequence, I load version but get master from another project > which > > is referenced indirectly. > > > > For me, that this is not good at all. I was wondering that this seems > not to > > be a problem for others. > > > > I found out that I can put a lock in my baselines preLoadDoIt for those > > indirectly referenced projects. > > > > Examlpe Artefact v1.0.1 > > > > > https://github.com/pharo-contributions/Artefact/blob/v1.0.1/src/BaselineOfA… > > > > loads github://zweidenker/Units/src (which is master). > > > > I found a solution for this: > > > > In the preLoadDoIt of my baseline I lock Units to a certain commit. > > > > preLoadDoIt > > Metacello new > > baseline: 'Units'; > > repository: 'github://zweidenker/Units:98d5a3d/src'; > > lock. > > > > This solves my problem in this example. > > > > Disadvantage is that I have to analyze everything which is loaded from > the > > projects I use and create a lock for it. > > > > Questions: > > 1.) Wouldn't it make sense to have some mechanism, perhaps in Rowan then, > > where I can say that a project which has a number can only reference > other > > projects with numbers? This would avoid the whole problem > > 2.) How do others solve this problem? > > > > addendum: I do not speak about project versions which are in development, > > here #stable or master are great features. But sometime when a project > has a > > certain state, and it gets a version, then it should not change..imho > > > > > > > > -- > > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > > > > >

Feb. 19, 2019

Re: [Pharo-users] How do you avoid loading master code which is indirectly referenced by a version in the baseline?

by Tim Mackinnon

Hi Sabine - you raise an important point, and I am interested in us getting better answers to this too. Hopefully Dale seeâs this and is thinking about this in Rowen. Repeatable loading is an important enterprise feature. Tim > On 18 Feb 2019, at 15:46, Sabine Manaa <manaa.sabine(a)gmail.com> wrote: > > For test and deployment, I have to be sure that I know exactly which versions > I load and I have to be sure to be able to load exactly the same code again. > I do not speak from my projects but from the projects I use. > > I found myself asking people again and again to set tags in their projects > and being surprised again and again by changed code even though I am trying > to load versions (with versions I mean NOT #stable or #master but like > v2.2.2). > > The reason for this problem I then have, is that often in baselines with > version numbers (e.g. v2.2.2) other projects are referenced but as master. > So in consequence, I load version but get master from another project which > is referenced indirectly. > > For me, that this is not good at all. I was wondering that this seems not to > be a problem for others. > > I found out that I can put a lock in my baselines preLoadDoIt for those > indirectly referenced projects. > > Examlpe Artefact v1.0.1 > > https://github.com/pharo-contributions/Artefact/blob/v1.0.1/src/BaselineOfA… > > loads github://zweidenker/Units/src (which is master). > > I found a solution for this: > > In the preLoadDoIt of my baseline I lock Units to a certain commit. > > preLoadDoIt > Metacello new > baseline: 'Units'; > repository: 'github://zweidenker/Units:98d5a3d/src'; > lock. > > This solves my problem in this example. > > Disadvantage is that I have to analyze everything which is loaded from the > projects I use and create a lock for it. > > Questions: > 1.) Wouldn't it make sense to have some mechanism, perhaps in Rowan then, > where I can say that a project which has a number can only reference other > projects with numbers? This would avoid the whole problem > 2.) How do others solve this problem? > > addendum: I do not speak about project versions which are in development, > here #stable or master are great features. But sometime when a project has a > certain state, and it gets a version, then it should not change..imho > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Feb. 19, 2019

Re: [Pharo-users] OSProcess / OSSubprocess / LibC uniqueInstance

by Serge Stinckwich

Thank you Thierry. On Tue, Feb 19, 2019 at 12:48 PM Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Hi Serge, Albrecht, > > loading OSProcess directly with the following expression works: > > Metacello new > configuration: 'OSProcess'; > repository: 'http://www.squeaksource.com/MetacelloRepository'; > load > > There is still some work to be done on OSProcess adaptation to Pharo > 7, but they are in rarely used parts. > > Regards, > > Thierry > > Le mar. 19 fÃ©vr. 2019 Ã 12:19, Albrecht Baur via Pharo-users > <pharo-users(a)lists.pharo.org> a Ã©crit : > > > > I need to execute OS commands from within a x64 pharo 7.01 image on > centos7 (for example: 'zip -r 123.zip zipme/'). > > > > I found these 3 tools: OSProcess, OSSubprocess, LibC uniqueInstance > > > > But I did not find any docu on which one to use for which use case. > > > > OSProcess is in the catalog browser but fails loading because of > ByteArray>>ifNotNilDo: > > -> So OSProcess is not to be used with p7 ? > > > > OSSubprocess loads via catalog browser and the following snippet works > (even though 64 bit): > > > > OSSUnixSubprocess new > > command: 'zip'; > > arguments: #('-r' '123.zip' 'zipme'); > > redirectStdout; > > runAndWaitOnExitDo: [ :process :outString | > > outString inspect > > ] > > > > So is it ok to use OSSubprocess with 64 bit even though documented as 32 > bit only ? (here: > https://github.com/pharo-contributions/OSSubprocess#installation) > > > > LibC uniqueInstance system: 'zip -r 123.zip zipme/' > > ... works, but I don't know if its the right tool for this. > > > > Is there somewhere more info on which tool to use for which use case ? > > > > Thanks in advance! > > > > Albrecht > > > > PS.: I need to use zip as os process only because of this issue: > https://github.com/pharo-project/pharo/issues/2584 > > -- Serge Stinckwic âhâ Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) âSorbonne University (SU) French National Research Institute for Sustainable Development (IRD)â U âniversity of YaoundÃ© Iâ, Cameroun "Programs must be written for people to read, and only incidentally for machines to execute." https://twitter.com/SergeStinckwich â

Feb. 19, 2019

Re: [Pharo-users] How to load a single package in a Metacello baseline

by Tim Mackinnon

Yeah - I have a similar issue with ExternalWebBrowser, which I load as: spec baseline: 'ExternalWebBrowser' with: [ spec repository: 'github://seandenigris/Pharo-Web-Browser:master/repository' ]; import: 'ExternalWebBrowser'. That drags in BabyMock and huge raft of tests (which Iâm grateful were written), but Iâd prefer not to muddy the waters when presenting Exercism. I think what we have to do is submit pull requests to these projects such that they create better baselines with Groups. Eg. The Exercism baseline does this so that students load core, but developers get extra tools to generate exercises - eg. spec package: 'Exercism' with: [ ]; package: 'ExercismDev' with: [ spec requires: #('Exercism' 'ExercismTools')]; package: 'ExercismTools' with: [ spec requires: #('OSProcess' 'ExternalWebBrowser') ]; group: 'default' with: #('ExercismTools'); group: 'dev' with: #('ExercismDevâ)] Then you can specify in your load request which group to use (I donât have the syntax handy for baselines, but when you load via iceberg, the Metacelle menu has a second option where you specify the group to use, so Iâm sure it can be done in code too). Iâd be interested if there is some way to do it without groups though, so that you donât have to rely on the package authors to do this (similar in thought to what Sabine is complaining about by not being able to better control version dependencies). This whole area is becoming more and more important as we grow up and what to have more controllable load characteristics. Tim > On 19 Feb 2019, at 11:13, N. Bouraqadi <bouraqadi(a)gmail.com> wrote: > > Hi, > > I'm updating the the baseline of PharoJS to use the zinc websockets from the github repo https://github.com/svenvc/zinc <https://github.com/svenvc/zinc>. I want to load package Zinc-WebSocket-Core. So, in BaselineOfPharoJS>>#baseline: I've defined > spec baseline: 'ZincHTTPComponents' with: [ > spec > loads: #('Zinc-WebSocket-Core'); > repository: 'github://svenvc/zinc <github://svenvc/zinc>' ]. > > However, for some reason I get Zinc-WebSocket-Tests loaded. Any hint how to avoid it?(edited) > Looking at BaselineOfZincHTTPComponents>>#baseline:, package WebSocket-Core does not seem to depend on tests > spec package: 'Zinc-WebSocket-Core' with: [ spec requires: 'Zinc-HTTP' ] > > Thanks, > Noury

Feb. 19, 2019

Re: [Pharo-users] OSProcess / OSSubprocess / LibC uniqueInstance

by Thierry Goubier

Hi Serge, Albrecht, loading OSProcess directly with the following expression works: Metacello new configuration: 'OSProcess'; repository: 'http://www.squeaksource.com/MetacelloRepository'; load There is still some work to be done on OSProcess adaptation to Pharo 7, but they are in rarely used parts. Regards, Thierry Le mar. 19 fÃ©vr. 2019 Ã 12:19, Albrecht Baur via Pharo-users <pharo-users(a)lists.pharo.org> a Ã©crit : > > I need to execute OS commands from within a x64 pharo 7.01 image on centos7 (for example: 'zip -r 123.zip zipme/'). > > I found these 3 tools: OSProcess, OSSubprocess, LibC uniqueInstance > > But I did not find any docu on which one to use for which use case. > > OSProcess is in the catalog browser but fails loading because of ByteArray>>ifNotNilDo: > -> So OSProcess is not to be used with p7 ? > > OSSubprocess loads via catalog browser and the following snippet works (even though 64 bit): > > OSSUnixSubprocess new > command: 'zip'; > arguments: #('-r' '123.zip' 'zipme'); > redirectStdout; > runAndWaitOnExitDo: [ :process :outString | > outString inspect > ] > > So is it ok to use OSSubprocess with 64 bit even though documented as 32 bit only ? (here: https://github.com/pharo-contributions/OSSubprocess#installation) > > LibC uniqueInstance system: 'zip -r 123.zip zipme/' > ... works, but I don't know if its the right tool for this. > > Is there somewhere more info on which tool to use for which use case ? > > Thanks in advance! > > Albrecht > > PS.: I need to use zip as os process only because of this issue: https://github.com/pharo-project/pharo/issues/2584

Feb. 19, 2019

Re: [Pharo-users] Pier3 & content management

by Esteban Lorenzano

Hello, Not many people are using it, but it should be not much problem make it run in Pharo 7 (and with current version of Seaside). Esteban > On 19 Feb 2019, at 12:03, Albrecht Baur via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Albrecht Baur <baur.albrecht(a)googlemail.com> > Subject: Pier3 & content management > Date: 19 February 2019 at 12:03:27 CET > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > > Hey, > > what is the status of Pier3 + Pier3AddOns ? > > -> Seems to me that it is discontinued since Pharo 5, right ? > > I'm asking because I look around to see if there is a project usable as a starting point of a small web content management module for seaside (nothing too complicated / fancy). > > Is there something besides Pier that goes into this direction ? > > Thanks for hints, > Albrecht > >

Feb. 19, 2019

How to load a single package in a Metacello baseline

by N. Bouraqadi

Hi, I'm updating the the baseline of PharoJS to use the zinc websockets from the github repo https://github.com/svenvc/zinc. I want to load package Zinc-WebSocket-Core. So, in BaselineOfPharoJS>>#baseline: I've defined spec baseline: 'ZincHTTPComponents' with: [ spec loads: #('Zinc-WebSocket-Core'); repository: 'github://svenvc/zinc' ]. However, for some reason I get Zinc-WebSocket-Tests loaded. Any hint how to avoid it?(edited) Looking at BaselineOfZincHTTPComponents>>#baseline:, package WebSocket-Core does not seem to depend on tests spec package: 'Zinc-WebSocket-Core' with: [ spec requires: 'Zinc-HTTP' ] Thanks, Noury

Feb. 19, 2019

Re: [Pharo-users] OSProcess / OSSubprocess / LibC uniqueInstance

by Albrecht Baur

I just tried the easy way via catalog browser. I think it is OSProcess 4.6.9 from http://www.squeaksource.com/OSProcess On 19.02.19 12:01, Serge Stinckwich wrote: > > > On Tue, Feb 19, 2019 at 11:56 AM David T. Lewis <lewis(a)mail.msen.com > <mailto:lewis@mail.msen.com>> wrote: > > On Tue, Feb 19, 2019 at 11:37:38AM +0100, Albrecht Baur via > Pharo-users wrote: > > From: Albrecht Baur <baur.albrecht(a)googlemail.com > <mailto:baur.albrecht@googlemail.com>> > > Subject: OSProcess / OSSubprocess / LibC uniqueInstance > > To: pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org> > > Date: Tue, 19 Feb 2019 11:37:38 +0100 > > > > I need to execute OS commands from within a x64 pharo 7.01 image on > > centos7 (for example: 'zip -r 123.zip zipme/'). > > > > I found these 3 tools: OSProcess, OSSubprocess, LibC uniqueInstance > > > > But I did not find any docu on which one to use for which use case. > > > >Â * OSProcess is in the catalog browser but fails loading because of > >Â Â ByteArray>>ifNotNilDo: > >Â Â -> So OSProcess is not to be used with p7 ? > > Hi Albrecht, > > I am sorry that I cannot check it right now, but it may be that > ConfigurationOfOSProcess needs to be updated. The #ifNotNilDo: problem > was fixed by Thierry Goubier in July 2017, so perhaps you are using > an out of date version. > > Hopefully someone else can give you a better answer, otherwise I will > try to follow up in a day or two. > > > I have the same problem of ifNotNilDo: when I load OSProcess in Pharo 7. > What version do you use ? > Regards, > > -- > Serge Stinckwic > h > > Int. Research Unit > Â on Modelling/Simulation of Complex Systems (UMMISCO) > Sorbonne University > Â (SU) > French National Research Institute for Sustainable Development (IRD) > U > niversity of YaoundÃ© I, Cameroun > "Programs must be written for people to read, and only incidentally > for machines to execute." > https://twitter.com/SergeStinckwich >

Feb. 19, 2019

Pier3 & content management

by Albrecht Baur

Hey, what is the status of Pier3 + Pier3AddOns ? -> Seems to me that it is discontinued since Pharo 5, right ? I'm asking because I look around to see if there is a project usable as a starting point of a small web content management module for seaside (nothing too complicated / fancy). Is there something besides Pier that goes into this direction ? Thanks for hints, Albrecht

Feb. 19, 2019

Re: [Pharo-users] OSProcess / OSSubprocess / LibC uniqueInstance

by Serge Stinckwich

On Tue, Feb 19, 2019 at 11:56 AM David T. Lewis <lewis(a)mail.msen.com> wrote: > On Tue, Feb 19, 2019 at 11:37:38AM +0100, Albrecht Baur via Pharo-users > wrote: > > From: Albrecht Baur <baur.albrecht(a)googlemail.com> > > Subject: OSProcess / OSSubprocess / LibC uniqueInstance > > To: pharo-users(a)lists.pharo.org > > Date: Tue, 19 Feb 2019 11:37:38 +0100 > > > > I need to execute OS commands from within a x64 pharo 7.01 image on > > centos7 (for example: 'zip -r 123.zip zipme/'). > > > > I found these 3 tools: OSProcess, OSSubprocess, LibC uniqueInstance > > > > But I did not find any docu on which one to use for which use case. > > > > * OSProcess is in the catalog browser but fails loading because of > > ByteArray>>ifNotNilDo: > > -> So OSProcess is not to be used with p7 ? > > Hi Albrecht, > > I am sorry that I cannot check it right now, but it may be that > ConfigurationOfOSProcess needs to be updated. The #ifNotNilDo: problem > was fixed by Thierry Goubier in July 2017, so perhaps you are using > an out of date version. > > Hopefully someone else can give you a better answer, otherwise I will > try to follow up in a day or two. > > I have the same problem of ifNotNilDo: when I load OSProcess in Pharo 7. What version do you use ? Regards, -- Serge Stinckwic h Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) Sorbonne University (SU) French National Research Institute for Sustainable Development (IRD) U niversity of YaoundÃ© I, Cameroun "Programs must be written for people to read, and only incidentally for machines to execute." https://twitter.com/SergeStinckwich

Feb. 19, 2019

Re: [Pharo-users] OSProcess / OSSubprocess / LibC uniqueInstance

by David T. Lewis

On Tue, Feb 19, 2019 at 11:37:38AM +0100, Albrecht Baur via Pharo-users wrote: > From: Albrecht Baur <baur.albrecht(a)googlemail.com> > Subject: OSProcess / OSSubprocess / LibC uniqueInstance > To: pharo-users(a)lists.pharo.org > Date: Tue, 19 Feb 2019 11:37:38 +0100 > > I need to execute OS commands from within a x64 pharo 7.01 image on > centos7 (for example: 'zip -r 123.zip zipme/'). > > I found these 3 tools: OSProcess, OSSubprocess, LibC uniqueInstance > > But I did not find any docu on which one to use for which use case. > > * OSProcess is in the catalog browser but fails loading because of > ByteArray>>ifNotNilDo: > -> So OSProcess is not to be used with p7 ? Hi Albrecht, I am sorry that I cannot check it right now, but it may be that ConfigurationOfOSProcess needs to be updated. The #ifNotNilDo: problem was fixed by Thierry Goubier in July 2017, so perhaps you are using an out of date version. Hopefully someone else can give you a better answer, otherwise I will try to follow up in a day or two. Dave > > * OSSubprocess loads via catalog browser and the following snippet > works (even though 64 bit): > > OSSUnixSubprocess new > ?????? command: 'zip'; > ?????? arguments: #('-r' '123.zip' 'zipme'); > ?????? redirectStdout; > ?????? runAndWaitOnExitDo: [ :process :outString?? | > ?????? ?????? outString inspect > ?????? ] > > So is it ok to use OSSubprocess with 64 bit even though documented as 32 > bit only ? (here: > https://github.com/pharo-contributions/OSSubprocess#installation) > > * LibC uniqueInstance system: 'zip -r 123.zip zipme/' > ... works, but I don't know if its the right tool for this. > > Is there somewhere more info on which tool to use for which use case ? > > Thanks in advance! > > Albrecht > > PS.: I need to use zip as os process only because of this issue: > https://github.com/pharo-project/pharo/issues/2584 >

Feb. 19, 2019

OSProcess / OSSubprocess / LibC uniqueInstance

by Albrecht Baur

I need to execute OS commands from within a x64 pharo 7.01 image on centos7 (for example: 'zip -r 123.zip zipme/'). I found these 3 tools: OSProcess, OSSubprocess, LibC uniqueInstance But I did not find any docu on which one to use for which use case. * OSProcess is in the catalog browser but fails loading because of ByteArray>>ifNotNilDo: -> So OSProcess is not to be used with p7 ? * OSSubprocess loads via catalog browser and the following snippet works (even though 64 bit): OSSUnixSubprocess new Â Â Â command: 'zip'; Â Â Â arguments: #('-r' '123.zip' 'zipme'); Â Â Â redirectStdout; Â Â Â runAndWaitOnExitDo: [ :process :outStringÂ | Â Â Â Â Â Â outString inspect Â Â Â ] So is it ok to use OSSubprocess with 64 bit even though documented as 32 bit only ? (here: https://github.com/pharo-contributions/OSSubprocess#installation) * LibC uniqueInstance system: 'zip -r 123.zip zipme/' ... works, but I don't know if its the right tool for this. Is there somewhere more info on which tool to use for which use case ? Thanks in advance! Albrecht PS.: I need to use zip as os process only because of this issue: https://github.com/pharo-project/pharo/issues/2584

Feb. 19, 2019

Re: [Pharo-users] [Pharo-dev] About Iceberg

by Damien Pollet

ð On Tue, 19 Feb 2019 at 10:06, Hilaire <hilaire(a)drgeo.eu> wrote: > I join your thank you note, although I only use one half, the tonel > part, it is pleasant to be able to commit to file base repository and > use related tools. > > Le 19/02/2019 Ã 09:50, Sven Van Caekenberghe a Ã©crit : > > This is a thank you note about Iceberg. > > -- > Dr. Geo > http://drgeo.eu > > > > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Feb. 19, 2019

About Iceberg

by Sven Van Caekenberghe

Hi, This is a thank you note about Iceberg. I have been moving all my external and internal Pharo code to git/tonel/7 and on multiple occasions I have been pleasantly surprised about the functionality and performance of Iceberg. Basically, it just works. Finally, Pharo code lives in standard open source and commercial repositories (git, GitHub, Bitbucket, ...), without losing anything. I know that it took years to get here and that lots of code and community battles had to be fought. So thank you, to the whole team, you did a great job ! Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

Feb. 19, 2019

Re: [Pharo-users] im using pharo 7 with linux env. but cannot input korean.

by Hilaire

Hi Pierce, Yes, this option worked to key in Chinese. By the way, do you know if any option is needed on Windows? I checked for the options but I did not see anything relevant: hilaire@PCHome:~/Travaux/Developpement/DrGeoII/trunk/build/bundles/windows/DrGeo$ wine Contents/vm/DrGeo.exe --help Usage: Pharo Virtual Machine [vmOptions] imageFile [imageOptions] vmOptions: -service: ServiceName (install VM as NT service) -headless (force VM to run headless) -timephases (print start load and run times) -log: LogFile (use LogFile for VM messages) -memory: megaByte (set memory to megaByte MB) -breaksel: string (call warning on send of sel for debug) -breakmnu: string (call warning on MNU of sel for debug) -leakcheck: n (leak check on GC (1=full,2=incr,3=both)) -eden: bytes (set eden memory size to bytes) -stackpages: n (use n stack pages) -numextsems: n (allow up to n external semaphores) -checkpluginwrites (check for writes past end of object in plugins -noheartbeat (no heartbeat for debug) -trace[=num] enable tracing (optionally to a specific value) -warnpid (print pid in warnings) -[no]failonffiexception ([never]always catch exceptions in FFI calls) -codesize: bytes (set machine-code memory size to bytes) -cogmaxlits: n (set max number of literals for methods to be compiled to machine code) -cogminjumps: n (set min number of backward jumps for interpreted methods to be considered for compilation to machine code) -tracestores (assert-check stores for debug) -reportheadroom (report unused stack headroom on exit) -dpcso: bytes (stack offset for prim calls for debug) -maxoldspace: bytes (set max size of old space memory to bytes) -logscavenge (log scavenging to scavenge.log) Options begin with single -, but -- prefix is silently accepted Options with arguments -opt:n are also accepted with separators -opt n Le 16/02/2019 Ã 04:54, Pierce Ng a Ã©critÂ : > I start Pharo with -compositioninput (one dash, didn't try two dashes -- Dr. Geo http://drgeo.eu

Feb. 19, 2019

Re: [Pharo-users] Pharo 7: Problems with the new file chooser UI

by Offray Vladimir Luna CÃ¡rdenas

Hi Sven, Yes I was sure. But that's because I was using Pharo-7.0.0+rc1.build.19.sha.1fcbcd5170ad that was the one loaded from Pharo launcher 1.6.x from 31.01.2019. Now I have updated Pharo Launcher to 1.7.2 and it makes available the 7.0.1 versions of Pharo and now that functionality is working well... I just deal with other dependencies and changes... But Grafoscopio is taking better form now. Cheers, Offray On 18/2/19 17:13, Sven Van Caekenberghe wrote: > Are you really sure ? It works for me, Pharo 7.0.1 macOS. > >> On 18 Feb 2019, at 22:57, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: >> >> Hi, >> >> While I'm migrating Grafoscopio to Pharo 7 I get a deprecation warning telling me that I need to change the previous code for choosing a file from the UI, but now when I proceed as advised (using chooseExistingFileReference: title extensions: exts path: path). It returns a FileReference but all the paths are referred to the place where the running image is located, instead of the place where the selected file is located. >> >> For example if you run: >> >> [1]~~~~ >> >> (FileLocator documents / 'test.ston') ensureCreateFile writeStreamDo: [:stream | STON put: (Rectangle center: 10@10 extent: 100@50) onStream: stream ]. >> >> ~~~~ >> >> You will get a file on your Documents folder called test.ston, but If I choose that file using: >> >> [2]~~~~ >> >> file := UIManager default >> chooseExistingFileReference:'Choose a file' >> extensions: #('ston') >> path: FileLocator documents. >> >> ~~~~ >> >> and I choose the "test.ston" file created at [1], Pharo tells me that the file is located in the same place as the running image, instead on my Documents folder. >> >> Am I missing something? >> >> Thanks, >> >> Offray >> > >

Feb. 19, 2019

Re: [Pharo-users] Partition/Sync ready databases for Pharo?

by Pierce Ng

On Mon, Feb 18, 2019 at 02:56:10PM -0300, Esteban Maringolo wrote: > I have the requirement that an app that I'm prospecting must be able > to work offline and synchronize changes once the connection is > restored. > > I want to avoid having to write "sync" logic manually. I've not done this for real before, but here are some possibilities: - https://github.com/sqlite-sync/SQLite-sync.com - http://www.symmetricds.org/ - https://github.com/CanonicalLtd/dqlite - Use Fossil as your database

Feb. 19, 2019

Re: [Pharo-users] Running pharo in daemon mode

by Pierce Ng

On Mon, Feb 18, 2019 at 04:39:03PM -0500, sergio ruiz wrote: > I found my issue.. I need to be running in daemon mode.. i was running with > &, but as soon as my connection lets go, the app dies.. My daemontools run file: #!/bin/sh /usr/bin/setuidgid app1 \ /pkg/vm/pharo -vm-display-null -vm-sound-null app1.image --no-quit My Dockerfile CMD /pkg/vm/pharo -vm-display-null -vm-sound-null app.image --no-quit st runApp.st You could also try '-headless' instead of '-vm-display-null'. Pierce

Feb. 19, 2019

Re: [Pharo-users] Iceberg working with forks - can it be easier?

by Tim Mackinnon

Hi Guille - thanks for taking the time to write this upâ¦ in the middle there I finally spotted the crucial bit âclone the original, push to your forkâ. I think thats what Iâve been doing wrong - and it leads to all kinds of confusion (at least Iâm hoping this is what it is). As I have cloned from my Fork (and in my defence - its because we were given a repository that collides with the pharo one - exercism/pharo - and P7 doesnât let us clone from that) - so Iâve had to clone from my fork. It all seemed to work until I started submitting my PRâs and then they seem to include commits going much further back than I think they should need Even wen I thought I was being careful and syncing to master - it still seems to go back to some of my earliest work. Now that we have managed to get the repo renamed - I will try working like you have suggested and make sure that it is working like you describe - as it shouldnât be as complicated as this to make clean isolated changes and then submit them as a PR. (otherwise Pharo would fall apart). One question I do have however - is what is the best procedure if you realised when making changes that A) you forgot to make changes in a branch (so are working on master) B) you are working in a branch but decide some of your changes should go in another branch itself based on master (how to stash?) These are 2 common scenarios Iâve found when trying to be a good citizen for my little project. Do I have to go to the terminal to do this stuff - or can I cleanly do these kinds of operations in Pharo (which I think you should be able to do, as its so easy to get into either of those states). Thanks in advance. Tim > On 18 Feb 2019, at 08:56, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi! > > On Fri, Feb 15, 2019 at 7:06 PM Tim Mackinnon <tim(a)testit.works> wrote: > Hi guys - Iâve spent a few hours scratching my head trying to understand why some of my Pull Requests to a project I had forked kept showing my previous commits when I thought I was all caught up. > > It suddenly dawned on me, that when I had forked, and then done some work and then submitted a PR, and then applied it upstream that my fork is now no longer in sync with its upstream counterpart. > > Having not done this in ages, it took me a while to then realise I have to do some git stuff to get it back in sync e.g. (and I think Iâve got this right) > > git fetch upstream (or whatever name you gave it) > Git checkout master > Git merge upstream/master > > When you did your clone, did you clone the original repository or your fork's? > One way to simplify this workflow is: > - you clone always the original repository > - you create a branch and work there > - then you'll push your branch to your fork + fork > > That way your branch will be always up to date with the original repository, and no need to sync (actually the sync is done automatically when you push to your fork). > > Of course this assumes you're doing a new clone every time you work :). > > > So I guess my question is - wouldnât it be helpful if this was a command in Iceberg? > > It would, there are several places where we could simplify the workflow for common cases, I agree. > > It seems quite common to fork a project (I think this is still recommended for pharo itself isnât it?) > > I'd say its mandatory :). Otherwise you will not be able to push directly to it because of permission problems (actually all main dev branches are now blocked so **nobody**, not even admins, push to them directly). > > - and then at some point you need to catchup with that origin again? Or am I missing something? > > Well, it really depends on the workflow you use. Above I've explained a workflow that works when you clone every time. > Git is so complex and so low level that you can do lots of different things with it. > > First thing is to understand what "catch up with origin" means. In my head it only means: > - checkout your "to-catchup" branch > - merge the remote "to-catchup" branch and merge it > > All the rest is workflow dependent. Even (!!) I would argue that merging is not, strictly speaking, a correct way to catch up: If you have made changes into "to-catchup", then merging will not make both branches the same, but your "to-catchup" branch may have extra commits that you did not want to introduce... > > And here I'm not saying you should not merge, actually I do it most of the times because I know that 90% of the times it will be ok, and I do rollback when I realize I was in the other 10%... > > I guess lots of stuff can go wrong - but if it does - youâd still get the same problems on the command line. > > Yes, and no. The "lots of stuff can go wrong" can be translated in most of the cases to "I had a merge conflict". But this is not git, this is git+pharo. > > The thing is that with Git, your code is dead in files. With Iceberg, your code is in the files but it also may be alive in your image too. So updating code for what you have existing instances, or announcement subscriptions or other could (and probably will) mess up with the running code... > So to the typical merge conflict, you may add breaking your running system. > > It just seems that for normal situations - it would be handy to run this straight in Pharo. > > Thoughts from the git experts? > > For these cases, you can do exactly as the command line from Iceberg's UI > > - change your branch to your "to-catchup" master > - fetch > - now you can go to the merge option, and choose to merge your remote branch into your checked-out branch. > - and push > > Of course, this simple workflow works most of the times, but you may find edge cases. > For those edge cases (typically updating iceberg itself, or trying to update pharo itself), in the checkout preview you will have the combo with the checkout strategy: choose the expert mode "do not load the code". This option will change the branch on git's world, but it will not load the code in your image. > > That is useful if you have living instances for example. > This option will though make a diff between the checked out version and your image code and show you differences. (think this as a git reset --soft) > > To me the fact that we are manipulating live code loaded in the image and not dead files makes a huge difference, and this makes that extrapolating git commands to iceberg is not so straight forward :). Also, understanding that git is stateful/context dependant, and applying an operation means changing your current state (modify your current branch, change your current branch) is useful to see the consequences. > > In any case, any more concrete suggestions for enhancing this workflow are welcome. I think that neither Esteban, Pablo, me nor other contributors are skilled UI designers, and thinking about the best way to present a usecase to a user is super super hard :). > > Guille, from his vacations >

Feb. 19, 2019

Re: [Pharo-users] Should epicea help me recover changes in a system crash?

by Tim Mackinnon

Ok - if its supposed to work in this situation, I will zip up that image and put it somewhere to try and figure out what happened. > On 18 Feb 2019, at 17:54, ducasse <stepharo(a)netcourrier.com> wrote: > > Hi tim > > this is strange. Normally epicea logs all the changes. In the past I got missing classes. > Epicea is git ignorant. So I do not see how it could interact. > I would love to see your bug solved. Could you keep your image and may be martin > has some time to have a look (he got flying back to chile). > > Stef > >> On 18 Feb 2019, at 18:13, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Hi - Iâve got mixed experiences with epicea - having had a few image seg faults recently its presented some of my changes and let me recover them. >> >> However just now, I had been working for an hour and my whole laptop went black (and then had the apple logo). I took the opportunity to apply the latest HighSierra updates (it has been a while) - but when I relaunched my image - epicea detected missing code however what it shows me is nothing like the changes I had recently made - it just showed me a merge change? >> >> Is it possible that if Iâm on the wrong branch - it wonât show me changes I made recently? >> >> I find Iâm kind of missing the old changes text file (which we say we are getting rid of) as at least it let me see an historic account of what I had done - as now things are a bit all of over the place (do-its you have to find in the playground history) and epicea is supposed to show the rest - execpt it doesnât appear to do so? >> >> Tim > > >

Feb. 19, 2019

Re: [Pharo-users] Pharo 7: Problems with the new file chooser UI

by Sven Van Caekenberghe

Are you really sure ? It works for me, Pharo 7.0.1 macOS. > On 18 Feb 2019, at 22:57, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Hi, > > While I'm migrating Grafoscopio to Pharo 7 I get a deprecation warning telling me that I need to change the previous code for choosing a file from the UI, but now when I proceed as advised (using chooseExistingFileReference: title extensions: exts path: path). It returns a FileReference but all the paths are referred to the place where the running image is located, instead of the place where the selected file is located. > > For example if you run: > > [1]~~~~ > > (FileLocator documents / 'test.ston') ensureCreateFile writeStreamDo: [:stream | STON put: (Rectangle center: 10@10 extent: 100@50) onStream: stream ]. > > ~~~~ > > You will get a file on your Documents folder called test.ston, but If I choose that file using: > > [2]~~~~ > > file := UIManager default > chooseExistingFileReference:'Choose a file' > extensions: #('ston') > path: FileLocator documents. > > ~~~~ > > and I choose the "test.ston" file created at [1], Pharo tells me that the file is located in the same place as the running image, instead on my Documents folder. > > Am I missing something? > > Thanks, > > Offray >

Feb. 18, 2019

Re: [Pharo-users] Running pharo in daemon mode

by Sven Van Caekenberghe

There are many options. Did you read https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… ? You can also study this https://github.com/svenvc/pharo-server-tools nohup is an easy to use, quick and dirty solution. > On 18 Feb 2019, at 22:39, sergio ruiz <sergio.rrd(a)gmail.com> wrote: > > Hey, all.. > > I found my issue.. I need to be running in daemon mode.. i was running with &, but as soon as my connection lets go, the app dies.. > > I tried using daemon tools, but it looks like the site stays up for one second, and a new PID is generated.. > > Anyone have any hints on how people are doing this lately? > > Thanks! > > > > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: http://bit.ly/29z9fG0 > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > http://www.codeandmusic.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101

Feb. 18, 2019

Pharo 7: Problems with the new file chooser UI

by Offray Vladimir Luna CÃ¡rdenas

Hi, While I'm migrating Grafoscopio to Pharo 7 I get a deprecation warning telling me that I need to change the previous code for choosing a file from the UI, but now when I proceed as advised (using |chooseExistingFileReference: title extensions: exts path: path|). It returns a |FileReference| but all the paths are referred to the place where the running image is located, instead of the place where the selected file is located. For example if you run: [1]~~~~ (FileLocator documents / 'test.ston') ensureCreateFileÂ writeStreamDo:Â [:stream | STON put: (Rectangle center: 10@10 extent: 100@50) onStream: stream ]. ~~~~ You will get a file on your Documents folder called test.ston, but If I choose that file using: [2]~~~~ file := UIManager default Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â chooseExistingFileReference:'Choose a file' Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â extensions: #('ston') Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â path: FileLocator documents. ~~~~ and I choose the "test.ston" file created at [1], Pharo tells me that the file is located in the same place as the running image, instead on my Documents folder. Am I missing something? Thanks, Offray

Feb. 18, 2019