November 2018 - Pharo-users

Re: [Pharo-users] [ANN] Teapot was moved to GitHub

by Esteban Maringolo

El miÃ©., 28 nov. 2018 a las 16:01, Sven Van Caekenberghe (<sven(a)stfx.eu>) escribiÃ³: > > Nice docs, thank you. +1 I couldn't avoid reading the whole getting started doc. Excellent material. I also liked that you not only provided instructions for installation, but also to set Teapot as a dependency. Please add the `pharo` tag to the repository, so it gets listed in the topics section [1] and also helps bumping Pharo topic to the home of the Topics page. [1] https://github.com/topics/pharo?o=desc&s=updated Esteban A. Maringolo

Nov. 28, 2018

Re: [Pharo-users] [ANN] Teapot was moved to GitHub

by Sven Van Caekenberghe

Nice docs, thank you. > On 28 Nov 2018, at 08:49, Attila Magyar <m.magyar3(a)gmail.com> wrote: > > Hi, > > I just want to let you know that the source code of Teapot was moved from > Smalltalkhub to GitHub. > > The new repository is located at: > > https://github.com/zeroflag/teapot <https://github.com/zeroflag/teapot> > > Attila > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Nov. 28, 2018

Re: [Pharo-users] Loading Metacello with Seaside

by Vitor Medina Cruz

