January 2016 - Pharo-users - lists.pharo.org

Re: [Pharo-users] CommandLineHandler surprises

by Esteban Lorenzano

> On 27 Jan 2016, at 23:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> >> On 27 Jan 2016, at 22:56, Jimmie Houchin <jlhouchin(a)gmail.com> wrote: >> >> Yes, I did not express myself well. What I am meaning is that I do not expect to have a UI window for the image pop-up. But it does, every time. >> >> The difference that I can find is that I have been downloading VMs from >> http://files.pharo.org/vm/pharo-spur32/linux/ >> >> These VMs have only a "pharo" and not a "pharo-ui". So ./pharo always opens an image in a UI window. >> >> When I do >> wget -O- get.pharo.org/stable+vm | bash >> >> Then it generates a pharo and a pharo-ui script. >> >> This is probably the problem that I am having is that the manual downloads from the website are not like the zeroconf scripts and so there are no explicit UI and Headless scripts. >> >> These zeroconf VMs with their differing scripts do exactly as advertised. Are the generated scripts different for different Linux distros? Is there a reason for the zipped downloads on the website to not include them? > > They are not that different. The 'secret' is the --nodisplay VM option, that's all. If you know what you are doing, there is actually something to say for not using the .sh wrapper scripts. > >> I tried the "get" handler and had it install XMLParser. Very nice. > > Good ! yes, the âgetâ command is one of the lastest cool additions (not because I added it ;) ) but the capability of express ./pharo Pharo.image get Seaside3 (for example) is very convenient :) Esteban > > Yes, once it works this is all very slick. > >> Thanks and Shalom Aleichem. >> >> Jimmie >> >> >> >> >> >> On 01/27/2016 01:21 PM, Sven Van Caekenberghe wrote: >>> Jimmie, >>> >>> Of course it opens an image, else nothing would work ;-) >>> I suspect you mean it opens a UI ? >>> That should not happen, it depends on what your ./pharo actually is or does. >>> In any case, rest assured, using it on the command line works perfectly. >>> >>> On the first Linux server that I log in to: >>> >>> $ cat ~/pharo/bin/pharo >>> #!/usr/bin/env bash >>> # some magic to find out the real location of this script dealing with symlinks >>> DIR=`readlink "$0"` || DIR="$0"; >>> DIR=`dirname "$DIR"`; >>> cd "$DIR" >>> DIR=`pwd` >>> cd - > /dev/null >>> # disable parameter expansion to forward all arguments unprocessed to the VM >>> set -f >>> # run the VM and pass along all arguments as is >>> "$DIR"/"pharo-vm/pharo" --nodisplay "$@" >>> >>> $ ~/pharo/bin/pharo ~/pharo/build/Pharo.image --list >>> Currently installed Command Line Handlers: >>> Fuel Loads fuel files >>> config Install and inspect Metacello Configurations from the command line >>> save Rename the image and changes file >>> update Load updates >>> printVersion Print image version >>> st Loads and executes .st source files >>> test A command line test runner >>> clean Run image cleanup >>> eval Directly evaluates passed in one line scripts >>> >>> $ ~/pharo/bin/pharo ~/pharo/build/Pharo.image eval '123 factorial' >>> 12146304367025329675766243241881295855454217088483382315328918161829235892362167668831156960612640202170735835221294047782591091570411651472186029519906261646730733907419814952960000000000000000000000000000 >>> >>> >>> HTH >>> >>> Sven >>> >>>> On 27 Jan 2016, at 19:59, Jimmie Houchin <jlhouchin(a)gmail.com> wrote: >>>> >>>> Hello, >>>> >>>> I am reading the Deep Into Pharo book. I have been playing with the CommandLineHandler. I have been surprised by some of its behavior. Though I have used Pharo a long time. I have not played with it from the command line. I am a very long time Linux user and am very comfortable on the command line. >>>> >>>> When according to the book I execute: >>>> >>>> ./pharo Pharo.image --list >>>> >>>> It will provide me with a list of the available handlers. >>>> >>>> I did not expect it to open up an image for me. That is not what I expected or wanted. I did not intend to use an image at this time. I am on the command line and expecting to see results there. Not for a new window to pop up. >>>> >>>> As of yet I have always opened up Pharo on the command line. I have yet to use PharoLauncher, but do intend to do so soon. So I am comfortable with Pharo opening up a new window and image from the command line. >>>> >>>> However it is very unintuitive and seemingly unnecessary to open up an image for these command line handlers. I naively think they should simply return the results. Now if that requires opening a headless image for a moment and close, then fine. >>>> >>>> --list >>>> --help >>>> --version >>>> --copyright >>>> eval >>>> printVersion >>>> >>>> Some other handlers I do not know if opening an image is the correct default. I have not spent the time learning them yet. >>>> >>>> Thanks. Shalom Aleichem. >>>> >>>> Jimmie

