June 2017 - Pharo-users - lists.pharo.org

Loading PharoJS Re: PharoJS

by Pierce Ng

Just tried loading PharoJS with this snippet: Gofer it smalltalkhubUser: 'noury' project: 'PharoJS'; configuration; loadStable Loaded cleanly on a fresh 32-bit Pharo-50772 image. Ran almost half the tests during which it created/deleted tabs on my open Chromium browser repeatedly. Then the tests started a new instance of my default browser (which happens to be Midori) and here seemingly the web socket stuff didn't work so well, so I aborted the tests, but this I attribute to Midori not PharoJS. On a fresh 64-bit Pharo-60501 image, while loading PharoJSBridge-NouryBouraqadi-120, error encountered: SyntaxError: Variable or expression expected Object as yet unclassified makeInspect makeInspect. Variable or expression expected-><javascript: 'blah blah blah blah }'> Closing the error alert box brought up a debugger at RBParser>>parserError:. Any idea what to fix, anyone? Pierce

June 25, 2017

Re: [Pharo-users] Working with a compressed Fuel file?

by stephan

A long time ago, Mariano wrote: > And what happened with the vm gzip crash? Still around? Yep, still crashing the vm. I revisited my MonticelloProjects experiment yesterday, and am still crashing the vm when serializing to a compressed fuel file. I wrote about it at the time, and then gave up as the vm was less stable during that period. To reproduce the crash in a pharo6 image: |project| Gofer it smalltalkhubUser: 'StephanEggermont' project: 'MonticelloProjects'; package: 'MonticelloProjects'; load. project := (Smalltalk at: #MCProject) new location: 'http://smalltalkhub.com/mc/StephanEggermont/Documentation/main'. project read. project saveToFile. That reliably crashes in saveToFile. It seems to be independent of 32/64 bit and mac/linux, as I tried some variations. Crash dumps in a mail to the vm list Stephan

June 25, 2017

Re: [Pharo-users] PharoJS

by Offray Vladimir Luna CÃ¡rdenas

I think that such diversity of tools is healthy and I wouldn't commit on killing anything. Projects would organically found ways of working together. Compared with other languages, I think that Pharo ecosystem is pretty cohesive. I would follow Steph's advice about choosing a theme/project and document your experience that help others to traverse such diversity instead of killing it. Cheers, Offray On 22/06/17 13:01, askoh wrote: > Norbert: > > I appreciate you explanation of Amber and PharoJS. I feel at a lost > understanding the plethora of Smalltalk + Web frameworks. Is there a place > where there is a pros and cons comparison of frameworks: > Seaside, SqueakJS, PharoJS, Amber, Caffeine, VisualWorks Appex, Illiad, > Aida, Teapot, etc? > > The sheer number of frameworks just makes it difficult for anyone to commit. > It is terrifying. Can we discuss and consolidate the best features into one > or two and kill the rest? > > All the best, > Aik-Siong Koh > > > > -- > View this message in context: http://forum.world.st/Re-PharoJS-tp4952267p4952361.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

June 25, 2017

Re: [Pharo-users] Pharo6 bootstrap how to

by Esteban Lorenzano

> On 25 Jun 2017, at 10:41, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Thank you for the update, the original script was done for older Iceberg versions. indeed :) Esteban > > Cheers, > -- Pavel > > 2017-06-25 10:38 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > Hi! > >> On 25 Jun 2017, at 10:14, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> wrote: >> >> You can clone a repository with Iceberg with a script like this: >> >> target := 'pharo-core' asFileReference ensureCreateDirectory. >> repository := IceRepositoryCreator new >> remote: (IceRemote url: 'git(a)github.com <mailto:git@github.com>:pharo-project/pharo.git'); >> location: target; >> subdirectory:'src'; >> createRepository. >> repository backend checkoutBranch: 'development'. >> repository register. > > this is a bit too verbose for my taste :) > you can do the same with this (which is more or less the same, btwâ¦ just more compact) > > repository := IceRepositoryCreator new > remote: (IceRemote url: 'git(a)github.com <mailto:git@github.com>:pharo-project/pharo.git'); > subdirectory:'src'; > createRepository. > repository checkoutBranch: 'development'. > repository register. > > - no need to violate demeters law by accessing directly to backend > - no need to specify a target location because it will put it in default place. > > :) > > Esteban > >> >> Setting of the system version is already fixed in Pharo 7. For Pharo 6 you want to do something like this: >> >> ./pharo Pharo.image eval --save "| updateString | updateString := 'tag.txt' asFileReference readStream contents allButFirst. SystemVersion classPool at: #Current put: (SystemVersion new type: 'Pharo'; major: updateString first asString asInteger; minor: updateString second asString asInteger; highestUpdate: updateString asInteger; suffix: ''; yourself)" >> >> Where tag.txt can by obtained from git by: >> git describe --tags > tag.txt >> >> Cheers, >> -- Pavel >> >> >> >> >> 2017-06-24 22:06 GMT+02:00 Alistair Grant <akgrant0710(a)gmail.com <mailto:akgrant0710@gmail.com>>: >> Hi Pavel, >> >> On Fri, Jun 23, 2017 at 10:08:29PM +0200, Pavel Krivanek wrote: >> > clone the master branch of git(a)github.com <mailto:git@github.com>:pharo-project/pharo.git and inside >> > this clone do: >> > >> > export PHARO_VERSION=60 >> > export BOOTSTRAP_ARCH=32 >> > >> > wget -O - get.pharo.org/${PHARO_VERSION}+vm <http://get.pharo.org/$%7BPHARO_VERSION%7D+vm> | bash >> > >> > ./pharo Pharo.image --no-default-preferences ./bootstrap/scripts/ >> > prepare_image.st <http://prepare_image.st/> --save --quit >> > ./pharo Pharo.image --no-default-preferences ./bootstrap/scripts/bootstrap.st <http://bootstrap.st/> >> > --ARCH=${BOOTSTRAP_ARCH} --quit >> > bash ./bootstrap/scripts/build.sh >> >> >> Thanks very much for providing these instructions. >> >> It would be great to have a version of the script that used Iceberg to >> load the code and kept the repository (pharo-project/pharo in the >> example above, but normally this would be a fork of the repository). >> This would greatly facilitate creating pull requests with bug fixes. >> >> I'll try and figure out how to modify your script to do this, but if >> you're able to provide a quick answer, or even a hint, it would be much >> appreciated. >> >> Also, the version information doesn't appear to be set here, i.e.: >> >> $ pharo Pharo.image printVersion >> [version] nil.nil #0 >> >> I'll try and figure this out, but if you know, what do I need to do to >> get this set? >> >> Thanks again, >> Alistair >> >> > >