> > "I tried to load magritte only and I got the same problem. Maybe I do not > have it in my project because I load seaside before with an other group?" > Probably "You can try to add seaside yourself in your project. Something like:" > I will try that :( On Wed, Nov 28, 2018 at 3:22 PM Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > Le 28/11/2018 Ã 17:38, Vitor Medina Cruz a Ã©crit : > > Tried now, didn't work, same error. It is working for you? > > > > I tried to load magritte only and I got the same problem. Maybe I do not > have it in my project because I load seaside before with an other group? > > I think there was an issue that is fixed in the dev version of Seaside > about that. It should be in the next release. > > You can try to add seaside yourself in your project. Something like: > > baseline: spec > <baseline> > spec > for: #common > do: [ > spec > baseline: 'Seaside3' with: [ spec repository: > 'github://SeasideSt/Seaside/repository' ]; > baseline: 'Magritte' > with: [ spec > loads: #('Seaside' 'Core'); > repository: > 'github://magritte-metamodel/magritte:v3.5.3/source' ]. > spec package: 'Employees' with: [ spec requires: #('Seaside3' > 'Magritte') ] ] > > > > -- > Cyril Ferlicot > https://ferlicot.fr > >

Nov. 28, 2018

Re: [Pharo-users] [ANN] Teapot was moved to GitHub

by Norbert Hartl

Great! Thanks! Norbert > Am 28.11.2018 um 08:49 schrieb Attila Magyar <m.magyar3(a)gmail.com>: > > Hi, > > I just want to let you know that the source code of Teapot was moved from > Smalltalkhub to GitHub. > > The new repository is located at: > > https://github.com/zeroflag/teapot <https://github.com/zeroflag/teapot> > > Attila > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Nov. 28, 2018

Re: [Pharo-users] Loading Metacello with Seaside

by Cyril Ferlicot D.

Le 28/11/2018 Ã 17:38, Vitor Medina Cruz a Ã©critÂ : > Tried now, didn't work, same error. It is working for you? > I tried to load magritte only and I got the same problem. Maybe I do not have it in my project because I load seaside before with an other group? I think there was an issue that is fixed in the dev version of Seaside about that. It should be in the next release. You can try to add seaside yourself in your project. Something like: baseline: spec <baseline> spec for: #common do: [ spec baseline: 'Seaside3' with: [ spec repository: 'github://SeasideSt/Seaside/repository' ]; baseline: 'Magritte' with: [ spec loads: #('Seaside' 'Core'); repository: 'github://magritte-metamodel/magritte:v3.5.3/source' ]. spec package: 'Employees' with: [ spec requires: #('Seaside3' 'Magritte') ] ] -- Cyril Ferlicot https://ferlicot.fr

Nov. 28, 2018

Re: [Pharo-users] Loading Metacello with Seaside

by Vitor Medina Cruz

Tried now, didn't work, same error. It is working for you? On Wed, Nov 28, 2018 at 8:34 AM Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > I tried with Baseline also, but it didn't work. I will try again as I can > have made some mistake and I will report here. > > On Tue, Nov 27, 2018 at 9:19 PM Cyril Ferlicot D. < > cyril.ferlicot(a)gmail.com> wrote: > >> Le 28/11/2018 Ã 00:08, Vitor Medina Cruz a Ã©crit : >> > Hello! >> > >> > WIndows 10 here with Pharo 7 32 bits. Here is my baseline: >> > >> > >> > baseline: spec >> > >> > <baseline> >> > >> > spec for: #'common' do: [ >> > spec blessing: #'baseline'; >> > repository: >> 'gitlab://vitormcruz/employees:master/pharo/'; >> > >> > project: 'Magritte3' with: [ spec repository: >> > 'github://magritte-metamodel/magritte:v3.5.3/source'; >> > className: >> > 'ConfigurationOfMagritte3'; >> > loads: #(Seaside >> > Core) ]; >> > >> > package: 'Employees' with: [ spec requires: >> > #('Magritte3'). ]; >> > >> > group: 'default' with: #('core'); >> > group: 'core' with: #('Employees') >> > >> > >> > >> > When I execute: >> > >> > Metacello new baseline: #Employees; >> > repository: >> > 'gitlab://vitormcruz/employees:master/pharo/'; load: #(core) >> > >> > >> > I got: >> > >> > "project group, or package named: 'Seaside-Pharo-Development' not >> > found when used in requires: or includes: field of package: >> > 'Seaside-Tests-Pharo-Development' for version: baseline of >> > BaselineOfSeaside3." >> > >> > >> > >> > It seems there is a problem with Magrite ConfigurationOf, am I correct? >> > >> > >> > Some general information: >> > >> > 1- Using https://github.com/magritte-metamodel/magritte instead >> > /magritte:v3.5.3/ of 'github://magritte-metamodel/magritte:v3.5.3/source >> > don't work; >> > >> > 2- You must provide className otherwise it does no work, even if docs >> > says itis not needed; >> > >> > 3- Metacello fail in ways it is hard to understand what happened; >> > >> > 4- On Pharo 64bits, Iceberg commit fails. >> > >> > < >> http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam… >> > >> > Livre de vÃrus. www.avg.com >> > < >> http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam… >> >. >> > >> > >> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >> >> Hi, >> >> Personally I declare my Magritte dependency with the Seaside group this >> way: >> >> spec >> baseline: 'Magritte' >> with: [ spec >> loads: #('Seaside'); >> repository: 'github://magritte-metamodel/magritte:v3.5.3/source' ]. >> >> If it can help you, here is a recent guide to Baselines: >> >> https://github.com/pharo-tips-and-tricks/pharo-tips-and-tricks/blob/master/… >> >> -- >> Cyril Ferlicot >> https://ferlicot.fr >> >>

Nov. 28, 2018

Re: [Pharo-users] Unable to compile myself Pharo

by tesonep＠gmail.com

Hi Alexandre, as CÃ©drick said there is no need to generate a new image from scratch. Pharo is basically divided in two parts an image (that is the one that it is generated by the process you want to run) and a virtual machine to run the image. The image is multi-OS you can download a 32 bits image and run it in any of the supported operating systems. Usually the VM will run in different OSs, there is a VM for Mac OS, one for Windows and one for Unix(es). The VM came in 32 and 64 bits flavors. You should try to run the pre built version of the pack. And again using the Pharo Launcher will be the simpler option. Cheers, Pablo On Wed, Nov 28, 2018 at 1:02 PM CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > Hi Alexandre, > > Do you really want to Â« bootstrap Â» an image ? You donât need to (just use > an official image). > > Try here, either through the launcher or the curl command line: > > https://pharo.org/download (Linux for thÃ© launcher or at the end of the > page from the command line. > > HTH, > > Cedrick > > EnvoyÃ© de mon iPhone > > Le 28 nov. 2018 Ã 11:23, Garreau, Alexandre <galex-713(a)galex-713.eu> a > Ã©crit : > > Le 28/11/2018 Ã 11h17, Garreau, Alexandre a Ã©crit : > > This VM uses a separate heartbeat thread to update its internal clock > > and handle events. For best operation, this thread should run at a > > higher priority, however the VM was unable to change the priority. The > > effect is that heavily loaded systems may experience some latency > > issues. If this occurs, please create the appropriate configuration > > file in /etc/security/limits.d/ as shown below: > > > cat <<END | sudo tee /etc/security/limits.d/pharo.conf > > * hard rtprio 2 > > * soft rtprio 2 > > END > > > and report to the pharo mailing list whether this improves behaviour. > > > Btw changing this didnât improve anything until then, since build still > fails (but the error disappeared). > > Sorry to clutter with a second mail. > > -- Pablo Tesone. tesonep(a)gmail.com

Nov. 28, 2018

Re: [Pharo-users] Unable to compile myself Pharo

by CÃ©drick BÃ©ler

Hi Alexandre, Do you really want to Â« bootstrap Â» an image ? You donât need to (just use an official image). Try here, either through the launcher or the curl command line: https://pharo.org/download (Linux for thÃ© launcher or at the end of the page from the command line. HTH, Cedrick EnvoyÃ© de mon iPhone > Le 28 nov. 2018 Ã 11:23, Garreau, Alexandre <galex-713(a)galex-713.eu> a Ã©crit : > >> Le 28/11/2018 Ã 11h17, Garreau, Alexandre a Ã©crit : >> This VM uses a separate heartbeat thread to update its internal clock >> and handle events. For best operation, this thread should run at a >> higher priority, however the VM was unable to change the priority. The >> effect is that heavily loaded systems may experience some latency >> issues. If this occurs, please create the appropriate configuration >> file in /etc/security/limits.d/ as shown below: >> >> cat <<END | sudo tee /etc/security/limits.d/pharo.conf >> * hard rtprio 2 >> * soft rtprio 2 >> END >> >> and report to the pharo mailing list whether this improves behaviour. > > Btw changing this didnât improve anything until then, since build still > fails (but the error disappeared). > > Sorry to clutter with a second mail. >

Nov. 28, 2018

Re: [Pharo-users] Reify RBLiteralNode and RBBlockNode args/return with MetaLink?

by Marcus Denker

> > >>> iii) How are cascaded message sends reified? Am I supposed to instrument the cascade node or the individual message sends? >>> > > https://pharo.fogbugz.com/f/cases/22702/support-before-after-intead-on-RBCa… <https://pharo.fogbugz.com/f/cases/22702/support-before-after-intead-on-RBCa…> > > It turns out this is just not implemented. Single message sends *inside* should work (as it calls the same code as a normal send to emit code). > But even that needs tests. > > Cascade itself needs some code for links, then it will be easy to add reifications for #receiver and #value (and #operation). > Done: https://github.com/pharo-project/pharo/pull/2018 <https://github.com/pharo-project/pharo/pull/2018> Marcus

