April 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] SmartSuggestions - Prototype 0

by Goubier Thierry

Le 11/04/2013 00:16, Gisela Decuzzi a Ã©crit : > Hi Alexandre, > > > >I have selected the class ROElement, and Nautilus still offers me to > look for the implementors > There aren't suggestion for a class currently implemented so it won't > offer you nothing yet. But something we can do it's to figure it out > witch options would be nice to have, I was thinking in: > - Class references > - Hierarchy > - Browse the class > So tell me your ideas and I will try to make a command for that and then > add it as a suggestion, if you browse #specialCommands (the message I'm > using to find the available actions for the selected code) you will see > that the only real implementors are the RBVariableNode and > RBMessageNode. I think that the actions you want are for > RBClassReference (I will check it). But tell me what would you expect to > see as a quick action over a class reference :) It maybe that you need to check the binding associated with the RBVariableNode to get that this is a Class reference. Ok. I added a debug command to AltBrowser to inspect the AST of a method, it may help. With that it shows that a Class is a RBVariableNode with a RBLiteralBinding name. Just change the RBVariableNode commands shown in that case. Thierry > > > About the suggestion... the "smart ones" are at the end of the menu, the > other ones are the default, it will be very cool to replace the hole > menu (it's something that I have in my todolist) but for a 0 prototype > I've just focused on adding more options. > In fact I surely will be commiting some changes for display just a > suggestions menu using a short cut (alt+t) tomorrow. > > >Well.. why do I need a new window? Why not simply give the list of the > implementors? You can easily turn your menu entry "Implementors" as a > submenu (as for "Extended search...") that gives the six implementors of > this method directly. > > This is just the default behavior for implementors, since I'm using the > same action, I will do some performace test in that and will check if I > can add it as a task for my todo. Maybe searching for implementors isn't > so fast and I wouldn't like to keep waiting a lot of time just to > display a menu because maybe you don't even want to search implementors. > But it's a good point for navigation improvements that I also want to > make :) > > Thanks for the review and let me know about witch suggestions would you > like to have depending what you have selected, I will implement as many > as possible and try to finish with an easy way to add more options. > > > > > 2013/4/10 Alexandre Bergel <alexandre.bergel(a)me.com > <mailto:alexandre.bergel@me.com>> > > Hi Gisela, > > Currently, Nautilus is not really smart at giving a contextual menu. > > Consider the following screenshot: > > I have selected the class ROElement, and Nautilus still offers me to > look for the implementors > > Another screenshot: > > I have selected the method startingPointOf: > > I like the idea of easily accessing Implementors. Currently, if I > click on "implementors of it" or in your menu "Implementors", I have > a new window. Well.. why do I need a new window? Why not simply give > the list of the implementors? You can easily turn your menu entry > "Implementors" as a submenu (as for "Extended search...") that gives > the six implementors of this method directly. > > Alexandre > > > On Apr 10, 2013, at 8:18 AM, Gisela Decuzzi <giseladecuzzi(a)gmail.com > <mailto:giseladecuzzi@gmail.com>> wrote: > >> Hello, I've been working in a prototype for adding some >> suggestions to the menu depending on what it's selected with the >> cursor. (The same feature that ALT-Browser has, but now in Nautilus). >> >> It's just a little piece of code and has a lot of pending work, >> right now you can press right click over a message send and offers >> you browse implementors: >> <Implementors.png> >> >> And if you are in an instance variable name and then right click: >> <InstanceVariablesOptions.png> >> (The same that ALT-Browser is doing, but in Nautilus) >> >> I developed in the latest 2.0 image. >> >> >> So, if you want to load in your image, play a little and then give >> me some feedback... >> >> Gofer it >> smalltalkhubUser: 'gisela' >> project: 'SmartSuggestions'; >> package: 'SmartSuggestions'; >> package: 'SmartSuggestionsNautilus'; >> load. >> >> :) >> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

April 11, 2013

Re: [Pharo-project] Video on code profiling

by Esteban Lorenzano

nice :) On Apr 11, 2013, at 1:10 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > Just wanted to share this with you: > https://vimeo.com/63319467 > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

April 11, 2013

Re: [Pharo-project] Versionner in 2.0 again

by Esteban Lorenzano

