- Pharo-dev - lists.pharo.org

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

by Christophe Demarey

Hi Eliot, Le 19 janv. 2016 Ã 19:29, Eliot Miranda a Ã©crit : > Hi All, > > great news! Where can I read a specification of the Oz VM facilities? I do not know all the details of the Oz VM but basically, it is a standard stack interpreter vm specialized to be able to run 2 images at the same time on top of it. Guillermo made it possible by using one available bit in the object header of objects to mark the ownership of an object (e.g. is my object from image1 or image2?). Then, he mainly had to specialize VM primitives dealing with objects retrieval from memory. By example, he had to modify the garbage collector to set the right nil instance (yes, we have 2 images so 2 nil instances. we need to take the one of the active image) when an object is garbage collected; the primitive someObject has to return an object from the active image, etc. There is also a way to switch execution from an image to the other just by switching the special objects array reference. You can find some information in: https://guillep.github.io/files/publications/Poli15Thesis.pdf. The Oz code is in http://smalltalkhub.com/#!/~Guille/ObjectSpace and in https://github.com/guillep/OzVM The current implementation uses Cog 6.6.1and OzVM-GuillermoPolito.22. I do not know if Guille has a more formal specification of the Oz VM. If you have advices on what is the best way to handle two distinct object (memory) spaces in Spur, they will be welcomed :) Cheers, Christophe > _,,,^..^,,,_ (phone) > > On Jan 19, 2016, at 6:29 AM, 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 >>

Jan. 20, 2016

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

by Christophe Demarey

Thanks all for your kind words and encouragements! Doru, you're right it has been made possible only because a lot of people took care to clean Pharo time after time*. By example, bootstraping Pharo 2.0 would have been a lot more pain! We can also thanks Pavel for the work he did / does on the minimal image that goes into the same direction. Cheers, Christophe * boy scouts rule: Leave the campground cleaner than you found it. Le 19 janv. 2016 Ã 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. 20, 2016

Re: [Pharo-dev] another spotter question

by Ben Coman

On Wed, 20 Jan 2016 at 3:37 AM stepharo <stepharo(a)free.fr> wrote: > > > Hmm. Thanks for describing this way of working. > > Here is the thing. We observed users working with this, and they all used predominantly the keyboard. So, we favored keyboard use. This is not an argument for anything, and it does not mean that that is the best design, I am just telling you how we designed it. Things can change, and this is why it is important to understand how people tend to use the UI. > > So, every (and only) selection has actions. In your example, the #Menu category has a right arrow next to it. If you click on that you âDive in categoryâ. That means that if you want to dive in #Implementors, you navigate there, and then you get the option of diving in. > > We consciously chose to not show all actions all the time because that would have led to an overcrowded UI with too many things to choose from. Right now, you have 5 main things to click on and that is it. > > Now, hearing your scenario, it seems to make sense to make the category clickable as well and make it dive in that category. We will look at it (or maybe someone else does it beforehand :)). Thanks. > > Does this make more sense now? > > > Yes! I do not get why keyboard is orthogonal to direct access. > > To me what I hate in UI is UI that are showing information but do not let > you access it. > > How can I see that I can do something on the list? > The arrows only arrive when I click on ........ > So I was trying to click on the label and it did not work. Of course I > must click on the first element > of the list so that the arrow show up on the element and the label!!!!! > > What??? > > Seriously doru. You should have asked UI blind like me to test > Spotter. > I would have recorded a session and you can see that there are > glitches that you do not even see. > I'm just continuously bumping on them. > This is why I could understand Spotter and use it only to find a > class. > > > > > > > > > This is why I like the grabbing possibility of file on mac via the icons > and the navigation from there > because I see the file it is in front of my nose and I do not to jump into > a file system (like a mail download folder > I have no clue where it is) to grab it. > So to me Spotter should offer the same. Show information and let me grab > it. Especially when this is on the suggstion > list. > > I do not understand how you solve the problem I got with shortcut btw. > > You see the point is the following. Diving can be frustrating. > If on click on the labl you get the list then it can work really well. > > > > Doru > > > Stef > > > > <icfedjib..png> > > > --www.tudorgirba.comwww.feenk.com > > "When people care, great things can happen." > > > > > > > > >

Jan. 20, 2016

[ANN] OSSubprocess v0.2.0 release

by Mariano Martinez Peck

Hi guys, I am happy to announce OSSubprocess v0.2.0. You can see the changelog here: https://github.com/marianopeck/OSSubprocess/releases/tag/v0.2.0 Such version becomes the #stable, so the installation instructions remain the same. Note that I have improved and added more info in the documentation. I took into account most of the feedback I received in the first release plus some other stuff from the survey. If you have more feedback, just let me know! Hope you enjoy. Best, -- Mariano http://marianopeck.wordpress.com

