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

[Pharo-project] [update 3.0] #30034

by StÃ©phane Ducasse

30034 ----- 10177 Deprecate accept* in visitor https://pharo.fogbugz.com/f/cases/1017 Diff information: http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/FileSystem-Core-StephaneDuca… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Announcements-Core-StephaneD… Stef and Igor (from Lviv)

April 11, 2013

Re: [Pharo-project] Is renamePackage in Nautilus correct ?

by Benjamin

Most probably yes :) Did I implemented myself or is this part of the refactoring engine ? Ben On Apr 11, 2013, at 2:47 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > 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] Versionner in 2.0 again

by Christophe Demarey

Hi Norbert, Sorry, I don't read Pharo ML every day else I will never have time to work on Versionner... I only have a part time to do that. What I'm doing on Versionner is to add the possibility to update your configurations at a very fine grained (add/remove projects/packages/groups). This version is a WIP and not yet usable. I'm not so far to have one version open for beta-test but I now face issues with Metacello on Pharo2 and some missing API in the toolbox. That's why I'm now working to have Metacello tests green on Pharo2. What I'm doing: update builderCi (used by Dale to test Metacello on Travis) to support Pharo2/3 : almost done be able to load MetacelloPreview on Pharo2/3 have green tests. With a clean and up to date metacello environment for Pharo, I will be able to focus on Versionner and have a result soon. I also did not take time to port the "old" Versionner on Pharo2 since I will face the same issues with Metacello/Pharo2. The problem is not really Versionner itself but the fact that it relies on libraries not tested and not fully working on Pharo2. I will take a look at your work. (some comments below). Thanks for your contribution. Regards, Christophe. Le 11 avr. 2013 Ã 13:18, Norbert Hartl a Ã©crit : > 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. I tried to switch at a time to Pharo2 but too many issues. So I switched back to Pharo1.4 to be able to work on Versionner. >> 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. I will check that you don't have useless parts of the new Versionner. As it is difficult to maintain branches with Monticello, I moved new Versionner developments to Smalltalkhub. >> 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. ConfigurationOf and Baseline are introduced by newest version of Metacello that the one shipped with Pharo2. >> 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. What is the version of Metacello and Metacello Toolbox you loaded? >> 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. I also fixed that for the new version. >> 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] [update 3.0] #30033

by Camille Teruel

On 11 avr. 2013, at 15:37, Marcus Denker wrote: > 30033 > ----- > > 10177 Deprecate accept* in visitor > https://pharo.fogbugz.com/f/cases/10177 > > Deprecate the wrong protocol for AST visitors. > Visitors do not accept they visit. > > - Clean also the messages send but not implemented > - rationalize the API now methods are named * Node > > The code to automatically rewrite all visitors is this (we tested with Opal): > > m := (RBProgramNodeVisitor allSubclasses gather: #methods) select: [ :e | e selector beginsWith: 'accept' ]. > m do: [ :e | > e methodClass compile: (e sourceCode copyReplaceAll: 'accept' with: 'visit'). > e methodClass removeSelector: e selector ]. Even if this script should do most of the work, one still needs to check the senders of the old selectors before. > (self systemNavigation allSendersOf: #acceptInlinedBlockNode:) > do: [ :e | e methodClass compile: (e sourceCode copyReplaceAll: 'acceptInlinedBlockNode:' with: 'visitInlinedBlockNode:') This last part is specific to Opal for example to rewrite the senders of #acceptInlinedBlock:.

April 11, 2013

[Pharo-project] [ANN] Pharo VM packages and PPA for Ubuntu (v2)

by Damien Cassou

Hi, Norbert Hartl and I are proud to announce that: - the pharo-vm package can now be installed on 64bits systems - the pharo-vm package can now be installed on older Ubuntu releases Todo list: -- - clean the package to avoid many warnings - automate the process of building these packages - create a server-only version which do not depend on graphical libraries (like X11 and libGL) -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

April 11, 2013

Re: [Pharo-project] Video on code profiling

by Alexandre Bergel

Here an abstract of what the video shows: -=-=-=-=-=-=-=-= This video demonstrates of Spy, the code execution profiling framework we have designed for the Pharo programming language. Spy offers efficient means to easily record particular information about a program execution. A profile may then be graphically rendered using the Roassal visualization engine. Such a visual representation of the program execution may exhibit relevant patterns indicating opportunities for improvement. -=-=-=-=-=-=-=-= Cheers, Alexandre On Apr 10, 2013, at 7:10 PM, 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 > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 11, 2013

Re: [Pharo-project] Test of patch needed for Linux users

by Damien Cassou

On Thu, Apr 11, 2013 at 3:10 PM, stephane ducasse <stephane.ducasse(a)free.fr>wrote: > we have a factory that create an object of each platform at startup. > look t OSPlatform. > it looks like FileSystem don't use that -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

April 11, 2013

[Pharo-project] [update 3.0] #30033

by Marcus Denker

30033 ----- 10177 Deprecate accept* in visitor https://pharo.fogbugz.com/f/cases/10177 Deprecate the wrong protocol for AST visitors. Visitors do not accept they visit. - Clean also the messages send but not implemented - rationalize the API now methods are named * Node The code to automatically rewrite all visitors is this (we tested with Opal): m := (RBProgramNodeVisitor allSubclasses gather: #methods) select: [ :e | e selector beginsWith: 'accept' ]. m do: [ :e | e methodClass compile: (e sourceCode copyReplaceAll: 'accept' with: 'visit'). e methodClass removeSelector: e selector ]. (self systemNavigation allSendersOf: #acceptInlinedBlockNode:) do: [ :e | e methodClass compile: (e sourceCode copyReplaceAll: 'acceptInlinedBlockNode:' with: 'visitInlinedBlockNode:')

April 11, 2013

Re: [Pharo-project] Versionner in 2.0 again

by stephane ducasse

We care a lot else we would not have christophe to work on it since september. the problem is that he was disrtacted by inria tasks. For us we cannot use versionner if does not handle project. stef 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] Test of patch needed for Linux users

by Guillermo Polito

On Thu, Apr 11, 2013 at 3:10 PM, stephane ducasse <stephane.ducasse(a)free.fr>wrote: > we have a factory that create an object of each platform at startup. > look t OSPlatform. > Ahh ok, yeap. I was using that too (OSPlatform current) and a double dispatch :). > > > > > On Thu, Apr 11, 2013 at 7:40 AM, stephane ducasse < > stephane.ducasse(a)free.fr> wrote: > >> did you use platform logic? >> > > Stef, What do you mean exactly by platform logic? :) > > Yesterday I was working on mapping the KeyDown/KeyUp events to have > uniform key values, and that included platform dependent code, so I'm > interested :). > > >> Because this may be the place to add this logic which is platform >> dependent. >> >> Stef >> >> On Apr 11, 2013, at 7:35 AM, Damien Cassou <damien.cassou(a)gmail.com> >> wrote: >> >> >> On Wed, Apr 10, 2013 at 8:06 PM, Igor Stasenko <siguctua(a)gmail.com>wrote: >> >>> is this image-side patch or vm-side? or both? >> >> >> image-side only, a combination of native boost and reading of the >> standard ~/.config/user-dirs.dirs >> >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without losing >> enthusiasm." >> Winston Churchill >> >> >> > >

April 11, 2013