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

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

by Alexandre Bergel

+1 Well phrased! -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jan 19, 2016, at 2:10 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > This is amazing news! > > For those that might be less involved in this, the minimal image is a long term goal that is essentially in the works since the beginning of Pharo. It accumulated a ton of effort from multiple people (I did not participate, but I have an idea of the amount of effort and it really is huge and tedious), and now we see the first palpable result. This is one of those things that have almost no visible output, but will turn out to have a tremendous impact. > > I would like to thank everyone involved! Please do keep this up. Even if it might look less rewarding, you should know that this work is greatly appreciated. > > Cheers, > Doru > > >> On Jan 19, 2016, at 3: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). >> >> 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 >> > > -- > www.tudorgirba.com > www.feenk.com > > "It's not what we do that matters most, it's how we do it." > >

Jan. 19, 2016

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

by stepharo

thanks doru. Yes this is a long term effort :) Le 19/1/16 18:10, Tudor Girba a Ã©crit : > This is amazing news! > > For those that might be less involved in this, the minimal image is a long term goal that is essentially in the works since the beginning of Pharo. It accumulated a ton of effort from multiple people (I did not participate, but I have an idea of the amount of effort and it really is huge and tedious), and now we see the first palpable result. This is one of those things that have almost no visible output, but will turn out to have a tremendous impact. > > I would like to thank everyone involved! Please do keep this up. Even if it might look less rewarding, you should know that this work is greatly appreciated. > > Cheers, > Doru > > >> On Jan 19, 2016, at 3: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). >> >> 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 >> > -- > www.tudorgirba.com > www.feenk.com > > "It's not what we do that matters most, it's how we do it." > > >

Jan. 19, 2016

Re: [Pharo-dev] PluggableButtonMorph does not respect font size :(

by stepharo

Indeed. Actually, Alex Syrel spent 2 weeks to get this âlittleâ thing of computing the bounds of a string right (I think it works well now hopefully) :). excellent And we should be really picky about that. Especially since we will have a vector graphic. and I would like to avoid to have the font plaque that we have now. > > Doru > >> Stef >> >> >> <djbhggee..png> > -- > www.tudorgirba.com > www.feenk.com > > "Problem solving should be focused on describing > the problem in a way that makes the solution obvious." > > > > > > >

Jan. 19, 2016

Re: [Pharo-dev] Cmd + click

by stepharo

strnage in my image Latest update: #50529 when I type factorial in the method definitino pane and do click + mouse I do not get the implementors Le 19/1/16 17:50, Yuriy Tymchuk a Ã©crit : > 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 >> <mailto:sven@stfx.eu>> wrote: >> >>> >>> On 19 Jan 2016, at 17:31, stepharo <stepharo(a)free.fr >>> <mailto:stepharo@free.fr>> wrote: >>> >>> >>> 2016-01-19 15:37 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com >>> <mailto:yuriy.tymchuk@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] how do I get the list of categories in Spotter?

by Tudor Girba

Hi, I was not arguing with you :). You asked how to find the answer to help you write something, and I replied how to get the information. I am not saying that this is the best way. Itâs only the way it is. Doru > On Jan 19, 2016, at 9:24 PM, stepharo <stepharo(a)free.fr> wrote: > > Doru I know that I can be a power user. > This is not the point I want to make. > The point I want to make (I know I'm dense) is how normal people under stress because > - they learn > - or are doing a task > can learn and discover. > When I'm hacking my business I do not want to browse a blog post. I want my job to get done and get home. > > Stef > > > Le 19/1/16 14:46, Tudor Girba a Ã©crit : >> Hi, >> >> Itâs not magic :) >> >> You can directly query this programmatically. >> - Find all processors defined in the image: >> GTSpotter spotterExtendingMethods >> - Find the top level processors defined in the first step >> GTSpotter spotterExtendingMethods select: [ :each | each methodClass = GTSpotter ] >> >> You can find some more details in the last post: >> http://www.humane-assessment.com/blog/spotting-senders-references-with-gtsp… >> >> Does this make sense? >> >> Cheers, >> Doru >> >> >>> On Jan 19, 2016, at 12:36 PM, stepharo <stepharo(a)free.fr> wrote: >>> >>> Hi >>> >>> I was stupid enough to write in the book that #method is for methods. but this is for #implementors. >>> So how do I get the list of categories in Spotter? >>> Magic? >>> >>> Stef >>> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Not knowing how to do something is not an argument for how it cannot be done." >> >> >> > > -- www.tudorgirba.com www.feenk.com "Every thing should have the right to be different."

