- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] spotter: top search for senders and references

by stepharo

Le 19/1/16 17:46, stepharo a Ã©crit : > You see I complained a lot about Spotter but I do not care about the > order. > I care that I can use it and be told how to use it. > As a newbie programmer I want to get the feel of going fast. I do not > want that > after the 1 hour of Pharo I'm told that I can look inside the > implementation to discover something. > First I need a system that shows me what I can do then when I get > fluent in Pharo I can > start to think about looking inside. > > Stef the poor guy that is writing documentation for dummies. > > PS: I want to program with my 15 y old son and that he can program by > himself not me doing > magic incantation. > > >> >>> On 19 Jan 2016, at 15:23, Esteban A. Maringolo <emaringolo(a)gmail.com >>> <mailto:emaringolo@gmail.com>> wrote: >>> >>> It turns the search field into a "kind of" command line interface, >>> with #sen/#ref as commands. >>> I love CLIs so I welcome it, but I think It "perverts" the search >>> field and uses an awkward syntax. I prefer to type "senders" than to >>> type a special character like #. >>> >>> I would prefer adding a suffix command so you search for 'do: >>> senders' or 'do: implementorsâ. >> >> just that there is no syntactical way to know when you want senders >> or just retrieve methods who start with do: and continue with keyword >> senâ¦ etc. >> thatâs the reason from the hashtag (which is now a common symbol to >> filter/tag like in twitter/facebook/etc.) >> >> cheers, >> Esteban >> >>> >>> Regards! >>> >>> >>> Esteban A. Maringolo >>> >>> 2016-01-19 10:43 GMT-03:00 Tudor Girba <tudor(a)tudorgirba.com>: >>> >>> Hi, >>> >>> With the latest GT integration, we also integrated the search >>> for senders and references from the first step. >>> >>> Here is a detailed explanation about it, including what we still >>> want to do, how itâs done, and how to discover what else is around: >>> http://www.humane-assessment.com/blog/spotting-senders-references-with-gtsp… >>> >>> <spotter-senders.png> >>> >>> Please let us know what you think. >>> >>> Cheers, >>> Doru >>> >>> >>> -- >>> www.tudorgirba.com <http://www.tudorgirba.com/> >>> www.feenk.com <http://www.feenk.com/> >>> >>> "Problem solving efficiency grows with the abstractness level of >>> problem understanding." >>> >>> >> >

Jan. 19, 2016

Re: [Pharo-dev] Cmd + click

by Yuriy Tymchuk

Sorry, Iâve tried again and it works. I donât know what happenedâ¦ Maybe something else was registering the event, or some other magic. I was using 50522. Cheers. Uko > On 19 Jan 2016, at 17:39, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> >> On 19 Jan 2016, at 17:31, stepharo <stepharo(a)free.fr> wrote: >> >> >> 2016-01-19 15:37 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: >> Hi, there was a future that "cmd + click" browsed classes or showed implementors. Now it doesnât seem to work at least in Nautilus. >> >> Is anyone aware of this? >> >> platform and image version? >> >> It works on Windows pharo 50529: >> alt+right click -> browse Class/implementors of >> alt+shift+right click -> users of class /senders of >> >>> Cmd (Apple) key + (Shift) + Click works fine on OS X in #50535 >> >> Sven do you get implementors and senders working because I get refs and class def but not the method counterparts. > > I just tried in a fresh 50 image, and they all work fine. (I seem to remember differently, maybe from 40). > >> Stef >>> >>>> Cheers. >>>> Uko

Jan. 19, 2016

Re: [Pharo-dev] [ANN] Pharo bootstrap

by stepharo