Jan. 27, 2016

Re: [Pharo-users] CommandLineHandler surprises

by Sven Van Caekenberghe

> On 27 Jan 2016, at 22:56, Jimmie Houchin <jlhouchin(a)gmail.com> wrote: > > Yes, I did not express myself well. What I am meaning is that I do not expect to have a UI window for the image pop-up. But it does, every time. > > The difference that I can find is that I have been downloading VMs from > http://files.pharo.org/vm/pharo-spur32/linux/ > > These VMs have only a "pharo" and not a "pharo-ui". So ./pharo always opens an image in a UI window. > > When I do > wget -O- get.pharo.org/stable+vm | bash > > Then it generates a pharo and a pharo-ui script. > > This is probably the problem that I am having is that the manual downloads from the website are not like the zeroconf scripts and so there are no explicit UI and Headless scripts. > > These zeroconf VMs with their differing scripts do exactly as advertised. Are the generated scripts different for different Linux distros? Is there a reason for the zipped downloads on the website to not include them? They are not that different. The 'secret' is the --nodisplay VM option, that's all. If you know what you are doing, there is actually something to say for not using the .sh wrapper scripts. > I tried the "get" handler and had it install XMLParser. Very nice. Good ! Yes, once it works this is all very slick. > Thanks and Shalom Aleichem. > > Jimmie > > > > > > On 01/27/2016 01:21 PM, Sven Van Caekenberghe wrote: >> Jimmie, >> >> Of course it opens an image, else nothing would work ;-) >> I suspect you mean it opens a UI ? >> That should not happen, it depends on what your ./pharo actually is or does. >> In any case, rest assured, using it on the command line works perfectly. >> >> On the first Linux server that I log in to: >> >> $ cat ~/pharo/bin/pharo >> #!/usr/bin/env bash >> # some magic to find out the real location of this script dealing with symlinks >> DIR=`readlink "$0"` || DIR="$0"; >> DIR=`dirname "$DIR"`; >> cd "$DIR" >> DIR=`pwd` >> cd - > /dev/null >> # disable parameter expansion to forward all arguments unprocessed to the VM >> set -f >> # run the VM and pass along all arguments as is >> "$DIR"/"pharo-vm/pharo" --nodisplay "$@" >> >> $ ~/pharo/bin/pharo ~/pharo/build/Pharo.image --list >> Currently installed Command Line Handlers: >> Fuel Loads fuel files >> config Install and inspect Metacello Configurations from the command line >> save Rename the image and changes file >> update Load updates >> printVersion Print image version >> st Loads and executes .st source files >> test A command line test runner >> clean Run image cleanup >> eval Directly evaluates passed in one line scripts >> >> $ ~/pharo/bin/pharo ~/pharo/build/Pharo.image eval '123 factorial' >> 12146304367025329675766243241881295855454217088483382315328918161829235892362167668831156960612640202170735835221294047782591091570411651472186029519906261646730733907419814952960000000000000000000000000000 >> >> >> HTH >> >> Sven >> >>> On 27 Jan 2016, at 19:59, Jimmie Houchin <jlhouchin(a)gmail.com> wrote: >>> >>> Hello, >>> >>> I am reading the Deep Into Pharo book. I have been playing with the CommandLineHandler. I have been surprised by some of its behavior. Though I have used Pharo a long time. I have not played with it from the command line. I am a very long time Linux user and am very comfortable on the command line. >>> >>> When according to the book I execute: >>> >>> ./pharo Pharo.image --list >>> >>> It will provide me with a list of the available handlers. >>> >>> I did not expect it to open up an image for me. That is not what I expected or wanted. I did not intend to use an image at this time. I am on the command line and expecting to see results there. Not for a new window to pop up. >>> >>> As of yet I have always opened up Pharo on the command line. I have yet to use PharoLauncher, but do intend to do so soon. So I am comfortable with Pharo opening up a new window and image from the command line. >>> >>> However it is very unintuitive and seemingly unnecessary to open up an image for these command line handlers. I naively think they should simply return the results. Now if that requires opening a headless image for a moment and close, then fine. >>> >>> --list >>> --help >>> --version >>> --copyright >>> eval >>> printVersion >>> >>> Some other handlers I do not know if opening an image is the correct default. I have not spent the time learning them yet. >>> >>> Thanks. Shalom Aleichem. >>> >>> Jimmie >>> >> > >