I care... and a LOT :) But I was waiting for Christophe to say something :P Esteban On Apr 11, 2013, at 1:18 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > Huh, I find it strange that nobody cares. Does anybody use Versionner? > > Norbert > > > Am 09.04.2013 um 11:31 schrieb Norbert Hartl <norbert(a)hartl.name>: > >> Yesterday I tried again to use Versionner in 2.0 but did have much success. So I tried myself (because I think Versionner is important) and could final generate a new version of my project using versionner. >> >> Following things I noticed (I'm writing this because I'm not sure which issue to open for what package. I'm just want opinions and after that I can open/upload whatever): >> >> I loaded Versionner from Metacello (taken from [1]) >> >> Gofer new >> url: 'http://ss3.gemstone.com/ss/Versionner'; >> package: 'ConfigurationOfVersionner'; >> load. >> (Smalltalk at: #ConfigurationOfVersionner) perform: #load >> >> monticello issues >> ============= >> >> While updating the rest of the packages to the newest I saw that >> >> Versionner-Core-Model-ChristopheDemarey.19 >> >> has an older ancestor for fixing something for pharo 1.4. The package >> >> Versionner-Core-Model-ChristopheDemarey.20 >> >> merged the packages back to HEAD but reverted some things like SystemAnnouncer back to SystemChangeNotifier. So I'm using >> >> Versionner-Core-Model-ChristopheDemarey.18 >> and >> Versionner-Core-Commands-ChristopheDemarey.17 >> >> as older packages. Any other package is the newest in the repository. >> >> metacello toolbox issues >> ================== >> >> I don't know much about metacello toolbox but the separation of files into ConfigurationOf and Baseline seems to have potential for confusion. There is a notion of a basename so it can build ConfigurationOfMyProject as well as BaselineOfMyProject (MyProject being the basename). But in the MetacelloToolbox in the pharo2.0 repository it does not seem right. I had to change the code to use (MBToolbox baseNameOf: â¦) at a few places. I took orientation from the message signature. If a method expects a configurationBaseName and the sender used the configuration class I changed it. I'll attach the mcz for now to this mail until it is clear what to do. >> >> versionner issues >> ============= >> >> At one place I added a metacello toolbox name conversion because it made sense to make it there. The other thing I had to fix is a method notification that takes the wrong entity from an announcement. Both packages attached as I don't have commit rights and don't know where the issue tracker for versionner is if there is any) >> >> I would be glad if any of you guys that know about that stuff could drop me a note if this is ok or where I've gone wrong. >> >> thanks, >> >> Norbert >> >> >> [1] http://users.dcc.uchile.cl/~jsandova/versionner/ >> >> <Metacello-ToolBox-NorbertHartl.136.mcz> >> <Versionner-Core-Commands-NorbertHartl.18.mcz> >> <Versionner-Core-Model-NorbertHartl.19.mcz> >

April 11, 2013

Re: [Pharo-project] Versionner in 2.0 again

by phil＠highoctane.be

Well, it for sure looks interesting. Once one has the understanding about configurations. Which will lead to look for something like that tool. Not sure I am mastering configuration basics at the moment... So, that's why I guess. Phil 2013/4/11 Norbert Hartl <norbert(a)hartl.name> > Huh, I find it strange that nobody cares. Does anybody use Versionner? > > Norbert > > > Am 09.04.2013 um 11:31 schrieb Norbert Hartl <norbert(a)hartl.name>: > > Yesterday I tried again to use Versionner in 2.0 but did have much > success. So I tried myself (because I think Versionner is important) and > could final generate a new version of my project using versionner. > > Following things I noticed (I'm writing this because I'm not sure which > issue to open for what package. I'm just want opinions and after that I can > open/upload whatever): > > I loaded Versionner from Metacello (taken from [1]) > > Gofer new > url: 'http://ss3.gemstone.com/ss/Versionner'; > package: 'ConfigurationOfVersionner'; > load. > (Smalltalk at: #ConfigurationOfVersionner) perform: #load > > monticello issues > ============= > > While updating the rest of the packages to the newest I saw that > > Versionner-Core-Model-ChristopheDemarey.19 > > has an older ancestor for fixing something for pharo 1.4. The package > > Versionner-Core-Model-ChristopheDemarey.20 > > merged the packages back to HEAD but reverted some things like > SystemAnnouncer back to SystemChangeNotifier. So I'm using > > Versionner-Core-Model-ChristopheDemarey.18 > and > Versionner-Core-Commands-ChristopheDemarey.17 > > as older packages. Any other package is the newest in the repository. > > metacello toolbox issues > ================== > > I don't know much about metacello toolbox but the separation of files into > ConfigurationOf and Baseline seems to have potential for confusion. There > is a notion of a basename so it can build ConfigurationOfMyProject as well > as BaselineOfMyProject (MyProject being the basename). But in the > MetacelloToolbox in the pharo2.0 repository it does not seem right. I had > to change the code to use (MBToolbox baseNameOf: â¦) at a few places. I took > orientation from the message signature. If a method expects a > configurationBaseName and the sender used the configuration class I changed > it. I'll attach the mcz for now to this mail until it is clear what to do. > > versionner issues > ============= > > At one place I added a metacello toolbox name conversion because it made > sense to make it there. The other thing I had to fix is a method > notification that takes the wrong entity from an announcement. Both > packages attached as I don't have commit rights and don't know where the > issue tracker for versionner is if there is any) > > I would be glad if any of you guys that know about that stuff could drop > me a note if this is ok or where I've gone wrong. > > thanks, > > Norbert > > > [1] http://users.dcc.uchile.cl/~jsandova/versionner/ > > <Metacello-ToolBox-NorbertHartl.136.mcz> > <Versionner-Core-Commands-NorbertHartl.18.mcz> > <Versionner-Core-Model-NorbertHartl.19.mcz> > > >

April 11, 2013

Re: [Pharo-project] Versionner in 2.0 again

by Norbert Hartl

Huh, I find it strange that nobody cares. Does anybody use Versionner? Norbert Am 09.04.2013 um 11:31 schrieb Norbert Hartl <norbert(a)hartl.name>: > Yesterday I tried again to use Versionner in 2.0 but did have much success. So I tried myself (because I think Versionner is important) and could final generate a new version of my project using versionner. > > Following things I noticed (I'm writing this because I'm not sure which issue to open for what package. I'm just want opinions and after that I can open/upload whatever): > > I loaded Versionner from Metacello (taken from [1]) > > Gofer new > url: 'http://ss3.gemstone.com/ss/Versionner'; > package: 'ConfigurationOfVersionner'; > load. > (Smalltalk at: #ConfigurationOfVersionner) perform: #load > > monticello issues > ============= > > While updating the rest of the packages to the newest I saw that > > Versionner-Core-Model-ChristopheDemarey.19 > > has an older ancestor for fixing something for pharo 1.4. The package > > Versionner-Core-Model-ChristopheDemarey.20 > > merged the packages back to HEAD but reverted some things like SystemAnnouncer back to SystemChangeNotifier. So I'm using > > Versionner-Core-Model-ChristopheDemarey.18 > and > Versionner-Core-Commands-ChristopheDemarey.17 > > as older packages. Any other package is the newest in the repository. > > metacello toolbox issues > ================== > > I don't know much about metacello toolbox but the separation of files into ConfigurationOf and Baseline seems to have potential for confusion. There is a notion of a basename so it can build ConfigurationOfMyProject as well as BaselineOfMyProject (MyProject being the basename). But in the MetacelloToolbox in the pharo2.0 repository it does not seem right. I had to change the code to use (MBToolbox baseNameOf: â¦) at a few places. I took orientation from the message signature. If a method expects a configurationBaseName and the sender used the configuration class I changed it. I'll attach the mcz for now to this mail until it is clear what to do. > > versionner issues > ============= > > At one place I added a metacello toolbox name conversion because it made sense to make it there. The other thing I had to fix is a method notification that takes the wrong entity from an announcement. Both packages attached as I don't have commit rights and don't know where the issue tracker for versionner is if there is any) > > I would be glad if any of you guys that know about that stuff could drop me a note if this is ok or where I've gone wrong. > > thanks, > > Norbert > > > [1] http://users.dcc.uchile.cl/~jsandova/versionner/ > > <Metacello-ToolBox-NorbertHartl.136.mcz> > <Versionner-Core-Commands-NorbertHartl.18.mcz> > <Versionner-Core-Model-NorbertHartl.19.mcz>

April 11, 2013

[Pharo-project] [update 1.4] #14460

by Marcus Denker

14460 ----- 7219 compiledMethod hash https://pharo.fogbugz.com/f/cases/7219

April 11, 2013

[Pharo-project] [update 2.0] #20597

by Marcus Denker

20597 ----- 10249 Backport 2.0: Red Light when all test are green https://pharo.fogbugz.com/f/cases/10249 10230 backport 2.0: 10229 Fix sender of #copyWithTempsFromMethodNode: https://pharo.fogbugz.com/f/cases/10230 10200 Date instances dayOfWeek wrong https://pharo.fogbugz.com/f/cases/10200 10179 backport 2.0: 10038 Wrong deprecated message https://pharo.fogbugz.com/f/cases/10179 Diff information: http://ss3.gemstone.com/ss/Pharo20/Nautilus-MarcusDenker.439.diff http://ss3.gemstone.com/ss/Pharo20/KernelTests-MarcusDenker.478.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1344.diff

April 11, 2013

[Pharo-project] [update 3.0] #30032

by Marcus Denker

30032 ----- 10237 MCHttpRepository>>#location: should instantiate specialized repositories if possible https://pharo.fogbugz.com/f/cases/10237/ 7627 FileReference>>deleteAll follows symlinks https://pharo.fogbugz.com/f/cases/7627/ Diff information: http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Monticello-MarcusDenker.781 http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/MonticelloGUI-MarcusDenker.2… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/FileSystem-Core-MarcusDenker… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/FileSystem-Tests-Core-Marcus…

April 11, 2013

[Pharo-project] Configuration browser doesn't works in 3.0?

by Torsten Bergmann

Esteban wrote: >there is no metarepo for 3.0 yet. >Also, it will be moved to sthub so... yep, broken :) I already created it two weeks ago and the config browser is already switched to it with SLICE-Issue-10138 on 27th of March http://smalltalkhub.com/#!/~Pharo/MetaRepoForPharo30 It also contains some contents to show that it is working Igor wrote: >#Pharo3.0 >#Latest update: #30013 Rather old, this was fixed in #30014 and 3.0 is already at #30031 Please update your 3.0 image ;) Bye T.

April 11, 2013

Re: [Pharo-project] [FYI] Athens tutorial

by Tristan Bourgois

2013/4/11 Igor Stasenko <siguctua(a)gmail.com> > On 11 April 2013 08:55, Tristan Bourgois <tristan.bourgois(a)gmail.com> > wrote: > > > > > > > > 2013/4/10 Igor Stasenko <siguctua(a)gmail.com> > >> > >> > >> > >> On 10 April 2013 09:14, Tristan Bourgois <tristan.bourgois(a)gmail.com> > >> wrote: > >>> > >>> > >>> > >>> > >>> 2013/4/9 Igor Stasenko <siguctua(a)gmail.com> > >>>> > >>>> Yes, this is a known bug actually, which i demonstrated to audience > >>>> during > >>>> tutorial presentation.. > >>>> i/cairo miss the correct font matrix setup.. and i need to see what's > >>>> there. > >>>> Cairo caching the glyphs in a strange way (so if you never drawn > >>>> anything with given font before and your first drawing will use some > >>>> rotation > >>>> then everything will be rendered correctly, but if you already drawn > >>>> anything > >>>> it will render them like you shown).. > >>>> I'm going to fix that issue when i come back from Lviv. > >>>> > >>> > >>> Super :) > >>> > >>> Did you also see the cairo_text_path() method? It's very interesting if > >>> you want to stroke the letter! > >> > >> > >> Yes but this is more for fancy artistic text. For rendering large > amounts > >> of text (like big lists/source code) you don't want to do that, > >> because it will be too slow. > >> > > > > Thanks for the advice I will share it to my team because they want > > performance and use text_path instead of show_text. > > > > yes, the freetype library (and i guess you using it) is highly > optimized for font rendering. > sure thing, cairo path rendering is fast as well, but it is not as > specialized for just font rendering as freetype, > therefore, i have no doubts that it will be slower. > I only use Athens to rendering the graphics framework :) And I try to not use directly some AthensCairo object to benefit of futur new backend of Athens :) and sincerely you really make a good job of the Athens interface! It's very easy to use it! In one case I use AthensCairo object. I have to use AthensCairoMatrix instead of AthensAffineTransform to represent the transformation of a shape because I have to make an inversion of the matrix to make a global position to the local position of the shape. >>>> -- > >>>> Best regards, > >>>> Igor Stasenko. > >>> > >>> > >> > >> > >> > >> -- > >> Best regards, > >> Igor Stasenko. > > > > > > > > -- > Best regards, > Igor Stasenko. > >

April 11, 2013