March 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Q: is there a way to get the classes referenced by a class?

by Esteban Lorenzano

Thank you, Miguel and Alexandre... I'm looking into it :) Cheers, Esteban On 2010-03-01 16:59:23 -0300, Alexandre Bergel <alexandre(a)bergel.eu> said: > > > Hi Esteban, > > I made a small extension of O2 that shows external dependencies. It is > not perfect, but I find it useful. I attached some screenshots. > The second screenshot shows that the package Network-Kernel has 6 > methods that references the package ToolBuilder-Kernel. > Right clicking on the mondrian node opens a menu that enable you to > browse the method. I use this tool to make sure I do not have any > unwanted dependencies. > > It works on PharoCore 1.1. To load it: > > #('DependencyView') > do: [:t | > | name | > name := 'ConfigurationOf', t. > Gofer new > squeaksource: 'MetacelloRepository'; > package: name; > load. > ((Smalltalk at: name asSymbol) project perform: #lastVersion) load ]. > > Cheers, > Alexandre > > > > <image> > > <image> > > > On 1 Mar 2010, at 15:58, Esteban Lorenzano wrote: > >> Hi, >> I'm trying to get a "dependency map" of a certain project (playing >> with >> pavel's kernel image, I'm trying to figure out how to feed it with all >> needed dependences). >> What I'm doing now is very inneficient (usign #allCallsOn and >> reversing >> the search), and I'm sure there should be something better... >> >> Thanks, >> Esteban >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 1, 2010

Re: [Pharo-project] about code formatting in pharo

by Lukas Renggli