Oh yes! You cannot imagine all the cleanings that (we they are doing behind your back :) A bootstrap is really a kick in the ass to produce a much much better system. Thanks you guys for making my dream becoming true. Stef Le 19/1/16 16:05, phil(a)highoctane.be a Ã©crit : > Keep up the good work, this is a huge step in making the whole thing a > crystal clear box! > > Phil > > On Tue, Jan 19, 2016 at 3:29 PM, Christophe Demarey > <christophe.demarey(a)inria.fr <mailto:christophe.demarey@inria.fr>> wrote: > > Hi all, > > In case you do not know, we work on bootstrapping Pharo, i.e. > create a Pharo image from sources, not based on a previous image > (well, we use a pharo image to produce it but no code / state from > it). > > This process will allow to define a minimal Pharo kernel > (currently 52 packages but we could have it far smaller) and to > modularize the whole image (currently packages have too much > dependencies on packages already loaded into the image). > The bootstrap process also allows to write down the recipe to > initialize a new image from scratch (some code is missing in the > image or is wrong). In addition, I think we will clean a lot of > historical objects that are not used anymore. > > With the amazing work done by Guillermo Polito during his Phd > (around Espell, Oz): > https://guillep.github.io/files/publications/Poli15Thesis.pdf, *we > succeeded to get a first prototype of a bootstraped Pharo 5 image > (from 5.392)*. > This prototype is able to run an eval command line handler and to > log output / errors. Not all classes are yet initialized and you > cannot yet save / restart this image but it is a big step forward. > It is a 4 mb image (could be half the size without unicode data). > You can download it at: > http://chercheurs.lille.inria.fr/~demarey/pmwiki/pub/pharo-bootstrap/pharo-… > <http://chercheurs.lille.inria.fr/%7Edemarey/pmwiki/pub/pharo-bootstrap/phar…>. > > Next steps are to have a bootstrapped image fully working, then to > load packages on top of it (like network, sunit) to produce a > minimal image. > Then, we need to implement an Oz VM on top of Spur. > After that, we need to work on a reliable way to build the > bootstrap (not too sensitive to changes in the image). > > Christophe. > > ------- > demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ > ../pharo bootstrap.image --no-default-preferences eval "1 + 1" > 2 > demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ > ../pharo bootstrap.image --no-default-preferences eval "'a' , 'b'" > 'ab' > demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ > ../pharo bootstrap.image --no-default-preferences eval "1 / 0" > ZeroDivide > SmallInteger>>/ > UndefinedObject>>DoIt > OpalCompiler>>evaluate > OpalCompiler(AbstractCompiler)>>evaluate: > SmalltalkImage>>evaluate: > > EvaluateCommandLineHandler>>no (source is Undeclared) > no source in EvaluateCommandLineHandler>>evaluate: in Block: no source > BlockClosure>>on:do: > EvaluateCommandLineHandler>>evaluate: > EvaluateCommandLineHandler>>evaluateArguments > EvaluateCommandLineHandler>>activate > EvaluateCommandLineHandler class(CommandLineHandler > class)>>activateWith: > > BasicCommandLineHandler>>no (source is Undeclared) > no source in > PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: > in Block: no source > BlockClosure>>on:do: > PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: > PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand > PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument: > > BasicCommandLineHandler>>no (source is Undeclared) > no source in > PharoCommandLineHandler(BasicCommandLineHandler)>>activate in > Block: no source > BlockClosure>>on:do: > PharoCommandLineHandler(BasicCommandLineHandler)>>activate > PharoCommandLineHandler>>activate > PharoCommandLineHandler class(CommandLineHandler class)>>activateWith: > > PharoCommandLineHandler class>>no (source is Undeclared) > no source in PharoCommandLineHandler class>>activateWith: in > Block: no source > NonInteractiveUIManager(UIManager)>>defer: > PharoCommandLineHandler class>>activateWith: > no source in BasicCommandLineHandler>>activateSubCommand: in > Block: no source > BlockClosure>>on:do: > BasicCommandLineHandler>>activateSubCommand: > BasicCommandLineHandler>>handleSubcommand > BasicCommandLineHandler>>handleArgument: > no source in BasicCommandLineHandler>>activate in Block: no source > > SmallInteger>>no (source is Undeclared) > > UndefinedObject>>no (source is Undeclared) > > AbstractCompiler>>no (source is Undeclared) > > SmalltalkImage>>no (source is Undeclared) > > BlockClosure>>no (source is Undeclared) > > EvaluateCommandLineHandler>>no (source is Undeclared) > > EvaluateCommandLineHandler>>no (source is Undeclared) > > CommandLineHandler class>>no (source is Undeclared) > > BasicCommandLineHandler>>no (source is Undeclared) > > BasicCommandLineHandler>>no (source is Undeclared) > > PharoCommandLineHandler>>no (source is Undeclared) > > UIManager>>no (source is Undeclared) > > UndefinedObject>>no (source is Undeclared) > > CommandLineUIManager>>no (source is Undeclared) > > SmalltalkImage>>no (source is Undeclared) > > DelayMicrosecondScheduler>>no (source is Undeclared) > > BlockClosure>>no (source is Undeclared) > > SmalltalkImage>>no (source is Undeclared) > > WeakArray class>>no (source is Undeclared) > > > ps: source cannot be displayed because there is no formatter > available in the bootstrap > >

Jan. 19, 2016

Re: [Pharo-dev] Cmd + click

by Sven Van Caekenberghe

> On 19 Jan 2016, at 17:31, stepharo <stepharo(a)free.fr> wrote: > > > 2016-01-19 15:37 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Hi, there was a future that "cmd + click" browsed classes or showed implementors. Now it doesnât seem to work at least in Nautilus. > > Is anyone aware of this? > > platform and image version? > > It works on Windows pharo 50529: > alt+right click -> browse Class/implementors of > alt+shift+right click -> users of class /senders of > >> Cmd (Apple) key + (Shift) + Click works fine on OS X in #50535 > > Sven do you get implementors and senders working because I get refs and class def but not the method counterparts. I just tried in a fresh 50 image, and they all work fine. (I seem to remember differently, maybe from 40). > Stef >> >>> Cheers. >>> Uko