June 25, 2017

Re: [Pharo-users] Pharo6 bootstrap how to

by Pavel Krivanek

Thank you for the update, the original script was done for older Iceberg versions. Cheers, -- Pavel 2017-06-25 10:38 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi! > > On 25 Jun 2017, at 10:14, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > You can clone a repository with Iceberg with a script like this: > > target := 'pharo-core' asFileReference ensureCreateDirectory. > repository := IceRepositoryCreator new > remote: (IceRemote url: 'git@github.com:pharo-project/pharo.git'); > location: target; > subdirectory:'src'; > createRepository. > repository backend checkoutBranch: 'development'. > repository register. > > > this is a bit too verbose for my taste :) > you can do the same with this (which is more or less the same, btwâ¦ just > more compact) > > repository := IceRepositoryCreator new > remote: (IceRemote url: 'git@github.com:pharo-project/pharo.git'); > subdirectory:'src'; > createRepository. > repository checkoutBranch: 'development'. > repository register. > > - no need to violate demeters law by accessing directly to backend > - no need to specify a target location because it will put it in default > place. > > :) > > Esteban > > > Setting of the system version is already fixed in Pharo 7. For Pharo 6 you > want to do something like this: > > ./pharo Pharo.image eval --save "| updateString | updateString := > 'tag.txt' asFileReference readStream contents allButFirst. SystemVersion > classPool at: #Current put: (SystemVersion new type: 'Pharo'; major: > updateString first asString asInteger; minor: updateString second asString > asInteger; highestUpdate: updateString asInteger; suffix: ''; yourself)" > > Where tag.txt can by obtained from git by: > git describe --tags > tag.txt > > Cheers, > -- Pavel > > > > > 2017-06-24 22:06 GMT+02:00 Alistair Grant <akgrant0710(a)gmail.com>: > >> Hi Pavel, >> >> On Fri, Jun 23, 2017 at 10:08:29PM +0200, Pavel Krivanek wrote: >> > clone the master branch of git@github.com:pharo-project/pharo.git and >> inside >> > this clone do: >> > >> > export PHARO_VERSION=60 >> > export BOOTSTRAP_ARCH=32 >> > >> > wget -O - get.pharo.org/${PHARO_VERSION}+vm >> <http://get.pharo.org/$%7BPHARO_VERSION%7D+vm> | bash >> > >> > ./pharo Pharo.image --no-default-preferences ./bootstrap/scripts/ >> > prepare_image.st --save --quit >> > ./pharo Pharo.image --no-default-preferences ./bootstrap/scripts/ >> bootstrap.st >> > --ARCH=${BOOTSTRAP_ARCH} --quit >> > bash ./bootstrap/scripts/build.sh >> >> >> Thanks very much for providing these instructions. >> >> It would be great to have a version of the script that used Iceberg to >> load the code and kept the repository (pharo-project/pharo in the >> example above, but normally this would be a fork of the repository). >> This would greatly facilitate creating pull requests with bug fixes. >> >> I'll try and figure out how to modify your script to do this, but if >> you're able to provide a quick answer, or even a hint, it would be much >> appreciated. >> >> Also, the version information doesn't appear to be set here, i.e.: >> >> $ pharo Pharo.image printVersion >> [version] nil.nil #0 >> >> I'll try and figure this out, but if you know, what do I need to do to >> get this set? >> >> Thanks again, >> Alistair >> >> > >