You can try with the attached patches. That should put the comments inside the cascade. Since there are no tests for this new behavior (it doesn't break any of the existing ones) I am reluctant of including them right away. It could well be that with these patches in some edge cases comments are lost or suddenly appear twice. Lukas On 1 March 2010 19:32, Lukas Renggli <renggli(a)gmail.com> wrote: > Excellent, thanks for the test case. I will have a look as soon as I get home. > > Lukas > > On Monday, March 1, 2010, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: >> Lukas, >> >> File in the attached and then reformat it. Â I have to admit there has been improvement; at least the comments remain within the cascade of which they were originally a part. Â Still, they end up out of order with respect to the reformatted code, which is devastating to what I am trying to accomplish. Â These are directly analogous to the types of comments that sat (in longer cascades) for several years only to save my back side last year. >> >> Bill >> >> >> ________________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Lukas Renggli [renggli(a)gmail.com] >> Sent: Monday, March 01, 2010 7:47 AM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] about code formatting in pharo >> >>> I'm not complaining; it's simply a fact, and I'm not the only one observing it. Â Links were given here some time back. >> >> Sorry, but this is only a fact if you provide unit tests (or at least >> a couple of examples) that fail in the latest code base. Otherwise >> simply nobody cares. >> >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > Lukas Renggli > http://www.lukas-renggli.ch > -- Lukas Renggli http://www.lukas-renggli.ch

March 1, 2010

Re: [Pharo-project] Q: is there a way to get the classes referenced by a class?

by Alexandre Bergel

Hi Esteban, I made a small extension of O2 that shows external dependencies. It is not perfect, but I find it useful. I attached some screenshots. The second screenshot shows that the package Network-Kernel has 6 methods that references the package ToolBuilder-Kernel. Right clicking on the mondrian node opens a menu that enable you to browse the method. I use this tool to make sure I do not have any unwanted dependencies. It works on PharoCore 1.1. To load it: #('DependencyView') do: [:t | | name | name := 'ConfigurationOf', t. Gofer new squeaksource: 'MetacelloRepository'; package: name; load. ((Smalltalk at: name asSymbol) project perform: #lastVersion) load ]. Cheers, Alexandre On 1 Mar 2010, at 15:58, Esteban Lorenzano wrote: > Hi, > I'm trying to get a "dependency map" of a certain project (playing > with > pavel's kernel image, I'm trying to figure out how to feed it with all > needed dependences). > What I'm doing now is very inneficient (usign #allCallsOn and > reversing > the search), and I'm sure there should be something better... > > Thanks, > Esteban > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 1, 2010

Re: [Pharo-project] about code formatting in pharo

by StÃ©phane Ducasse

It makes sense. Stef On Mar 1, 2010, at 7:23 PM, Schwab,Wilhelm K wrote: > Stef, > > To that reasoned response I will add that I do not at all care what others choose to use in their code; I simply don't want a formatter applied to my code that lives in my image. Whatever works for you and others in the core is fine by me. > > Bill > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Dale Henrichs > Sent: Monday, March 01, 2010 1:07 PM > To: Pharo-project(a)lists.gforge.inria.fr > Cc: Pharo-project Development > Subject: Re: [Pharo-project] about code formatting in pharo > > Stef, > > I really like formatters, but as the discussion has already shown, there isn't one format that fits everyone's definition of beauty/readability. > > Personally I am willing to use any formatter that saves me from having to hand edit code for format, but I think I am in the minority. > > Presumably the formatter can be configured to produce different output formats ... if the format operation avoided dirtying the method, then supporting multiple formats would be less onerous ... I can reformat a method in my image using my formatter so that I can read someone else's code is pretty useful...Along the same line, having Monticello use the canonical formatter to format code when writing out mcz files would eliminate format issues for saved mczs (note that for source code comparison in Monticello, the canonical formatter should be used on both strings), finally it might make sense to format code on read, so that noone will ever have to know that their chosen format is not the canonical one:) ... > > Just some thoughts that might minimize the impact of "format wars"... > > Dale > ----- "stephane ducasse" <stephane.ducasse(a)free.fr> wrote: > > | Hi guys > | > | I would like to build a set of canonical code formatting convention > | for Pharo. > | I need your help. Now take time before replying :) I would like to > | structure the discussion and proceed step by step. So at max I would > | like to discuss one or two formatting approach per mail. > | Once we agree I would like to define a wiki page. > | > | > | **Space after : rule > | ============= > | for example I would like to always have a space after a : > | > | classes := Smalltalk allClasses select:[:aClass| > | (aClass class includesSelector: #cleanUp) > | or:[aClass class includesSelector: #cleanUp:] > | ]. > | > | -> > | > | > | classes := Smalltalk allClasses select: [:aClass| > | (aClass class includesSelector: #cleanUp) > | or: [aClass class includesSelector: #cleanUp:] > | ]. > | > | > | **Block arg rule > | ============= > | Do we want a space before and after block arg > | > | Smalltalk allClasses select: [:aClass :method| > | > | -> Smalltalk allClasses select: [ :aClass :method | > | > | > | ** selector or block indented compared to receiver > | ======================================= > | > | Finally do we follow kent block ideas? > | > | classes := Smalltalk allClasses select: [:aClass| > | (aClass class includesSelector: #cleanUp) > | or: [aClass class includesSelector: #cleanUp:] > | ]. > | > | -> > | classes := Smalltalk allClasses > | select: [:aClass| (aClass class includesSelector: #cleanUp) > | or: [aClass class includesSelector: > | #cleanUp:]]. > | > | Stef > | _______________________________________________ > | Pharo-project mailing list > | Pharo-project(a)lists.gforge.inria.fr > | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 1, 2010

Re: [Pharo-project] Polymorph fixes

by StÃ©phane Ducasse

Thanks. I will give a try but may be we have a bug in scriptLoader :) Stef On Mar 1, 2010, at 6:52 PM, Gary Chambers wrote: > A few fixes on SqueakSource. > > Polymorph-Widgets-gvc.24 > Polymorph-Tools-Diff-gvc.24 > > Notably: > > Table layout of submorphs with #shrinkWrap attributes. > Themeing of menu item text colours to help Hilaire in his Sugar theme efforts. ThemeSettings integration left for another time... > Wrong "sides" for "compare to current" when using diff tools in change sets (versions browser etc.). > Prevention of window dragging from submorphs promoted from StandardWindow to SystemWindow (deals with oddities when click-dragging from submorphs... offset would be wrong and window "jumps"). > Wrong colours for faded background windows in Watery themes. > Fix colours in W2K theme (requires class-side reinitialisation of defaultSettings. Do "UIThemeW2K defaultSettings: nil" before changing theme). > Toolbars now Panel-based to adapt to pane colour. > DockingBar based menus now deal with mouseFocus correctly. > > > Regards, Gary > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 1, 2010

Re: [Pharo-project] Q: is there a way to get the classes referenced by a class?

by Miguel Enrique CobÃ¡ Martinez

El lun, 01-03-2010 a las 16:14 -0300, Esteban Lorenzano escribiÃ³: > which one? > Sorry :) > > Check this thread: > > > > It hast tools from Lukas and from HernÃ¡n Morales http://lists.squeakfoundation.org/pipermail/magma/2010-January/001493.html -- Miguel CobÃ¡ http://miguel.leugim.com.mx