Jan. 19, 2016

Re: [Pharo-dev] [ANN] Pharo bootstrap

by Ben Coman

On Tue, Jan 19, 2016 at 10:29 PM, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > Hi all, > > In case you do not know, we work on bootstrapping Pharo, i.e. create a Pharo > image from sources, not based on a previous image (well, we use a pharo > image to produce it but no code / state from it). > > This process will allow to define a minimal Pharo kernel (currently 52 > packages but we could have it far smaller) and to modularize the whole image > (currently packages have too much dependencies on packages already loaded > into the image). > The bootstrap process also allows to write down the recipe to initialize a > new image from scratch (some code is missing in the image or is wrong). In > addition, I think we will clean a lot of historical objects that are not > used anymore. > > With the amazing work done by Guillermo Polito during his Phd (around > Espell, Oz): https://guillep.github.io/files/publications/Poli15Thesis.pdf, > we succeeded to get a first prototype of a bootstraped Pharo 5 image (from > 5.392). > This prototype is able to run an eval command line handler and to log output > / errors. Not all classes are yet initialized and you cannot yet save / > restart this image but it is a big step forward. > It is a 4 mb image (could be half the size without unicode data). You can > download it at: > http://chercheurs.lille.inria.fr/~demarey/pmwiki/pub/pharo-bootstrap/pharo-…. > > Next steps are to have a bootstrapped image fully working, then to load > packages on top of it (like network, sunit) to produce a minimal image. > Then, we need to implement an Oz VM on top of Spur. > After that, we need to work on a reliable way to build the bootstrap (not > too sensitive to changes in the image). Great work guys. Now what stops me feeling compelled to really look deep into this is having a class browser / senders / implementers interface. I guess this is what Oz would facilitate for peeking into the bootstrap image from another image ?? cheers -ben > > Christophe. > > ------- > demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo > bootstrap.image --no-default-preferences eval "1 + 1" > 2 > demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo > bootstrap.image --no-default-preferences eval "'a' , 'b'" > 'ab' > demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ ../pharo > bootstrap.image --no-default-preferences eval "1 / 0" > ZeroDivide > SmallInteger>>/ > UndefinedObject>>DoIt > OpalCompiler>>evaluate > OpalCompiler(AbstractCompiler)>>evaluate: > SmalltalkImage>>evaluate: > > EvaluateCommandLineHandler>>no (source is Undeclared) > no source in EvaluateCommandLineHandler>>evaluate: in Block: no source > BlockClosure>>on:do: > EvaluateCommandLineHandler>>evaluate: > EvaluateCommandLineHandler>>evaluateArguments > EvaluateCommandLineHandler>>activate > EvaluateCommandLineHandler class(CommandLineHandler class)>>activateWith: > > BasicCommandLineHandler>>no (source is Undeclared) > no source in > PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in > Block: no source > BlockClosure>>on:do: > PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: > PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand > PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument: > > BasicCommandLineHandler>>no (source is Undeclared) > no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activate in > Block: no source > BlockClosure>>on:do: > PharoCommandLineHandler(BasicCommandLineHandler)>>activate > PharoCommandLineHandler>>activate > PharoCommandLineHandler class(CommandLineHandler class)>>activateWith: > > PharoCommandLineHandler class>>no (source is Undeclared) > no source in PharoCommandLineHandler class>>activateWith: in Block: no > source > NonInteractiveUIManager(UIManager)>>defer: > PharoCommandLineHandler class>>activateWith: > no source in BasicCommandLineHandler>>activateSubCommand: in Block: no > source > BlockClosure>>on:do: > BasicCommandLineHandler>>activateSubCommand: > BasicCommandLineHandler>>handleSubcommand > BasicCommandLineHandler>>handleArgument: > no source in BasicCommandLineHandler>>activate in Block: no source > > SmallInteger>>no (source is Undeclared) > > UndefinedObject>>no (source is Undeclared) > > AbstractCompiler>>no (source is Undeclared) > > SmalltalkImage>>no (source is Undeclared) > > BlockClosure>>no (source is Undeclared) > > EvaluateCommandLineHandler>>no (source is Undeclared) > > EvaluateCommandLineHandler>>no (source is Undeclared) > > CommandLineHandler class>>no (source is Undeclared) > > BasicCommandLineHandler>>no (source is Undeclared) > > BasicCommandLineHandler>>no (source is Undeclared) > > PharoCommandLineHandler>>no (source is Undeclared) > > UIManager>>no (source is Undeclared) > > UndefinedObject>>no (source is Undeclared) > > CommandLineUIManager>>no (source is Undeclared) > > SmalltalkImage>>no (source is Undeclared) > > DelayMicrosecondScheduler>>no (source is Undeclared) > > BlockClosure>>no (source is Undeclared) > > SmalltalkImage>>no (source is Undeclared) > > WeakArray class>>no (source is Undeclared) > > > ps: source cannot be displayed because there is no formatter available in > the bootstrap >