June 25, 2017

Re: [Pharo-users] Pharo6 bootstrap how to

by Esteban Lorenzano

> On 25 Jun 2017, at 10:38, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi! > >> On 25 Jun 2017, at 10:14, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> wrote: >> >> You can clone a repository with Iceberg with a script like this: >> >> target := 'pharo-core' asFileReference ensureCreateDirectory. >> repository := IceRepositoryCreator new >> remote: (IceRemote url: 'git(a)github.com <mailto:git@github.com>:pharo-project/pharo.git'); >> location: target; >> subdirectory:'src'; >> createRepository. >> repository backend checkoutBranch: 'development'. >> repository register. > > this is a bit too verbose for my taste :) > you can do the same with this (which is more or less the same, btwâ¦ just more compact) > > repository := IceRepositoryCreator new > remote: (IceRemote url: 'git(a)github.com <mailto:git@github.com>:pharo-project/pharo.git'); > subdirectory:'src'; > createRepository. > repository checkoutBranch: 'development'. > repository register. Ah, and not that I think, you can also doit like this: repository := IceRepositoryCreator new url: 'git(a)github.com <mailto:git@github.com>:pharo-project/pharo.git'; subdirectory:'src'; createRepository. repository checkoutBranch: 'development'. repository register. :) > - no need to violate demeters law by accessing directly to backend > - no need to specify a target location because it will put it in default place. > > :) > > Esteban > >> >> Setting of the system version is already fixed in Pharo 7. For Pharo 6 you want to do something like this: >> >> ./pharo Pharo.image eval --save "| updateString | updateString := 'tag.txt' asFileReference readStream contents allButFirst. SystemVersion classPool at: #Current put: (SystemVersion new type: 'Pharo'; major: updateString first asString asInteger; minor: updateString second asString asInteger; highestUpdate: updateString asInteger; suffix: ''; yourself)" >> >> Where tag.txt can by obtained from git by: >> git describe --tags > tag.txt >> >> Cheers, >> -- Pavel >> >> >> >> >> 2017-06-24 22:06 GMT+02:00 Alistair Grant <akgrant0710(a)gmail.com <mailto:akgrant0710@gmail.com>>: >> Hi Pavel, >> >> On Fri, Jun 23, 2017 at 10:08:29PM +0200, Pavel Krivanek wrote: >> > clone the master branch of git(a)github.com <mailto:git@github.com>:pharo-project/pharo.git and inside >> > this clone do: >> > >> > export PHARO_VERSION=60 >> > export BOOTSTRAP_ARCH=32 >> > >> > wget -O - get.pharo.org/${PHARO_VERSION}+vm <http://get.pharo.org/$%7BPHARO_VERSION%7D+vm> | bash >> > >> > ./pharo Pharo.image --no-default-preferences ./bootstrap/scripts/ >> > prepare_image.st <http://prepare_image.st/> --save --quit >> > ./pharo Pharo.image --no-default-preferences ./bootstrap/scripts/bootstrap.st <http://bootstrap.st/> >> > --ARCH=${BOOTSTRAP_ARCH} --quit >> > bash ./bootstrap/scripts/build.sh >> >> >> Thanks very much for providing these instructions. >> >> It would be great to have a version of the script that used Iceberg to >> load the code and kept the repository (pharo-project/pharo in the >> example above, but normally this would be a fork of the repository). >> This would greatly facilitate creating pull requests with bug fixes. >> >> I'll try and figure out how to modify your script to do this, but if >> you're able to provide a quick answer, or even a hint, it would be much >> appreciated. >> >> Also, the version information doesn't appear to be set here, i.e.: >> >> $ pharo Pharo.image printVersion >> [version] nil.nil #0 >> >> I'll try and figure this out, but if you know, what do I need to do to >> get this set? >> >> Thanks again, >> Alistair >> >> >