March 1, 2010

Re: [Pharo-project] Q: is there a way to get the classes referenced by a class?

by Esteban Lorenzano

which one? On 2010-03-01 16:02:33 -0300, Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> said: > El lun, 01-03-2010 a las 15:58 -0300, Esteban Lorenzano escribiÃ³: >> Hi, >> I'm trying to get a "dependency map" of a certain project (playing with >> pavel's kernel image, I'm trying to figure out how to feed it with all >> needed dependences). >> What I'm doing now is very inneficient (usign #allCallsOn and reversing >> the search), and I'm sure there should be something better... >> >> Thanks, >> Esteban > > Check this thread: > > It hast tools from Lukas and from HernÃ¡n Morales > > Cheers

March 1, 2010

Re: [Pharo-project] Q: is there a way to get the classes referenced by a class?

by Miguel Enrique CobÃ¡ Martinez

El lun, 01-03-2010 a las 15:58 -0300, Esteban Lorenzano escribiÃ³: > Hi, > I'm trying to get a "dependency map" of a certain project (playing with > pavel's kernel image, I'm trying to figure out how to feed it with all > needed dependences). > What I'm doing now is very inneficient (usign #allCallsOn and reversing > the search), and I'm sure there should be something better... > > Thanks, > Esteban Check this thread: It hast tools from Lukas and from HernÃ¡n Morales Cheers -- Miguel CobÃ¡ http://miguel.leugim.com.mx

March 1, 2010

[Pharo-project] Q: is there a way to get the classes referenced by a class?

by Esteban Lorenzano

Hi, I'm trying to get a "dependency map" of a certain project (playing with pavel's kernel image, I'm trying to figure out how to feed it with all needed dependences). What I'm doing now is very inneficient (usign #allCallsOn and reversing the search), and I'm sure there should be something better... Thanks, Esteban

March 1, 2010

Re: [Pharo-project] about code formatting in pharo

by Schwab,Wilhelm K

Gary, What is a "compact format?" If it reproduces _exactly_ what I typed (e.g. lossless compression) then I suppose there is no reason to object. If it changes what I see, then I would have to ask for cost/benfit information. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Gary Chambers Sent: Monday, March 01, 2010 1:45 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] about code formatting in pharo Just the issue of "resaved" code then... I suggest a compact format regardelss with "on view" formatting to the user's liking.... Regards, Gary ----- Original Message ----- From: "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Monday, March 01, 2010 6:29 PM Subject: Re: [Pharo-project] about code formatting in pharo > Gary, > > That's pretty much what I just proposed based on your suggestion and a > "null" formatter. However it is implemented, the idea is to render the > code using a formatter so the code itself is not altered. That will > hopefully give everyone what they want. Stef, will that work? > > Bill > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr > [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Gary > Chambers > Sent: Monday, March 01, 2010 1:26 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] about code formatting in pharo > > Perhaps a setting to mark saved code "as is" then? Along with an override > for people who want formatting regardless? > > Regards, Gary > > ----- Original Message ----- > From: "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> > To: <Pharo-project(a)lists.gforge.inria.fr>; <dale.henrichs(a)gemstone.com> > Sent: Monday, March 01, 2010 6:23 PM > Subject: Re: [Pharo-project] about code formatting in pharo > > >> Stef, >> >> To that reasoned response I will add that I do not at all care what >> others >> choose to use in their code; I simply don't want a formatter applied to >> my >> code that lives in my image. Whatever works for you and others in the >> core is fine by me. >> >> Bill >> >> >> -----Original Message----- >> From: pharo-project-bounces(a)lists.gforge.inria.fr >> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Dale >> Henrichs >> Sent: Monday, March 01, 2010 1:07 PM >> To: Pharo-project(a)lists.gforge.inria.fr >> Cc: Pharo-project Development >> Subject: Re: [Pharo-project] about code formatting in pharo >> >> Stef, >> >> I really like formatters, but as the discussion has already shown, there >> isn't one format that fits everyone's definition of beauty/readability. >> >> Personally I am willing to use any formatter that saves me from having to >> hand edit code for format, but I think I am in the minority. >> >> Presumably the formatter can be configured to produce different output >> formats ... if the format operation avoided dirtying the method, then >> supporting multiple formats would be less onerous ... I can reformat a >> method in my image using my formatter so that I can read someone else's >> code is pretty useful...Along the same line, having Monticello use the >> canonical formatter to format code when writing out mcz files would >> eliminate format issues for saved mczs (note that for source code >> comparison in Monticello, the canonical formatter should be used on both >> strings), finally it might make sense to format code on read, so that >> noone will ever have to know that their chosen format is not the >> canonical >> one:) ... >> >> Just some thoughts that might minimize the impact of "format wars"... >> >> Dale >> ----- "stephane ducasse" <stephane.ducasse(a)free.fr> wrote: >> >> | Hi guys >> | >> | I would like to build a set of canonical code formatting convention >> | for Pharo. >> | I need your help. Now take time before replying :) I would like to >> | structure the discussion and proceed step by step. So at max I would >> | like to discuss one or two formatting approach per mail. >> | Once we agree I would like to define a wiki page. >> | >> | >> | **Space after : rule >> | ============= >> | for example I would like to always have a space after a : >> | >> | classes := Smalltalk allClasses select:[:aClass| >> | (aClass class includesSelector: #cleanUp) >> | or:[aClass class includesSelector: #cleanUp:] >> | ]. >> | >> | -> >> | >> | >> | classes := Smalltalk allClasses select: [:aClass| >> | (aClass class includesSelector: #cleanUp) >> | or: [aClass class includesSelector: #cleanUp:] >> | ]. >> | >> | >> | **Block arg rule >> | ============= >> | Do we want a space before and after block arg >> | >> | Smalltalk allClasses select: [:aClass :method| >> | >> | -> Smalltalk allClasses select: [ :aClass :method | >> | >> | >> | ** selector or block indented compared to receiver >> | ======================================= >> | >> | Finally do we follow kent block ideas? >> | >> | classes := Smalltalk allClasses select: [:aClass| >> | (aClass class includesSelector: #cleanUp) >> | or: [aClass class includesSelector: #cleanUp:] >> | ]. >> | >> | -> >> | classes := Smalltalk allClasses >> | select: [:aClass| (aClass class includesSelector: #cleanUp) >> | or: [aClass class includesSelector: >> | #cleanUp:]]. >> | >> | Stef >> | _______________________________________________ >> | Pharo-project mailing list >> | Pharo-project(a)lists.gforge.inria.fr >> | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 1, 2010