Jan. 27, 2016

Re: [Pharo-users] CommandLineHandler surprises

by Jimmie Houchin

Yes, I did not express myself well. What I am meaning is that I do not expect to have a UI window for the image pop-up. But it does, every time. The difference that I can find is that I have been downloading VMs from http://files.pharo.org/vm/pharo-spur32/linux/ These VMs have only a "pharo" and not a "pharo-ui". So ./pharo always opens an image in a UI window. When I do wget -O- get.pharo.org/stable+vm | bash Then it generates a pharo and a pharo-ui script. This is probably the problem that I am having is that the manual downloads from the website are not like the zeroconf scripts and so there are no explicit UI and Headless scripts. These zeroconf VMs with their differing scripts do exactly as advertised. Are the generated scripts different for different Linux distros? Is there a reason for the zipped downloads on the website to not include them? I tried the "get" handler and had it install XMLParser. Very nice. Thanks and Shalom Aleichem. Jimmie On 01/27/2016 01:21 PM, Sven Van Caekenberghe wrote: > Jimmie, > > Of course it opens an image, else nothing would work ;-) > I suspect you mean it opens a UI ? > That should not happen, it depends on what your ./pharo actually is or does. > In any case, rest assured, using it on the command line works perfectly. > > On the first Linux server that I log in to: > > $ cat ~/pharo/bin/pharo > #!/usr/bin/env bash > # some magic to find out the real location of this script dealing with symlinks > DIR=`readlink "$0"` || DIR="$0"; > DIR=`dirname "$DIR"`; > cd "$DIR" > DIR=`pwd` > cd - > /dev/null > # disable parameter expansion to forward all arguments unprocessed to the VM > set -f > # run the VM and pass along all arguments as is > "$DIR"/"pharo-vm/pharo" --nodisplay "$@" > > $ ~/pharo/bin/pharo ~/pharo/build/Pharo.image --list > Currently installed Command Line Handlers: > Fuel Loads fuel files > config Install and inspect Metacello Configurations from the command line > save Rename the image and changes file > update Load updates > printVersion Print image version > st Loads and executes .st source files > test A command line test runner > clean Run image cleanup > eval Directly evaluates passed in one line scripts > > $ ~/pharo/bin/pharo ~/pharo/build/Pharo.image eval '123 factorial' > 12146304367025329675766243241881295855454217088483382315328918161829235892362167668831156960612640202170735835221294047782591091570411651472186029519906261646730733907419814952960000000000000000000000000000 > > > HTH > > Sven > >> On 27 Jan 2016, at 19:59, Jimmie Houchin <jlhouchin(a)gmail.com> wrote: >> >> Hello, >> >> I am reading the Deep Into Pharo book. I have been playing with the CommandLineHandler. I have been surprised by some of its behavior. Though I have used Pharo a long time. I have not played with it from the command line. I am a very long time Linux user and am very comfortable on the command line. >> >> When according to the book I execute: >> >> ./pharo Pharo.image --list >> >> It will provide me with a list of the available handlers. >> >> I did not expect it to open up an image for me. That is not what I expected or wanted. I did not intend to use an image at this time. I am on the command line and expecting to see results there. Not for a new window to pop up. >> >> As of yet I have always opened up Pharo on the command line. I have yet to use PharoLauncher, but do intend to do so soon. So I am comfortable with Pharo opening up a new window and image from the command line. >> >> However it is very unintuitive and seemingly unnecessary to open up an image for these command line handlers. I naively think they should simply return the results. Now if that requires opening a headless image for a moment and close, then fine. >> >> --list >> --help >> --version >> --copyright >> eval >> printVersion >> >> Some other handlers I do not know if opening an image is the correct default. I have not spent the time learning them yet. >> >> Thanks. Shalom Aleichem. >> >> Jimmie >> >

