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

Re: [Pharo-dev] [PROVENANCE INTERNET] Re: problems with RPackage and cie...

by Esteban Lorenzano

On 15 Jan 2014, at 17:11, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > > > Le 15/01/2014 16:59, Esteban Lorenzano a Ã©crit : >> >> On 15 Jan 2014, at 16:52, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >> >>> Ok, testing a bit and I can't see much of a problem, except ... >>> >>> something really annoying ... >>> >>> Why is the tag disappearing if I move the only class in it to another package? >> >> RPackageTags are auto-removed if they become empty. > > Arrg! Again? > > And I guess the system category behind still exist? > > Ok, I won't hold that as a bug. It is a "feature". > > Just don't forget what happens if you want to reorganize classes between two packages : you're not free to do it the way you want, you have to keep at least one class in a tag to avoid seeing it disappear. yeah, I knowâ¦ I was just pointing how it is. Not sure how it has to beâ¦ AFAIR, this was a requested feature too :S > > 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 >

Jan. 15, 2014

Re: [Pharo-dev] [PROVENANCE INTERNET] Re: problems with RPackage and cie...

by Goubier Thierry

Le 15/01/2014 17:27, Goubier Thierry a Ã©crit : > > > Le 15/01/2014 16:59, Benjamin a Ã©crit : >> We are also facing some RPackage cache not in sync anymore with system >> leading to the impossibility to commit the code :( >> >> Ben > > I'm onto something with very few manipulations. Now I have a class > belonging to A listed in B too, but with the system category of A. > > And, if I inspect the B RPackage, there is no reference to that class. False alert. A bug in my stuff. I'll try again. 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

Jan. 15, 2014

Re: [Pharo-dev] problems with RPackage and cie...

by Goubier Thierry

Le 15/01/2014 16:59, Benjamin a Ã©crit : > We are also facing some RPackage cache not in sync anymore with system > leading to the impossibility to commit the code :( > > Ben I'm onto something with very few manipulations. Now I have a class belonging to A listed in B too, but with the system category of A. And, if I inspect the B RPackage, there is no reference to that class. 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

Jan. 15, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30698 Home: https://github.com/pharo-project/pharo-core

Jan. 15, 2014

[pharo-project/pharo-core] 6f0bc6: 30698

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 6f0bc6535899a0cf82aea50b990f08e8c444fa1c https://github.com/pharo-project/pharo-core/commit/6f0bc6535899a0cf82aea50b… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-01-15 (Wed, 15 Jan 2014) Changed paths: R Metacello-MC.package/MetacelloConfigTemplate.class/instance/baselines/baseline10_.st R Metacello-MC.package/MetacelloConfigTemplate.class/instance/external projects/fileSystemLegacy_.st R Metacello-MC.package/MetacelloConfigTemplate.class/instance/external projects/fuelMetalevel_.st R Metacello-MC.package/MetacelloConfigTemplate.class/instance/tags/development_.st R Metacello-MC.package/MetacelloConfigTemplate.class/instance/tags/stable_.st R Metacello-MC.package/MetacelloConfigTemplate.class/instance/versions/version10_.st R Metacello-MC.package/MetacelloConfigTemplate.class/instance/versions/versionDevelopment_.st A Metacello-MC.package/MetacelloConfigTemplateExample.class/README.md A Metacello-MC.package/MetacelloConfigTemplateExample.class/class/accessing/project.st A Metacello-MC.package/MetacelloConfigTemplateExample.class/class/development support/DevelopmentSupport.st A Metacello-MC.package/MetacelloConfigTemplateExample.class/class/development support/validate.st A Metacello-MC.package/MetacelloConfigTemplateExample.class/class/loading/load.st A Metacello-MC.package/MetacelloConfigTemplateExample.class/class/loading/loadBleedingEdge.st A Metacello-MC.package/MetacelloConfigTemplateExample.class/class/loading/loadDevelopment.st A Metacello-MC.package/MetacelloConfigTemplateExample.class/class/metacello tool support/isMetacelloConfig.st A Metacello-MC.package/MetacelloConfigTemplateExample.class/class/private/baseConfigurationClassIfAbsent_.st A Metacello-MC.package/MetacelloConfigTemplateExample.class/class/private/ensureMetacello.st A Metacello-MC.package/MetacelloConfigTemplateExample.class/class/private/ensureMetacelloBaseConfiguration.st A Metacello-MC.package/MetacelloConfigTemplateExample.class/definition.st A Metacello-MC.package/MetacelloConfigTemplateExample.class/instance/accessing/customProjectAttributes.st A Metacello-MC.package/MetacelloConfigTemplateExample.class/instance/accessing/project.st A Metacello-MC.package/MetacelloConfigTemplateExample.class/instance/baselines/baseline10_.st A Metacello-MC.package/MetacelloConfigTemplateExample.class/instance/external projects/fileSystemLegacy_.st A Metacello-MC.package/MetacelloConfigTemplateExample.class/instance/external projects/fuelMetalevel_.st A Metacello-MC.package/MetacelloConfigTemplateExample.class/instance/tags/development_.st A Metacello-MC.package/MetacelloConfigTemplateExample.class/instance/tags/stable_.st A Metacello-MC.package/MetacelloConfigTemplateExample.class/instance/versions/version10_.st A Metacello-MC.package/MetacelloConfigTemplateExample.class/instance/versions/versionDevelopment_.st M RPackage-Core.package/RPackage.class/instance/file in%2Fout/fileOut.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script351.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30698.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-FilePackage.package/FilePackage.class/instance/accessing/packageInfo.st Log Message: ----------- 30698 11120 Browse code files in FileBrowser not working https://pharo.fogbugz.com/f/cases/11120 12653 MetacelloConfigTemplate is wrong https://pharo.fogbugz.com/f/cases/12653 12589 Nautilus: Package file-outs are empty https://pharo.fogbugz.com/f/cases/12589 http://files.pharo.org/image/30/30698.zip

Jan. 15, 2014

Re: [Pharo-dev] Roassal Visualization for control flow graph issues

by Goubier Thierry

Le 15/01/2014 17:07, Tudor Girba a Ã©crit : > If you pass userDefinedEdges: to a graph layout, it will only consider > those edges. This is what happens for example in the Meta Browser: the > red arrows are not taken into account. I'll keep track of that gem. Thierry > > Doru > > > On Wed, Jan 15, 2014 at 3:32 PM, Usman Bhatti <usman.bhatti(a)gmail.com > <mailto:usman.bhatti@gmail.com>> wrote: > > Alex, > > I remember to have talked to Mathieu about the making layouts ignore > some edges when drawing visualizations and I think he gave it a try > as well. I think that can be helpful in Clement's case (back jumps > are ignored in the layout). > Do you remember to have integrated something in Roassal on these > lines from Mathieu's work? > > Usman > > > > On Tue, Jan 14, 2014 at 6:20 PM, Alexandre Bergel > <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: > > Hi ClÃ©ment, > > Thanks for your nice words. > Layouts provided by Roassal are well known generic algorithm. > Creating a new layout is not complicated at all. Just subclass > ROLayout and override the hook methods. Creating a layout for > your need is not easy. Have you tried to google for a layout? If > you find one, it should be rather easy to implement it. > > Alexandre > > > On Jan 14, 2014, at 12:50 PM, ClÃ©ment Bera > <bera.clement(a)gmail.com <mailto:bera.clement@gmail.com>> wrote: > > > Hello Roassal developers, > > > > A few time ago Usman Bhatti showed me Roassal. Today I > decided to use it for my daily work on a project that aims to > optimize Pharo's methods. > > > > Firstly I am quite impressed by the quality of Roassal, I am > currently using the Roassal + Mondrian builder and I have a > visual representation which is very close to what I want after 1 > hour of work with the help of Usman. Good job guys. > > > > Here are 2 examples of what I use: > > > > exampleIfTrueIfFalse2 > > | a b | > > a := true. > > a > > ifTrue: [ > > false ifTrue: [ ^ b := 1 ] ifFalse: [ b > := 2 ] ] > > ifFalse: [ > > true ifTrue: [ b := 4 ] ifFalse: [ b := > 5 ] ]. > > ^ b > > > > <Screen Shot 2014-01-14 at 4.14.49 PM.png> > > > > Here there's one rectangle for each basic block, > entrance/exits are basic blocks with bigger borders, and borders > in red represents the "hot path", which the path the execution > flow most frequently uses (based on native code counters added > at some spots in the method by Cogit). > > > > Another example: > > > > exampleToDo > > > > 1 to: 10 do: [ :i | > > self kick: i ] > > > > <Screen Shot 2014-01-14 at 4.36.47 PM.png> > > > > Now I have a few issues with the layout. I am currently using > the narrowTreeLayout which seems to be the best for my > visualisation. > > > > issue 1: When branches merges, which is in a tree when a node > has 2 or more parents, or when I have a #ifTrue:ifFalse:, the > child is not well aligned horizontally. Here in the first > visualisation I showed, BasicBlock 5 is below but not in the > middle of Basic block 8,7 and 4 (horizontally). I put a minimal > width for each basic block to make it better but it's still not > perfect. > > issue 2: (most important issue) I cannot display back jumps > because then all the graph is missdrawn, therefore I need to > remember where they are instead of visualizing them all the time > (I cannot display the back jump from basic block 3 to basic > block 2 in the second representation. In addition, the back jump > edge, when well displayed, overlaps the basic blocks visualizations. > > > > Here is an example of what I would like for the edges and > basic block positions: > > > > <Screen Shot 2014-01-14 at 4.27.32 PM.png> > > > > As you can see, here exit is in the middle of B2 and B5 > horizontally, which is not the case in my roassal visualization. > > In addition, there's a back jump from B6 to B4 that I cannot > display (or all the visual representation goes nuts). The edge > for the back jump does not overlap with the basic blocks. In > this graph, arrows follow a grid. I don't care that arrows are > diagonals instead of a mix of horizontal and vertical lines but > I would like to be able to see nicely the back jumps as in this > graph. > > > > Do you have an idea on what layout/view options I could use > with Roassal +Mondrian to have a better result ? > > > > I tried to create my own layout but after 2 hours I > understood this cost too much time for my planning (or perhaps > I'm just too dumb to do it fast :-( ). > > > > Anyway, the representation I have now is good enough for me > to use it. But a better one would be better, especially for back > jumps :-). > > > > Thanks for any help. > > > > Clement > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow" -- 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

Jan. 15, 2014

Re: [Pharo-dev] [PROVENANCE INTERNET] Re: problems with RPackage and cie...

by Goubier Thierry

Le 15/01/2014 16:59, Esteban Lorenzano a Ã©crit : > > On 15 Jan 2014, at 16:52, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > >> Ok, testing a bit and I can't see much of a problem, except ... >> >> something really annoying ... >> >> Why is the tag disappearing if I move the only class in it to another package? > > RPackageTags are auto-removed if they become empty. Arrg! Again? And I guess the system category behind still exist? Ok, I won't hold that as a bug. It is a "feature". Just don't forget what happens if you want to reorganize classes between two packages : you're not free to do it the way you want, you have to keep at least one class in a tag to avoid seeing it disappear. 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

Jan. 15, 2014

Re: [Pharo-dev] Roassal Visualization for control flow graph issues

by Tudor Girba

If you pass userDefinedEdges: to a graph layout, it will only consider those edges. This is what happens for example in the Meta Browser: the red arrows are not taken into account. Doru On Wed, Jan 15, 2014 at 3:32 PM, Usman Bhatti <usman.bhatti(a)gmail.com>wrote: > Alex, > > I remember to have talked to Mathieu about the making layouts ignore some > edges when drawing visualizations and I think he gave it a try as well. I > think that can be helpful in Clement's case (back jumps are ignored in the > layout). > Do you remember to have integrated something in Roassal on these lines > from Mathieu's work? > > Usman > > > > On Tue, Jan 14, 2014 at 6:20 PM, Alexandre Bergel <alexandre.bergel(a)me.com > > wrote: > >> Hi ClÃ©ment, >> >> Thanks for your nice words. >> Layouts provided by Roassal are well known generic algorithm. Creating a >> new layout is not complicated at all. Just subclass ROLayout and override >> the hook methods. Creating a layout for your need is not easy. Have you >> tried to google for a layout? If you find one, it should be rather easy to >> implement it. >> >> Alexandre >> >> >> On Jan 14, 2014, at 12:50 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> >> wrote: >> >> > Hello Roassal developers, >> > >> > A few time ago Usman Bhatti showed me Roassal. Today I decided to use >> it for my daily work on a project that aims to optimize Pharo's methods. >> > >> > Firstly I am quite impressed by the quality of Roassal, I am currently >> using the Roassal + Mondrian builder and I have a visual representation >> which is very close to what I want after 1 hour of work with the help of >> Usman. Good job guys. >> > >> > Here are 2 examples of what I use: >> > >> > exampleIfTrueIfFalse2 >> > | a b | >> > a := true. >> > a >> > ifTrue: [ >> > false ifTrue: [ ^ b := 1 ] ifFalse: [ b := 2 ] ] >> > ifFalse: [ >> > true ifTrue: [ b := 4 ] ifFalse: [ b := 5 ] ]. >> > ^ b >> > >> > <Screen Shot 2014-01-14 at 4.14.49 PM.png> >> > >> > Here there's one rectangle for each basic block, entrance/exits are >> basic blocks with bigger borders, and borders in red represents the "hot >> path", which the path the execution flow most frequently uses (based on >> native code counters added at some spots in the method by Cogit). >> > >> > Another example: >> > >> > exampleToDo >> > >> > 1 to: 10 do: [ :i | >> > self kick: i ] >> > >> > <Screen Shot 2014-01-14 at 4.36.47 PM.png> >> > >> > Now I have a few issues with the layout. I am currently using the >> narrowTreeLayout which seems to be the best for my visualisation. >> > >> > issue 1: When branches merges, which is in a tree when a node has 2 or >> more parents, or when I have a #ifTrue:ifFalse:, the child is not well >> aligned horizontally. Here in the first visualisation I showed, BasicBlock >> 5 is below but not in the middle of Basic block 8,7 and 4 (horizontally). I >> put a minimal width for each basic block to make it better but it's still >> not perfect. >> > issue 2: (most important issue) I cannot display back jumps because >> then all the graph is missdrawn, therefore I need to remember where they >> are instead of visualizing them all the time (I cannot display the back >> jump from basic block 3 to basic block 2 in the second representation. In >> addition, the back jump edge, when well displayed, overlaps the basic >> blocks visualizations. >> > >> > Here is an example of what I would like for the edges and basic block >> positions: >> > >> > <Screen Shot 2014-01-14 at 4.27.32 PM.png> >> > >> > As you can see, here exit is in the middle of B2 and B5 horizontally, >> which is not the case in my roassal visualization. >> > In addition, there's a back jump from B6 to B4 that I cannot display >> (or all the visual representation goes nuts). The edge for the back jump >> does not overlap with the basic blocks. In this graph, arrows follow a >> grid. I don't care that arrows are diagonals instead of a mix of horizontal >> and vertical lines but I would like to be able to see nicely the back jumps >> as in this graph. >> > >> > Do you have an idea on what layout/view options I could use with >> Roassal +Mondrian to have a better result ? >> > >> > I tried to create my own layout but after 2 hours I understood this >> cost too much time for my planning (or perhaps I'm just too dumb to do it >> fast :-( ). >> > >> > Anyway, the representation I have now is good enough for me to use it. >> But a better one would be better, especially for back jumps :-). >> > >> > Thanks for any help. >> > >> > Clement >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 15, 2014

Re: [Pharo-dev] [PROVENANCE INTERNET] Re: problems with RPackage and cie...

by Esteban Lorenzano

On 15 Jan 2014, at 16:52, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > Ok, testing a bit and I can't see much of a problem, except ... > > something really annoying ... > > Why is the tag disappearing if I move the only class in it to another package? RPackageTags are auto-removed if they become empty. Esteban > > Thierry > > Le 15/01/2014 16:41, Goubier Thierry a Ã©crit : >> Do you have an issue on that? Or does it happens just when moving >> classes from any package to another? >> >> Thierry >> >> Le 15/01/2014 16:34, Alexandre Bergel a Ã©crit : >>> Hi! >>> >>> We are constantly facing problems when moving classes between >>> packages. This is highly discouraging. This involves tricky parts of >>> the system that both difficult to understand and to debug. >>> >>> Alexandre >>> >> > > -- > 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 >

Jan. 15, 2014

Re: [Pharo-dev] problems with RPackage and cie...

by Benjamin

We are also facing some RPackage cache not in sync anymore with system leading to the impossibility to commit the code :( Ben On 15 Jan 2014, at 12:56, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > > > Le 15/01/2014 16:46, Alexandre Bergel a Ã©crit : >>> Do you have an issue on that? Or does it happens just when moving classes from any package to another? >> >> I do not know. I do not see on https://pharo.fogbugz.comhow I can list issues that contains the RPackage and that are still open. >> >> The problems we are facing usually involves having more than one browser opened, dragging classes from one browser to another browser. Hard to be more accurate because students are calling me to the rescue when they are already in the mess. We can put images online if this help. > > Ok, this could be in Nautilus. > > I was drag and dropping in AltBrowser and couldn't see anything wrong, but I'm not exercising the same code paths on RPackage than Nautilus does. > > As far as AltBrowser goes, recompiling the class with a new system category is picked up fine (apart from the disappearing tag). > > Thierry > >> Alexandre >> >> >>> >>> Thierry >>> >>> Le 15/01/2014 16:34, Alexandre Bergel a Ã©crit : >>>> Hi! >>>> >>>> We are constantly facing problems when moving classes between packages. This is highly discouraging. This involves tricky parts of the system that both difficult to understand and to debug. >>>> >>>> Alexandre >>>> >>> >>> -- >>> 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 >> > > -- > 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

Jan. 15, 2014