- Pharo-dev - lists.pharo.org

[Pharo-project] Is renamePackage in Nautilus correct ?

by Goubier Thierry

Hi, I'm trying to rename packages, so I'm adding the command to AltBrowser using the Nautilus renamePackage as the way to do it. But looking at the code, I wonder : does this really work ? If I select a subcategory of my Monticello package, it looks like it will work (call RPackageOrganizer>>renamePackage:in:). But, if I select my Monticello package itself (the one with the curly M ico) then it seems it will rename just the RPackage and not much else (i.e. for example, if I rename AST-Core, AST-Core-Matching, AST-Core-Nodes, etc... will stay unchanged). Did I got that right ? Thierry -- 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] [3.0] CI build is broken

by Camillo Bruni

Norbert, I deprecated now the old scripts and I had a look at your script proposal and I extended it a bit: https://gist.github.com/dh83/5363000 what do you think? On 2013-04-02, at 12:02, Camillo Bruni <camillobruni(a)gmail.com> wrote: > Yes I just haven't fully announced it yet ;) since I only programmed them > this saturday and was waiting for the pharo conf ;) > > But I will deprecate it with a warning message in it tomorrow or so. > And then people should rename their scripts. > > > On 2013-04-02, at 11:58, Norbert Hartl <norbert(a)hartl.name> wrote: > >> Well, I would say a >> >> mv vm-ui.sh pharo-ui >> >> would do a good job to get out of deprecation. Honestly if the scripts are deprecated just take them out of the download. I don't know why to leave them there because it is confusing. >> >> Norbert >> >> Am 02.04.2013 um 11:24 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> Hi Norbert, >>> >>> the vm-ui.sh script is deprecated (yep, Camillo already deprecated something, even if it is brand new). >>> >>> now the valid scripts are >>> >>> "pharo" and "pharo-ui" >>> >>> :) >>> >>> Esteban >>> >>> On Apr 2, 2013, at 11:17 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>>> Another attempt. >>>> >>>> Norbert >>>> >>>> >>>> <vm-ui.sh> >>>> Am 02.04.2013 um 10:43 schrieb Norbert Hartl <norbert(a)hartl.name>: >>>> >>>>> Ah, rats, didn't think it through. It only works for commandline switches that do not have an argument itself. Sad and sorry! >>>>> >>>>> Norbert >>>>> >>>>> Am 02.04.2013 um 10:38 schrieb Norbert Hartl <norbert(a)hartl.name>: >>>>> >>>>>> Very good Cami. I have two remarks. If it should be short I think that >>>>>> >>>>>> curl -sL get.pharo.org | bash >>>>>> >>>>>> is shorter than >>>>>> >>>>>> wget --quiet -O - get.pharo.org | bash >>>>>> >>>>>> If I see it correct the script is used for CI but as there is a get.pharo.org host I assume it is supposed to be an easy entry point for all kind of users, right? >>>>>> >>>>>> If this is true I find it somewhat strange to have a download-all-in-one-and-cozy-script that downloads everything needed but to start it I have still to provide the image myself to the shell scripts. So I added this to the script >>>>>> >>>>>> # parse vm options and image >>>>>> for arg in "$@" >>>>>> do >>>>>> if [[ $arg == -* ]]; >>>>>> then >>>>>> VMOPTIONS="$VMOPTIONS $arg" >>>>>> shift >>>>>> else >>>>>> break >>>>>> fi >>>>>> done >>>>>> IMAGE=$1 >>>>>> shift >>>>>> # if no image has been provided use the installed one >>>>>> if [ -z "$IMAGE" ]; >>>>>> then >>>>>> IMAGE=$DIR/Pharo.image >>>>>> fi >>>>>> >>>>>> which uses the downloaded image in case nothing has been specified on the commandline. >>>>>> >>>>>> Hope you like it. Usually I would extract the same portion of both scripts to an extra file but then there is the trade-off to have one more file in the download. I'll attach a version of vm-ui.sh for you to try. If you need help I'm happy to chime in for this. >>>>>> >>>>>> thanks for the effort, >>>>>> >>>>>> Norbert >>>>>> >>>>>> <vm-ui.sh> >>>>>> >>>>>> Am 02.04.2013 um 09:15 schrieb Camillo Bruni <camillobruni(a)gmail.com>: >>>>>> >>>>>>> we're back up, shinier than ever ;) >>>>>>> >>>>>>> check http://get.pharo.org ;) >>>>>>> >>>>>>> now you can use: >>>>>>> wget --quiet -O - get.pharo.org | bash >>>>>>> for the current stable release of Pharo and the PharoVM. >>>>>>> >>>>>>> On 2013-04-01, at 22:52, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>>>>>> No stress. In the worst case you can fix it tomorrow during the tutorial :). >>>>>>>> >>>>>>>> Doru >>>>>>>> >>>>>>>> >>>>>>>> On Apr 1, 2013, at 10:26 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> On 2013-04-01, at 22:09, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: >>>>>>>>> >>>>>>>>>> Tudor Girba-2 wrote >>>>>>>>>>> Could it have something to do with the latest optimizations of Camillo? >>>>>>>>>> >>>>>>>>>> Probably... Cami breaks everything :-P >>>>>>>>> >>>>>>>>> dammit, I wanted to silently add the new zeroconf scripts >>>>>>>>> obviously something went horribly wrong there, sorry guys.. working on it! >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> www.tudorgirba.com >>>>>>>> >>>>>>>> "What is more important: To be happy, or to make happy?" >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>> >>> >>> >> >> >

April 11, 2013

Re: [Pharo-project] Versionner in 2.0 again

by Alexandre Bergel

Yes, I use Versionner everyday. I do not commit without it actually. So far, I use Pharo 1.4 to do all my commit, sadly... Alexandre On Apr 11, 2013, at 7:32 AM, phil(a)highoctane.be wrote: > 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> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 11, 2013

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