October 2014 - Pharo-users - lists.pharo.org

Pharo program examples

by Hans Schueren

Hello again , let me ask a strange question for a beginner of pharo. Let the system be the system. hahaha " Are there examples of complete , simple programs for Pharo smalltalk 80 ? " Very simple ones for beginners ? A file archieve perhaps or so ? For example : a simple personal database a simple calculation program for any purposes s simple statistic program or so This could help for learning. Hans

Oct. 23, 2014

Pharo program examples

by Hans Schueren

Hello again , let me ask a strange question for a beginner of pharo. Let the system be the system. hahaha " Are there examples of complete , simple programs for Pharo smalltalk 80 ? " Very simple ones for beginners ? A file archieve perhaps or so ? For example : a simple personal database a simple calculation program for any purposes s simple statistic program or so This could help for learning. Hans

Oct. 23, 2014

Re: [Pharo-users] Starting a pool of worker images using command line parameters

by Sven Van Caekenberghe

> On 23 Oct 2014, at 21:54, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > > 2014-10-23 16:08 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >> Nah, you can do it way easier: >> >> $ cat run.st >> NonInteractiveTranscript stdout install. >> >> Transcript show: Smalltalk commandLine arguments; cr. >> >> Smalltalk quitPrimitive. >> >> $ ./pharo Pharo.image run.st 1 2 3 >> #('1' '2' '3') >> >> HTH, > > > Utterly concise. Thanks. > > Why do you use the pharo shell script instead of pharo-vm with > --no-display? Is there any benefit other than having the pwd set to > the image location? And hence, the argument script should be relative > to the image. No particular reason, mostly because I hate adding the --no-display But yes, I usually bypass the script and use the executable directly. > Thanks again, You're welcome. All this sharing, talking & discussing, even over small issues and style is important, we can all learn a lot from each other and save time and money. Sven

Oct. 23, 2014

Re: [Pharo-users] Starting a pool of worker images using command line parameters

by Esteban A. Maringolo

2014-10-23 16:08 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > Nah, you can do it way easier: > > $ cat run.st > NonInteractiveTranscript stdout install. > > Transcript show: Smalltalk commandLine arguments; cr. > > Smalltalk quitPrimitive. > > $ ./pharo Pharo.image run.st 1 2 3 > #('1' '2' '3') > > HTH, Utterly concise. Thanks. Why do you use the pharo shell script instead of pharo-vm with --no-display? Is there any benefit other than having the pwd set to the image location? And hence, the argument script should be relative to the image. Thanks again,

Oct. 23, 2014

Re: [Pharo-users] Starting a pool of worker images using command line parameters

by Sven Van Caekenberghe

> On 23 Oct 2014, at 21:17, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > $ cat startserver.sh > #! /bin/sh > nohup ./pharo Pharo.image eval âno-quit âMyServerStart port: $1â & > > ./startserver 8080 > ./startserver 8081 > ./startserver 8082 > > but is a bitâ¦ âtruchoâ (in plain argentinian)â¦ which means a bad quality hack :P No, I actually like it: it is explicit and simple to understand. Clean. If you think that is a ugly hack, I would not dare to ask what your opinion is of *any* shell script ;-) - and any Unix like system that we trust our daily computing to is full of those ! >> On 23 Oct 2014, at 21:08, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Nah, you can do it way easier: >> >> $ cat run.st >> NonInteractiveTranscript stdout install. >> >> Transcript show: Smalltalk commandLine arguments; cr. >> >> Smalltalk quitPrimitive. >> >> $ ./pharo Pharo.image run.st 1 2 3 >> #('1' '2' '3') >> >> HTH, >> >> Sven >> >>> On 23 Oct 2014, at 20:52, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>> >>> 2014-10-23 15:19 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>> >>>>> On 23 Oct 2014, at 20:16, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>>>> Do I have to define a subclass of STCommandLineHandler? >>>> yes >>> >>> I thought so. >>> >>>>> How can I capture the --port argument? For what I saw, only "boolean" >>>>> parameters can be defined (--quit, --save, etc, without arguments). It >>>>> is, no getopts compatibility. >>>> no ideaâ¦ we can work on thatâ¦ is necessary :) >>> >>> The VM itself has its own command parameters, are the parameters >>> handled and/or passed to the image? If so, how? >>> >>> Regards! >>> >> >> > >

Oct. 23, 2014

Re: [Pharo-users] Starting a pool of worker images using command line parameters

by Esteban Lorenzano