Jan. 19, 2016

Re: [Pharo-dev] how do I get the list of categories in Spotter?

by stepharo

Doru I know that I can be a power user. This is not the point I want to make. The point I want to make (I know I'm dense) is how normal people under stress because - they learn - or are doing a task can learn and discover. When I'm hacking my business I do not want to browse a blog post. I want my job to get done and get home. Stef Le 19/1/16 14:46, Tudor Girba a Ã©crit : > Hi, > > Itâs not magic :) > > You can directly query this programmatically. > - Find all processors defined in the image: > GTSpotter spotterExtendingMethods > - Find the top level processors defined in the first step > GTSpotter spotterExtendingMethods select: [ :each | each methodClass = GTSpotter ] > > You can find some more details in the last post: > http://www.humane-assessment.com/blog/spotting-senders-references-with-gtsp… > > Does this make sense? > > Cheers, > Doru > > >> On Jan 19, 2016, at 12:36 PM, stepharo <stepharo(a)free.fr> wrote: >> >> Hi >> >> I was stupid enough to write in the book that #method is for methods. but this is for #implementors. >> So how do I get the list of categories in Spotter? >> Magic? >> >> Stef >> > -- > www.tudorgirba.com > www.feenk.com > > "Not knowing how to do something is not an argument for how it cannot be done." > > >

Jan. 19, 2016

Re: [Pharo-dev] running Hapao on the String class - error: key not found in MethodDictionary for testClassComment

by Alejandro Infante

Hi again! So I looked at the problem, wrote a fix, committed, created a new version and tested it. It should work out of the box :) Also the ConfigurationOfSpy should load Roassal by its own, so to download Hapao just run: ââ Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Spy2'; configurationOf: 'Spy2'; loadStable. ââ Cheers! Alejandro > On Jan 19, 2016, at 4:25 PM, Alejandro Infante <alejandroinfante91(a)gmail.com> wrote: > > Hi, > So this is not problem of Spy2, but a bug of Hapao. There should be no problem instrumenting String with Spy2 if your profiler is correct, the proof of this is that the image does not explode when you were debugging the execution (I was actually able to open a browser and check the tests of String). > > This problem happened because we naively assumed, at least in this implementation Hapao, that for every Test Object there is a Test Method associated in the class of the Test Object. This is not correct for inherited tests, where the Test Method is in one of the superclasses. > > I will submit a fix for that as soon as possible ;) > > Thanks for the bug report!! > Alejandro > >> On Jan 19, 2016, at 8:58 AM, stepharo <stepharo(a)free.fr> wrote: >> >> Hi sheridan >> >> spy string can be a challenge. >> Now I was thikning recently that we should have tests for Ring. So if you are interested I would love to review your tests. >> >> Sef >> >> >> Le 18/1/16 22:45, sheridan(a)sheridan-mahoney.com a Ã©crit : >>> Hi there, >>> >>> I am trying to use Hapao to check test coverage in the String class and have run across some trouble. To begin, I loaded Spy2 and Roassal2 using the following code: >>> >>> Gofer new smalltalkhubUser: 'ObjectProfile' >>> project: 'Roassal2'; >>> package: 'ConfigurationOfRoassal2'; >>> load. >>> (Smalltalk at: #ConfigurationOfRoassal2) load. >>> >>> Gofer it >>> smalltalkhubUser: 'ObjectProfile' project: 'Spy2'; >>> configurationOf: 'Spy2'; >>> loadStable. >>> >>> Hapao then showed up in the "World" menu, and I selected it. I chose "Hapao @ class ... " and entered "String". >>> >>> Hapao starts running tests, but before long a debugger comes up with the error: KeyNotFound: key #testClassComment not found in MethodDictionary . IF I click "Proceed", other keyNotFound errors come up. This is in a 50524 image. >>> >>> Is there something wrong with the way I am invoking Hapao? >>> Many thanks, >>> Sheridan >>> >>> >>> >> >> >