Jan. 27, 2016

Re: [Pharo-users] mini Actor model in two classes and

by Norbert Hartl

Super simple implementation. I made Andrew Blacks Erlang example run on pharo a while ago if you are interested. http://smalltalkhub.com/#!/~NorbertHartl/Erlang Keep us posted what you learn so we can, too ;) Norbert > Am 27.01.2016 um 21:53 schrieb stepharo <stepharo(a)free.fr>: > > Hi > > Since long time I wanted to have fun building a mini actor model. > So I did one and I attached the skeleton of a future chapter for FunWithPharo :) > > Now I will read about futures and the rest. > > may be there is a problem with the compiling behavior. > (see thread learningObject) > > Stef > > <Actalk.pdf>

Jan. 27, 2016

Re: [Pharo-users] mini Actor model in two classes and

by Esteban A. Maringolo

2016-01-27 17:53 GMT-03:00 stepharo <stepharo(a)free.fr>: > Hi > > Since long time I wanted to have fun building a mini actor model. > So I did one and I attached the skeleton of a future chapter for > FunWithPharo :) Cool! How did you find working with ProtoObject with the current tools (inspector/debugger/etc.)? Regards! Esteban A. Maringolo

Jan. 27, 2016

mini Actor model in two classes and

by stepharo

Hi Since long time I wanted to have fun building a mini actor model. So I did one and I attached the skeleton of a future chapter for FunWithPharo :) Now I will read about futures and the rest. may be there is a problem with the compiling behavior. (see thread learningObject) Stef

Jan. 27, 2016

Re: [Pharo-users] CommandLineHandler surprises

by Sven Van Caekenberghe

Jimmie, Of course it opens an image, else nothing would work ;-) I suspect you mean it opens a UI ? That should not happen, it depends on what your ./pharo actually is or does. In any case, rest assured, using it on the command line works perfectly. On the first Linux server that I log in to: $ cat ~/pharo/bin/pharo #!/usr/bin/env bash # some magic to find out the real location of this script dealing with symlinks DIR=`readlink "$0"` || DIR="$0"; DIR=`dirname "$DIR"`; cd "$DIR" DIR=`pwd` cd - > /dev/null # disable parameter expansion to forward all arguments unprocessed to the VM set -f # run the VM and pass along all arguments as is "$DIR"/"pharo-vm/pharo" --nodisplay "$@" $ ~/pharo/bin/pharo ~/pharo/build/Pharo.image --list Currently installed Command Line Handlers: Fuel Loads fuel files config Install and inspect Metacello Configurations from the command line save Rename the image and changes file update Load updates printVersion Print image version st Loads and executes .st source files test A command line test runner clean Run image cleanup eval Directly evaluates passed in one line scripts $ ~/pharo/bin/pharo ~/pharo/build/Pharo.image eval '123 factorial' 12146304367025329675766243241881295855454217088483382315328918161829235892362167668831156960612640202170735835221294047782591091570411651472186029519906261646730733907419814952960000000000000000000000000000 HTH Sven > On 27 Jan 2016, at 19:59, Jimmie Houchin <jlhouchin(a)gmail.com> wrote: > > Hello, > > I am reading the Deep Into Pharo book. I have been playing with the CommandLineHandler. I have been surprised by some of its behavior. Though I have used Pharo a long time. I have not played with it from the command line. I am a very long time Linux user and am very comfortable on the command line. > > When according to the book I execute: > > ./pharo Pharo.image --list > > It will provide me with a list of the available handlers. > > I did not expect it to open up an image for me. That is not what I expected or wanted. I did not intend to use an image at this time. I am on the command line and expecting to see results there. Not for a new window to pop up. > > As of yet I have always opened up Pharo on the command line. I have yet to use PharoLauncher, but do intend to do so soon. So I am comfortable with Pharo opening up a new window and image from the command line. > > However it is very unintuitive and seemingly unnecessary to open up an image for these command line handlers. I naively think they should simply return the results. Now if that requires opening a headless image for a moment and close, then fine. > > --list > --help > --version > --copyright > eval > printVersion > > Some other handlers I do not know if opening an image is the correct default. I have not spent the time learning them yet. > > Thanks. Shalom Aleichem. > > Jimmie >