June 25, 2017

Re: [Pharo-users] Pharo6 bootstrap how to

by Esteban Lorenzano

Hi! > On 25 Jun 2017, at 10:14, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > You can clone a repository with Iceberg with a script like this: > > target := 'pharo-core' asFileReference ensureCreateDirectory. > repository := IceRepositoryCreator new > remote: (IceRemote url: 'git@github.com:pharo-project/pharo.git'); > location: target; > subdirectory:'src'; > createRepository. > repository backend checkoutBranch: 'development'. > repository register. this is a bit too verbose for my taste :) you can do the same with this (which is more or less the same, btwâ¦ just more compact) repository := IceRepositoryCreator new remote: (IceRemote url: 'git@github.com:pharo-project/pharo.git'); subdirectory:'src'; createRepository. repository checkoutBranch: 'development'. repository register. - no need to violate demeters law by accessing directly to backend - no need to specify a target location because it will put it in default place. :) Esteban > > Setting of the system version is already fixed in Pharo 7. For Pharo 6 you want to do something like this: > > ./pharo Pharo.image eval --save "| updateString | updateString := 'tag.txt' asFileReference readStream contents allButFirst. SystemVersion classPool at: #Current put: (SystemVersion new type: 'Pharo'; major: updateString first asString asInteger; minor: updateString second asString asInteger; highestUpdate: updateString asInteger; suffix: ''; yourself)" > > Where tag.txt can by obtained from git by: > git describe --tags > tag.txt > > Cheers, > -- Pavel > > > > > 2017-06-24 22:06 GMT+02:00 Alistair Grant <akgrant0710(a)gmail.com <mailto:akgrant0710@gmail.com>>: > Hi Pavel, > > On Fri, Jun 23, 2017 at 10:08:29PM +0200, Pavel Krivanek wrote: > > clone the master branch of git@github.com:pharo-project/pharo.git and inside > > this clone do: > > > > export PHARO_VERSION=60 > > export BOOTSTRAP_ARCH=32 > > > > wget -O - get.pharo.org/${PHARO_VERSION}+vm <http://get.pharo.org/$%7BPHARO_VERSION%7D+vm> | bash > > > > ./pharo Pharo.image --no-default-preferences ./bootstrap/scripts/ > > prepare_image.st <http://prepare_image.st/> --save --quit > > ./pharo Pharo.image --no-default-preferences ./bootstrap/scripts/bootstrap.st <http://bootstrap.st/> > > --ARCH=${BOOTSTRAP_ARCH} --quit > > bash ./bootstrap/scripts/build.sh > > > Thanks very much for providing these instructions. > > It would be great to have a version of the script that used Iceberg to > load the code and kept the repository (pharo-project/pharo in the > example above, but normally this would be a fork of the repository). > This would greatly facilitate creating pull requests with bug fixes. > > I'll try and figure out how to modify your script to do this, but if > you're able to provide a quick answer, or even a hint, it would be much > appreciated. > > Also, the version information doesn't appear to be set here, i.e.: > > $ pharo Pharo.image printVersion > [version] nil.nil #0 > > I'll try and figure this out, but if you know, what do I need to do to > get this set? > > Thanks again, > Alistair > >

June 25, 2017

Re: [Pharo-users] Pharo6 bootstrap how to

by Pavel Krivanek