Jan. 19, 2016

Re: [Pharo-dev] running Hapao on the String class - error: key not found in MethodDictionary for testClassComment

by stepharo

Le 19/1/16 19:45, sheridan(a)sheridan-mahoney.com a Ã©crit : > Hi Stef, > > That would be great. I have only been writing very simple tests but it > would be nice to get some feedback. > > What is the best way to get you the tests? Publish a slice to the > Pharo50Inbox? Create a bug entry and post in Pharo50Inbox. I think that you canget an impact because Ring should be nice to get tests and like that we can make sure that we will know if we break it in the future > Thanks, > > Sheridan > > > > Hi sheridan spy string can be a challenge. Now I was thikning recently > that we should have tests for Ring. So if you are interested I would > love to review your tests. Sef > > Le 18/1/16 22:45, > >>> Hi there, I am trying to use Hapao to check test coverage in the >>> String class and have run across some trouble. To begin, I loaded >>> Spy2 and Roassal2 using the following code: Gofer new >>> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; package: >>> 'ConfigurationOfRoassal2'; load. (Smalltalk at: >>> #ConfigurationOfRoassal2) load. Gofer it smalltalkhubUser: >>> 'ObjectProfile' project: 'Spy2'; configurationOf: 'Spy2'; >>> loadStable. Hapao then showed up in the "World" menu, and I selected >>> it. I chose "Hapao @ class ... " and entered "String". Hapao starts >>> running tests, but before long a debugger comes up with the error: >>> KeyNotFound: key #testClassComment not found in MethodDictionary . >>> IF I click "Proceed", other keyNotFound errors come up. This is in a >>> 50524 image. Is there something wrong with the way I am invoking >>> Hapao? Many thanks, Sheridan >> ****************************** > > >

Jan. 19, 2016

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

by stepharo

Le 19/1/16 20:25, David Allouche a Ã©crit : > BTW, thanks for the explanations for Spotter. > >> On 19 Jan 2016, at 18:37, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> And then, in Spotter we have another discovery mechanism: Shift. When you press it, all clickable things get highlighted (including the arrow). We chose Shift because it is something that you type often as part of a text, so it will be very likely that you will press it when working with Spotter as well. And this will get you to see that something happens. > I am lazy and fearful of RSI. If I can avoid using the shift key at all, I am quite happy. So I did not notice that the arrows where clickable. :) Same here. > > Here are a few suggestions that would fit my workflow. > > I also think that "Selectors" should appear after classes and before packages, and be called "Messages". Typically I want to open a specific class, or a specific message in a specific class. > > The short list of implementors at the top level is usually noise and might have confused Stef. It becomes relevant once the message is fully specified. > > Diving in should be done with right arrow when at the end of the command line. > > Diving out with left arrow at the start of the command line. I was wondering what is the benefit to have cmd - shit arrow vs arrow > > When a list of paginated (only first N items), then the category line should be accessible with arrows, so we can dive into a category just with arrows. > > That would be awesome. >

Jan. 19, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] 4e9825: 50535

by David Allouche

> On 19 Jan 2016, at 19:07, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > I can only tell what the github interface let me see: > > 1) the diffs in update scripts (my guess comes from here) > -script50534 > +script50535 > > and > update50535 > > 2) the commentForCurrentUpdate.st > > 3) the ConfigurationOfUnifiedFFI > > The real changes of code (if any ?), I can't see any of them - because massive changes screw github iface as already noticed. I think the problem is more that github blows on large numbers of file renames. That because git does not have any native rename tracking, and renames are detected from file similarity. So rename detection when generating diffs is disabled when there is a large number of file adds/removals. Git sucks like that. Serializing packages as single files (instead of methods as a single file) would limit the problem. And In my opinion that would also make code easier to read. It would make sense to make one commit per issue, that would limit the damage from renames. Even if not all commits are individually validated by the bot. I guess those validated by the bot could have a special note in the commit message.

Jan. 19, 2016