Jan. 27, 2016

CommandLineHandler surprises

by Jimmie Houchin

Hello, I am reading the Deep Into Pharo book. I have been playing with the CommandLineHandler. I have been surprised by some of its behavior. Though I have used Pharo a long time. I have not played with it from the command line. I am a very long time Linux user and am very comfortable on the command line. When according to the book I execute: ./pharo Pharo.image --list It will provide me with a list of the available handlers. I did not expect it to open up an image for me. That is not what I expected or wanted. I did not intend to use an image at this time. I am on the command line and expecting to see results there. Not for a new window to pop up. As of yet I have always opened up Pharo on the command line. I have yet to use PharoLauncher, but do intend to do so soon. So I am comfortable with Pharo opening up a new window and image from the command line. However it is very unintuitive and seemingly unnecessary to open up an image for these command line handlers. I naively think they should simply return the results. Now if that requires opening a headless image for a moment and close, then fine. --list --help --version --copyright eval printVersion Some other handlers I do not know if opening an image is the correct default. I have not spent the time learning them yet. Thanks. Shalom Aleichem. Jimmie

Jan. 27, 2016

Re: [Pharo-users] Some Spotter Questions

by Tudor Girba

Hi, > On Jan 27, 2016, at 4:54 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > I managed to add a spotter extension and preview, but I still have some questions. Thank you! Can you describe the extension? > Is there some global top level overview documentation about writing Spotter extensions ? Only some blog posts: https://www.google.com/search?client=safari&rls=en&q=site:humane-assessment… Writing a help is in progress. It would be very useful to drive it through your questions. > Is the only way to add a 'global/first' search extension by adding a method to class GTSpotter itself ? Yes. > I don't see any other package do that (in a modular way), it feels a bit wrong compared to how modular the GT inspector is. It is exactly the same design as the inspector. Every step in Spotter has an object as an input (like the inspector), and the first object when opening Spotter is an instance of GTSpotter. > Is there a way to reuse a GT inspector view as a preview ? I tried that but it did not work, but what I copied over was 99% identical. Not yet. The problem is the missing 1% :) > Can you have tabs (multiple pages) in the preview ? Not for now. At the moment, you can have multiple previews, and only the first one will be displayed. > Is it possible to control on what tab an inspector opens when a matching item is clicked (like to maintain the same view as the preview) ? No. > What are some best practices for the order, exact matches, fast searching, etc â¦ ? Not much. The best practice is to simply watch the usage, and try to accommodate the best way :). > Is it possible to search in multiple ways (multiple properties), not just collection -> itemName -> GTFilterSubstring ? (Say I want to search all fields of an address object). Of course. Take a look at the GTFilter hierarchy, and you can just write your own. > Searching for Color by name, or by RGB and other representations would seem like a good tutorial example (for me). I am not sure I understand, but it sounds intriguing and I am looking for a case that we can use for a tutorial. Could you elaborate? Perhaps we can write this together. Cheers, Doru > Thx, > > Sven -- www.tudorgirba.com www.feenk.com "Don't give to get. Just give."

Jan. 27, 2016

Some Spotter Questions

by Sven Van Caekenberghe

Hi, I managed to add a spotter extension and preview, but I still have some questions. Is there some global top level overview documentation about writing Spotter extensions ? Is the only way to add a 'global/first' search extension by adding a method to class GTSpotter itself ? I don't see any other package do that (in a modular way), it feels a bit wrong compared to how modular the GT inspector is. Is there a way to reuse a GT inspector view as a preview ? I tried that but it did not work, but what I copied over was 99% identical. Can you have tabs (multiple pages) in the preview ? Is it possible to control on what tab an inspector opens when a matching item is clicked (like to maintain the same view as the preview) ? What are some best practices for the order, exact matches, fast searching, etc ... ? Is it possible to search in multiple ways (multiple properties), not just collection -> itemName -> GTFilterSubstring ? (Say I want to search all fields of an address object). Searching for Color by name, or by RGB and other representations would seem like a good tutorial example (for me). Thx, Sven

Jan. 27, 2016