You can clone a repository with Iceberg with a script like this: target := 'pharo-core' asFileReference ensureCreateDirectory. repository := IceRepositoryCreator new remote: (IceRemote url: 'git@github.com:pharo-project/pharo.git'); location: target; subdirectory:'src'; createRepository. repository backend checkoutBranch: 'development'. repository register. Setting of the system version is already fixed in Pharo 7. For Pharo 6 you want to do something like this: ./pharo Pharo.image eval --save "| updateString | updateString := 'tag.txt' asFileReference readStream contents allButFirst. SystemVersion classPool at: #Current put: (SystemVersion new type: 'Pharo'; major: updateString first asString asInteger; minor: updateString second asString asInteger; highestUpdate: updateString asInteger; suffix: ''; yourself)" Where tag.txt can by obtained from git by: git describe --tags > tag.txt Cheers, -- Pavel 2017-06-24 22:06 GMT+02:00 Alistair Grant <akgrant0710(a)gmail.com>: > Hi Pavel, > > On Fri, Jun 23, 2017 at 10:08:29PM +0200, Pavel Krivanek wrote: > > clone the master branch of git@github.com:pharo-project/pharo.git and > inside > > this clone do: > > > > export PHARO_VERSION=60 > > export BOOTSTRAP_ARCH=32 > > > > wget -O - get.pharo.org/${PHARO_VERSION}+vm | bash > > > > ./pharo Pharo.image --no-default-preferences ./bootstrap/scripts/ > > prepare_image.st --save --quit > > ./pharo Pharo.image --no-default-preferences ./bootstrap/scripts/ > bootstrap.st > > --ARCH=${BOOTSTRAP_ARCH} --quit > > bash ./bootstrap/scripts/build.sh > > > Thanks very much for providing these instructions. > > It would be great to have a version of the script that used Iceberg to > load the code and kept the repository (pharo-project/pharo in the > example above, but normally this would be a fork of the repository). > This would greatly facilitate creating pull requests with bug fixes. > > I'll try and figure out how to modify your script to do this, but if > you're able to provide a quick answer, or even a hint, it would be much > appreciated. > > Also, the version information doesn't appear to be set here, i.e.: > > $ pharo Pharo.image printVersion > [version] nil.nil #0 > > I'll try and figure this out, but if you know, what do I need to do to > get this set? > > Thanks again, > Alistair > >

June 25, 2017

Re: [Pharo-users] Pharo6 bootstrap how to

by Pavel Krivanek

Hi Hilaire, I tried to play a little bit with that. As the first step please check that Dr. Geo can be loaded properly into the standard Pharo 6 image with the package Deprecated60 unloaded. The Dr. Geo uses some deprecated calls and this package is not present in the smaller images. Cheers, -- Pavel 2017-06-24 10:29 GMT+02:00 Hilaire <hilaire(a)drgeo.eu>: > Hi Pavel, > > Le 24/06/2017 Ã 09:35, Pavel Krivanek a Ã©crit : > > The question is what is your goal because the bootstrapped image will > > I want to build an image for DrGeo which is not 60MB. (the size I have > now on my P6 dev image for Dr. Geo) > > Until now, DrGeo was installed then unecessary packages removed. With > the first Pharo release, DrGeo image was around 10MB, in the latest > DrGeo release (based on P3), its image is more than 20MB. > > For P6, if possible, I would like to use the bootstrap process > > > have in the end (almost) the same content as the default > > non-bootstrapped image. > > You probably want to change the content of the produced image wich > > requires to modify the related baselines and do not load them all. For > > Dr Geo you will probably want to start with the BaselineOfMorphic > > however you will probably need a lot of custom modifications. > > > I don't know... May be we can take Dr. Geo as an excuse to see step by > step how to do it. If we succeed I could document it so it may be useful > to other. > > > -- > Dr. Geo > http://drgeo.eu > > >

June 25, 2017

Re: [Pharo-users] Pharo6 bootstrap how to

by Alistair Grant

Hi Pavel, On Fri, Jun 23, 2017 at 10:08:29PM +0200, Pavel Krivanek wrote: > clone the master branch of git@github.com:pharo-project/pharo.git and inside > this clone do: > > export PHARO_VERSION=60 > export BOOTSTRAP_ARCH=32 > > wget -O - get.pharo.org/${PHARO_VERSION}+vm | bash > > ./pharo Pharo.image --no-default-preferences ./bootstrap/scripts/ > prepare_image.st --save --quit > ./pharo Pharo.image --no-default-preferences ./bootstrap/scripts/bootstrap.st > --ARCH=${BOOTSTRAP_ARCH} --quit > bash ./bootstrap/scripts/build.sh Thanks very much for providing these instructions. It would be great to have a version of the script that used Iceberg to load the code and kept the repository (pharo-project/pharo in the example above, but normally this would be a fork of the repository). This would greatly facilitate creating pull requests with bug fixes. I'll try and figure out how to modify your script to do this, but if you're able to provide a quick answer, or even a hint, it would be much appreciated. Also, the version information doesn't appear to be set here, i.e.: $ pharo Pharo.image printVersion [version] nil.nil #0 I'll try and figure this out, but if you know, what do I need to do to get this set? Thanks again, Alistair

June 24, 2017