$ cat startserver.sh #! /bin/sh nohup ./pharo Pharo.image eval âno-quit âMyServerStart port: $1â & ./startserver 8080 ./startserver 8081 ./startserver 8082 but is a bitâ¦ âtruchoâ (in plain argentinian)â¦ which means a bad quality hack :P > On 23 Oct 2014, at 21:08, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Nah, you can do it way easier: > > $ cat run.st > NonInteractiveTranscript stdout install. > > Transcript show: Smalltalk commandLine arguments; cr. > > Smalltalk quitPrimitive. > > $ ./pharo Pharo.image run.st 1 2 3 > #('1' '2' '3') > > HTH, > > Sven > >> On 23 Oct 2014, at 20:52, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> >> 2014-10-23 15:19 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>> >>>> On 23 Oct 2014, at 20:16, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>>> Do I have to define a subclass of STCommandLineHandler? >>> yes >> >> I thought so. >> >>>> How can I capture the --port argument? For what I saw, only "boolean" >>>> parameters can be defined (--quit, --save, etc, without arguments). It >>>> is, no getopts compatibility. >>> no ideaâ¦ we can work on thatâ¦ is necessary :) >> >> The VM itself has its own command parameters, are the parameters >> handled and/or passed to the image? If so, how? >> >> Regards! >> > >

Oct. 23, 2014

Re: [Pharo-users] Starting a pool of worker images using command line parameters

by Damien Cassou

On Thu, Oct 23, 2014 at 8:16 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > How can I capture the --port argument? For what I saw, only "boolean" > parameters can be defined (--quit, --save, etc, without arguments). It > is, no getopts compatibility. no; it is possible to define parameters like --to=html as we do in Pillar. Take a Pillar image from Jenkins and look at the source code. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Oct. 23, 2014

Re: [Pharo-users] Starting a pool of worker images using command line parameters

by Sven Van Caekenberghe

Nah, you can do it way easier: $ cat run.st NonInteractiveTranscript stdout install. Transcript show: Smalltalk commandLine arguments; cr. Smalltalk quitPrimitive. $ ./pharo Pharo.image run.st 1 2 3 #('1' '2' '3') HTH, Sven > On 23 Oct 2014, at 20:52, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > > 2014-10-23 15:19 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> On 23 Oct 2014, at 20:16, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>> Do I have to define a subclass of STCommandLineHandler? >> yes > > I thought so. > >>> How can I capture the --port argument? For what I saw, only "boolean" >>> parameters can be defined (--quit, --save, etc, without arguments). It >>> is, no getopts compatibility. >> no ideaâ¦ we can work on thatâ¦ is necessary :) > > The VM itself has its own command parameters, are the parameters > handled and/or passed to the image? If so, how? > > Regards! >

Oct. 23, 2014

Re: [Pharo-users] Starting a pool of worker images using command line parameters

by Esteban A. Maringolo

2014-10-23 15:19 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> On 23 Oct 2014, at 20:16, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> Do I have to define a subclass of STCommandLineHandler? > yes I thought so. >> How can I capture the --port argument? For what I saw, only "boolean" >> parameters can be defined (--quit, --save, etc, without arguments). It >> is, no getopts compatibility. > no ideaâ¦ we can work on thatâ¦ is necessary :) The VM itself has its own command parameters, are the parameters handled and/or passed to the image? If so, how? Regards!

Oct. 23, 2014

Re: [Pharo-users] Starting a pool of worker images using command line parameters

by Esteban Lorenzano

> On 23 Oct 2014, at 20:16, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > > tl;dr version: > > I'd like to be able to do something like > > $PATH/app/pharo-vm/pharo --nodisplay app.image st setup-worker.st --port 8091 > and: > $PATH/app/pharo-vm/pharo --nodisplay app.image st setup-worker.st --port 8092 > etc. > > Do I have to define a subclass of STCommandLineHandler? yes > > How can I capture the --port argument? For what I saw, only "boolean" > parameters can be defined (--quit, --save, etc, without arguments). It > is, no getopts compatibility. no ideaâ¦ we can work on thatâ¦ is necessary :) Esteban > > > Long version: > For my apps I have a pool of worker images with Zinc+Seaside behind an > nginx proxy. > > Each "upstream" (aka "worker") server, is started by supervisord, > using a separate startup smalltalk script, where the only thing I > change is the port of ZnZincServerAdaptor to start on a different > port. The rest is identical. > > The startup is something like: > $PATH/app/pharo-vm/pharo --nodisplay app.image st setup-worker1.st > and for worker2: > $PATH/app/pharo-vm/pharo --nodisplay app.image st setup-worker2.st > and for worker3: > $PATH/app/pharo-vm/pharo --nodisplay app.image st setup-worker3.st > etc. > > Is there a better way to perform this without having to copy > setup-worker1.st to setup-workerN.st for each worker image? > > How do you manage this? > > Regards, > > Esteban A. Maringolo >

Oct. 23, 2014