Jan. 20, 2016

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

by Alexandre Bergel

hi Sheridan, Let us know how it goes with Hapao Alexandre > On Jan 18, 2016, at 6:45 PM, sheridan(a)sheridan-mahoney.com wrote: > > 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 > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 19, 2016

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

by Alexandre Bergel

Thanks Alejandro! I also bumped into this problem this very morning Cheers, Alexandre > On Jan 19, 2016, at 5:21 PM, Alejandro Infante <alejandroinfante91(a)gmail.com> wrote: > > 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 >>>> >>>> >>>> >>> >>> >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 19, 2016

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

by Sven Van Caekenberghe

> On 19 Jan 2016, at 22:40, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > What is RSI? https://en.wikipedia.org/wiki/Repetitive_strain_injury

Jan. 19, 2016

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

by Tudor Girba

Hi, > On Jan 19, 2016, at 9:18 PM, stepharo <stepharo(a)free.fr> wrote: > > > > Le 19/1/16 20:25, David Allouche a Ã©crit : >> BTW, thanks for the explanations for Spotter. You are welcome. Please keep challenging. This is how good design happens. >>> 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. What is RSI? Most people I know use Shift to type an upper case, and we observed that when people search, they often tend to still use uppercase. Not all, but many. That is why we put this functionality on Shift. This does not mean that it is enough, but we just wanted to increase the chance of people stumbling across this without any documentation. It only partially succeeded. Anyway, we should externalize the key bindings. Another thing on the to do list :) >> 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. #Messages is not a bad name, but then again I also thought that #Selectors was explicit enough :). What do others think? >> 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 Left/Right is used to move inside the text area (there is only one text field in the whole UI), and that is why you cannot consistently use it for navigating through results. Navigating when the cursor is at the end is a tempting idea, but it implies a mode that is not contextual (you need to things to look at). That is why I would not want to have it in this interface. >> >> 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. We explicitly chose not to do that because we did not want to mingle different kinds of elements in the same list. So, like this, when you press Cmd+Right, you will always dive in one single element, and not in many by mistake. Actually, our original goal was to have a way to expand the list in place (not only to dive in category). For this we wanted a â¦ line and clicking on that would expand the list in place. We did not get to do it yet, but I think this would solve quite some of the reported problems. But, please do keep challenging. And give it a try with writing your own processors. It would help us a lot. Cheers, Doru >> That would be awesome. -- www.tudorgirba.com www.feenk.com "Obvious things are difficult to teach."

Jan. 19, 2016

Re: [Pharo-dev] About Spotter Implementors and selectors

by Tudor Girba

Hi, > On Jan 19, 2016, at 9:36 PM, stepharo <stepharo(a)free.fr> wrote: > > Hi doru > > I was rereading your answers (which I could find anymore - shitty thunderbird) > and I realised that I have the impression that they are two mixed concerns. > > You use one to express exact matching and the other to have multiple match > and to me it looks not the right way to do it. > > Would you express the same if I could write > > #implement do: > > => exact match > > #implement *do: > => show only > when:do: > and otherâ¦do: That is the point! :) These are not the same. Right now we have #Implementors as being a partial match. But, we can have two different way (Implementors, and PartialImplementors or whatever). The processors that we have are not meant to be written in stone. Our idea was that we push it out there as examples, and then see what people want to use. We need people to play with this instead of us pushing a single set of searches on to people :). Regarding #Selectors, this idea came from a very long email exchange about a year ago when people were looking at Spotter like they did with the old Spotlight. Spotlight was actually finding #Selectors and was opening an Implementors Browser and people got confused when we showed the #Implementors as methods. But, we can rethink this. Really. Letâs continue the brainstorming, and I would love it if someone would jump in and propose code that we can play with. Cheers, Doru > Stef > -- www.tudorgirba.com www.feenk.com "Next time you see your life passing by, say 'hi' and get to know her."

Jan. 19, 2016

Re: [Pharo-dev] Cmd + click

by Nicolai Hess

2016-01-19 22:04 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > > > 2016-01-19 21:47 GMT+01:00 stepharo <stepharo(a)free.fr>: > >> Sven >> - I took the latest 50 >> - open playground >> - type factorial >> - cmd click on it => nothing >> - cmd shift click on it => nothing >> >> Now doing the same in Nautilus method pane works >> Now I understand why it was not working with me. >> >> It only works on method body. >> If you click on a signature it does not work (which is a bug to me). >> >> Stef >> >> > 17431 > <https://pharo.fogbugz.com/f/cases/17431/No-TextLink-for-methods-signature-i…> > No TextLink for methods signature in the code pane > oh, sorry you already opened an issue (17430) I didn't saw that.

Jan. 19, 2016