- Pharo-users - lists.pharo.org

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

Re: [Pharo-users] [ANN] success story: surgery appointments digitalised

by andrew glynn

Thanks, it had occurred to me to take a look at the other drivers in Garage - been a bit busy though so might not get to it until tomorrow. Andrew Glynn ________________________________ From: Pierce Ng <pierce(a)samadhiweb.com> Sent: Friday, June 23, 2017 8:19 PM To: Any question about pharo is welcome Subject: Re: [Pharo-users] [ANN] success story: surgery appointments digitalised On Sat, Jun 24, 2017 at 12:48:56AM +0800, Ben Coman wrote: > @anyone, If Andrew can get a proof of concept working, what are the best > frameworks for it to work with? Write the Oracle set-oriented driver according to UDBC convention. Then, write a Glorp ORM driver based on it. The Pharo version of Glorp already has OraclePlatform, which comes from the VW upstream and presumably works, so it can be used as a reference. There's also Garage which also suppors Glorp. All are available in the Catalogue Browser. STH search shows a project named Garage-Oracle by CraigAllen but 'the page does not exist, sadly.' Pierce

June 24, 2017

Re: [Pharo-users] PharoJS

by Stephane Ducasse

Askoh As soon as we will say something somene else will not be happy so I will comment on this. Now let us look at the trajectory: - Pharo is moving super fast - Daily improving - Large set of frameworks - Many companies SHARING bricks (Zinc, Mustache, Mustaside, ... and many many more). So pick up a topic you like or that you think you can make money and just come to have fun with us and doing so you will learn. This way you can also build your future. You see the actions that you do today and that open paths for tomorrow. THERE IS A ***HUGE*** difference between open community and source like Pharo and close source. Pharo is alive, kicking and it will continue. With git support Pharo will make a huge visibility credibility and community sharing step. We have a long list of super cool improvement in the pipe. Just join. Stef On Thu, Jun 22, 2017 at 8:01 PM, askoh <askoh(a)askoh.com> 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 24, 2017

Re: [Pharo-users] [ANN] success story: surgery appointments digitalised

by Stephane Ducasse

Supercool Norbert do you have screenshot for the Pharo success web page ? On Thu, Jun 22, 2017 at 2:40 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > I'm sorry I forgot to post this much earlier. Anywayâ¦. > > We are proud to add another success story to the pharo portfolio > > http://zweidenker.de/en/project/operationstermine-digitalisiert > > It is an operation planning tool for an eye surgery clinic. The core system > is pharo4 and voyage (using mongo). The user interface is done with seaside. > It interfaces with a legacy patient information system, microsoft exchange > and other stuff in order to orchestrate the arrangement of surgery dates. > The tool automates planning (which doctor works on which day and has still > time to do the operation,â¦.). Finalized plans are produced in PDF an printed > by the staff. > > This as a short info. If you have question don't hesitate to ask. > > Implanting more pharo everywhere :) > > Norbert >

June 24, 2017

Re: [Pharo-users] Pharo6 bootstrap how to

by Hilaire

Ok, I executed these statements. It seems to do its jobs just fine, I request for a 64bits architecture. What's next? Thanks Hilaire Le 23/06/2017 Ã 22:08, Pavel Krivanek a Ã©crit : > ./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 > -- Dr. Geo http://drgeo.eu

June 24, 2017