Jan. 19, 2016

Re: [Pharo-dev] spotter: top search for senders and references

by stepharo

cool now could we have an help menu that describes the key elements. People cannot discover that by themselves. A menu item is cheap. Stef Le 19/1/16 14:43, Tudor Girba a Ã©crit : > Hi, > > With the latest GT integration, we also integrated the search for > senders and references from the first step. > > Here is a detailed explanation about it, including what we still want > to do, how itâs done, and how to discover what else is around: > http://www.humane-assessment.com/blog/spotting-senders-references-with-gtsp… > > > Please let us know what you think. > > Cheers, > Doru > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > www.feenk.com > > "Problem solving efficiency grows with the abstractness level of > problem understanding."

Jan. 19, 2016

Re: [Pharo-dev] Cmd + click

by stepharo

2016-01-19 15:37 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: Hi, there was a future that "cmd + click" browsed classes or showed implementors. Now it doesnât seem to work at least in Nautilus. Is anyone aware of this? platform and image version? It works on Windows pharo 50529: alt+right click -> browse Class/implementors of alt+shift+right click -> users of class /senders of > Cmd (Apple) key + (Shift) + Click works fine on OS X in #50535 Sven do you get implementors and senders working because I get refs and class def but not the method counterparts. Stef > >> Cheers. >> Uko >> > >

Jan. 19, 2016

Re: [Pharo-dev] Cmd + click

by stepharo

Excellent I will add it in the Updated Pharo by Example chapter Stef Le 19/1/16 16:50, Sven Van Caekenberghe a Ã©crit : >> On 19 Jan 2016, at 15:51, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >> >> >> >> 2016-01-19 15:37 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: >> Hi, there was a future that "cmd + click" browsed classes or showed implementors. Now it doesnât seem to work at least in Nautilus. >> >> Is anyone aware of this? >> >> platform and image version? >> >> It works on Windows pharo 50529: >> alt+right click -> browse Class/implementors of >> alt+shift+right click -> users of class /senders of > Cmd (Apple) key + (Shift) + Click works fine on OS X in #50535 > >> Cheers. >> Uko >> > >

Jan. 19, 2016

Re: [Pharo-dev] Cmd + click

by Sven Van Caekenberghe

> On 19 Jan 2016, at 15:51, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2016-01-19 15:37 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Hi, there was a future that "cmd + click" browsed classes or showed implementors. Now it doesnât seem to work at least in Nautilus. > > Is anyone aware of this? > > platform and image version? > > It works on Windows pharo 50529: > alt+right click -> browse Class/implementors of > alt+shift+right click -> users of class /senders of Cmd (Apple) key + (Shift) + Click works fine on OS X in #50535 > Cheers. > Uko >

Jan. 19, 2016

Re: [Pharo-dev] spotter: top search for senders and references

by Esteban Lorenzano

> On 19 Jan 2016, at 16:15, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > >> On 19 Jan 2016, at 15:23, Esteban A. Maringolo <emaringolo(a)gmail.com <mailto:emaringolo@gmail.com>> wrote: >> >> It turns the search field into a "kind of" command line interface, with #sen/#ref as commands. >> I love CLIs so I welcome it, but I think It "perverts" the search field and uses an awkward syntax. I prefer to type "senders" than to type a special character like #. >> >> I would prefer adding a suffix command so you search for 'do: senders' or 'do: implementorsâ. > > just that there is no syntactical way to know when you want senders or just retrieve methods who start with do: and continue with keyword senâ¦ etc. > thatâs the reason from the hashtag (which is now a common symbol to filter/tag like in twitter/facebook/etc.) ah, btwâ¦ you can also do: do: #sen it does not have to be in frontâ¦ just you need to use the hash :) > cheers, > Esteban > >> >> Regards! >> >> >> Esteban A. Maringolo >> >> 2016-01-19 10:43 GMT-03:00 Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>>: >> Hi, >> >> With the latest GT integration, we also integrated the search for senders and references from the first step. >> >> Here is a detailed explanation about it, including what we still want to do, how itâs done, and how to discover what else is around: >> http://www.humane-assessment.com/blog/spotting-senders-references-with-gtsp… <http://www.humane-assessment.com/blog/spotting-senders-references-with-gtsp…> >> >> <spotter-senders.png> >> >> Please let us know what you think. >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com/> >> www.feenk.com <http://www.feenk.com/> >> >> "Problem solving efficiency grows with the abstractness level of problem understanding." >> >

Jan. 19, 2016