Nov. 28, 2018

Re: [Pharo-users] Loading Metacello with Seaside

by Vitor Medina Cruz

I tried with Baseline also, but it didn't work. I will try again as I can have made some mistake and I will report here. On Tue, Nov 27, 2018 at 9:19 PM Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > Le 28/11/2018 Ã 00:08, Vitor Medina Cruz a Ã©crit : > > Hello! > > > > WIndows 10 here with Pharo 7 32 bits. Here is my baseline: > > > > > > baseline: spec > > > > <baseline> > > > > spec for: #'common' do: [ > > spec blessing: #'baseline'; > > repository: > 'gitlab://vitormcruz/employees:master/pharo/'; > > > > project: 'Magritte3' with: [ spec repository: > > 'github://magritte-metamodel/magritte:v3.5.3/source'; > > className: > > 'ConfigurationOfMagritte3'; > > loads: #(Seaside > > Core) ]; > > > > package: 'Employees' with: [ spec requires: > > #('Magritte3'). ]; > > > > group: 'default' with: #('core'); > > group: 'core' with: #('Employees') > > > > > > > > When I execute: > > > > Metacello new baseline: #Employees; > > repository: > > 'gitlab://vitormcruz/employees:master/pharo/'; load: #(core) > > > > > > I got: > > > > "project group, or package named: 'Seaside-Pharo-Development' not > > found when used in requires: or includes: field of package: > > 'Seaside-Tests-Pharo-Development' for version: baseline of > > BaselineOfSeaside3." > > > > > > > > It seems there is a problem with Magrite ConfigurationOf, am I correct? > > > > > > Some general information: > > > > 1- Using https://github.com/magritte-metamodel/magritte instead > > /magritte:v3.5.3/ of 'github://magritte-metamodel/magritte:v3.5.3/source > > don't work; > > > > 2- You must provide className otherwise it does no work, even if docs > > says itis not needed; > > > > 3- Metacello fail in ways it is hard to understand what happened; > > > > 4- On Pharo 64bits, Iceberg commit fails. > > > > < > http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam… > > > > Livre de vÃrus. www.avg.com > > < > http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam… > >. > > > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > Hi, > > Personally I declare my Magritte dependency with the Seaside group this > way: > > spec > baseline: 'Magritte' > with: [ spec > loads: #('Seaside'); > repository: 'github://magritte-metamodel/magritte:v3.5.3/source' ]. > > If it can help you, here is a recent guide to Baselines: > > https://github.com/pharo-tips-and-tricks/pharo-tips-and-tricks/blob/master/… > > -- > Cyril Ferlicot > https://ferlicot.fr > >

Nov. 28, 2018