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

Re: [Pharo-project] Senders from package(s)

by Schwab,Wilhelm K

Were you thinking of something like: ( ( BrowserEnvironment new forPackageNames:#( 'Gizmo' ) ) label:'Fix these'; referencesTo:#next ) open. ? ________________________________________ 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: Friday, August 13, 2010 1:25 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Senders from package(s) http://stackoverflow.com/questions/3290225/restrict-querying-for-senders-to… On Friday, August 13, 2010, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Lukas, > > As a side effect of searching, I found that ShoutPier lives in Pier-add-ons. Otherwise, it's information overload on browser scoping; can you narrow it down? > > 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: Friday, August 13, 2010 11:50 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Senders from package(s) > > Check "Pharo by Example" and stackoverflow.com, there is a > chapter/question on exactly that. > > Lukas > > On Friday, August 13, 2010, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: >> Stef, >> >> That sounds great, but I'm confused about the menus. The offending code is all one package with lots of branches: stuff like Gizmo-base, Gizmo-devices-gas-analyzer, Gizmo-oxygen-sensor, etc. How can I open a scoped browser on all of Gizmo? >> >> Bill >> >> >> >> ________________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] >> Sent: Friday, August 13, 2010 6:21 AM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] Senders from package(s) >> >> yes use the refactoring browser and open a scope >> refactor menu >> you get a yellow browser where all the operations are scoped >> >> On Aug 13, 2010, at 12:37 AM, Schwab,Wilhelm K wrote: >> >>> Hello all, >>> >>> Is there a way to browse all senders of particular selector, scoped to one or more packages? >>> >>> Bill >>> >>> >>> _______________________________________________ >>> 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 >> > > -- > Lukas Renggli > 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli 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

Aug. 13, 2010

Re: [Pharo-project] Senders from package(s)

by Lukas Renggli

http://stackoverflow.com/questions/3290225/restrict-querying-for-senders-to… On Friday, August 13, 2010, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Lukas, > > As a side effect of searching, I found that ShoutPier lives in Pier-add-ons. Â Otherwise, it's information overload on browser scoping; can you narrow it down? > > 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: Friday, August 13, 2010 11:50 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Senders from package(s) > > Check "Pharo by Example" and stackoverflow.com, there is a > chapter/question on exactly that. > > Lukas > > On Friday, August 13, 2010, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: >> Stef, >> >> That sounds great, but I'm confused about the menus. Â The offending code is all one package with lots of branches: stuff like Gizmo-base, Gizmo-devices-gas-analyzer, Gizmo-oxygen-sensor, etc. Â How can I open a scoped browser on all of Gizmo? >> >> Bill >> >> >> >> ________________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] >> Sent: Friday, August 13, 2010 6:21 AM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] Senders from package(s) >> >> yes use the refactoring browser and open a scope >> Â Â Â Â refactor menu >> Â Â Â Â you get a yellow browser where all the operations are scoped >> >> On Aug 13, 2010, at 12:37 AM, Schwab,Wilhelm K wrote: >> >>> Hello all, >>> >>> Is there a way to browse all senders of particular selector, scoped to one or more packages? >>> >>> Bill >>> >>> >>> _______________________________________________ >>> 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 >> > > -- > Lukas Renggli > 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

Aug. 13, 2010

Re: [Pharo-project] Senders from package(s)

by Schwab,Wilhelm K

Lukas, As a side effect of searching, I found that ShoutPier lives in Pier-add-ons. Otherwise, it's information overload on browser scoping; can you narrow it down? 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: Friday, August 13, 2010 11:50 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Senders from package(s) Check "Pharo by Example" and stackoverflow.com, there is a chapter/question on exactly that. Lukas On Friday, August 13, 2010, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Stef, > > That sounds great, but I'm confused about the menus. The offending code is all one package with lots of branches: stuff like Gizmo-base, Gizmo-devices-gas-analyzer, Gizmo-oxygen-sensor, etc. How can I open a scoped browser on all of Gizmo? > > Bill > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] > Sent: Friday, August 13, 2010 6:21 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Senders from package(s) > > yes use the refactoring browser and open a scope > refactor menu > you get a yellow browser where all the operations are scoped > > On Aug 13, 2010, at 12:37 AM, Schwab,Wilhelm K wrote: > >> Hello all, >> >> Is there a way to browse all senders of particular selector, scoped to one or more packages? >> >> Bill >> >> >> _______________________________________________ >> 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 > -- Lukas Renggli 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

Aug. 13, 2010

Re: [Pharo-project] Senders from package(s)

by Lukas Renggli

Check "Pharo by Example" and stackoverflow.com, there is a chapter/question on exactly that. Lukas On Friday, August 13, 2010, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Stef, > > That sounds great, but I'm confused about the menus. Â The offending code is all one package with lots of branches: stuff like Gizmo-base, Gizmo-devices-gas-analyzer, Gizmo-oxygen-sensor, etc. Â How can I open a scoped browser on all of Gizmo? > > Bill > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] > Sent: Friday, August 13, 2010 6:21 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Senders from package(s) > > yes use the refactoring browser and open a scope > Â Â Â Â refactor menu > Â Â Â Â you get a yellow browser where all the operations are scoped > > On Aug 13, 2010, at 12:37 AM, Schwab,Wilhelm K wrote: > >> Hello all, >> >> Is there a way to browse all senders of particular selector, scoped to one or more packages? >> >> Bill >> >> >> _______________________________________________ >> 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 > -- Lukas Renggli www.lukas-renggli.ch

Aug. 13, 2010

[Pharo-project] File out with syntax highlighting

by Schwab,Wilhelm K

Hello all, I did a little more digging toward my goal of exporting a given package's code in syntax-highlighted form. Solutions suggested below include Squeak's copy-to-html and Shout-Pier. The copy code was removed from Pharo. Are the pieces still more or less available, or did a lot of code get tossed? I envision a small export filter that takes a package name and writes html for every method that belongs in the package, so I don't care about the menu/command integration, only about how practical it would be to use the pieces in the image to build the filter. The other option is Pier-Shout. Where does that live? It is not my first choice, but if nothing else, it might fill in the missing pieces allowing me to build what I want. Bill http://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg21418.ht…

Aug. 13, 2010

Re: [Pharo-project] Contributors page (was little pictures of you)

by Miguel Enrique CobÃ¡ MartÃnez

El vie, 13-08-2010 a las 08:15 +0200, Adrian Lienhard escribiÃ³: > On Aug 13, 2010, at 07:58 , laurent laffont wrote: > > > On Fri, Aug 13, 2010 at 4:59 AM, Serge Stinckwich < > > serge.stinckwich(a)gmail.com> wrote: > > > >> Nice ! But you know i'm not a big contributor to Pharo. > >> > >> > > The page is "Contributors", not "Big contributors" :) I wonder if I should > > change it to "Contributors & Users". Users are really important because it > > shows Pharo is used in real world. > > > > One of the first question when I show Pharo is: who use it ? It seems people > > don't care if it's good or not. Knowing that there's users bring confidence. > > Yes, but for the users we have the success stories page. I would separate the two. I suggest to move the contributors page with pictures from About to Community and only list contributors but not users. About users of Pharo I want to know the company (btw, there's bombardier.com in the list now!) and if possible what they do, but I don't need to know how these people look like. Seeing the face of somebody is interesting if we discuss and work together. +1 -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Aug. 13, 2010

Re: [Pharo-project] [ANN] Pharo Metacello Universes

by Miguel Enrique CobÃ¡ MartÃnez

El vie, 13-08-2010 a las 14:07 +0200, StÃ©phane Ducasse escribiÃ³: > > > > > > 1. Add to the image (maybe SystemVersion current metacelloRepository) a > > getter that returns the standardized string pointing to the correct > > metacello repository for the image: > > > > SystemVersion>>metacelloRepository > > ^ 'MetaRepoForPharo12' > > > > And then all the series of Pharo releases based on that PharoCore image > > will point to MetaRepoPharo12 (PharoCore 1.2, PharoCore 1.2.1, PharoCore > > 1.2.2, Pharo 1.2, Pharo 1.2.1, Pharo 1.2.4, etc. They are the same > > release family and supposedly "binary" compatible). > > > > For PharoCore 1.3, that string should be changed to > > > > SystemVersion>>metacelloRepository > > ^ 'MetaRepoForPharo13' > > > > and so on. > > ok > > > > > > Metacello > > ------------- > > This is the most difficult part. > > - Right now, Metacello hardcodes repository paths in the references to > > other projects. This isn't bad, but an alternative should be provided. > > That is, when referencing external projects like: > > > > project: 'Refactoring-Core' with: [ > > spec > > className: 'ConfigurationOfRefactoringBrowser'; > > loads: #('Refactoring-Core' ); > > file: 'ConfigurationOfRefactoringBrowser'; > > repository: 'http://www.squeaksource.com/MetacelloRepository' ]; > > > But a spec is an object so we could have a visitor going over and doing the automatic > rewrite for us. > > > Of course nothing prevents for a configuration to reference a project > > outside the "universe" repository, but that is a decision of the > > maintainer. > > No this is a dogma. NO NO NO reference outside the repository. > NOT A SINGLE ONE. NEVER. > We want 100% self contained distribution. > > Stef :) Ok. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Aug. 13, 2010

Re: [Pharo-project] [ANN] Pharo Metacello Universes

by Miguel Enrique CobÃ¡ MartÃnez

El vie, 13-08-2010 a las 15:53 +0200, Mariano Martinez Peck escribiÃ³: > > > > > > > and > > > > http://www.squeaksource.com/Pharo11Metacello > > > > I didn't send any email because I was not sure about certain > points. I > > want to discuss them now: > > > > 1) Problem: know which project version must be used for a > particular > > pharo version. There are two solutions: > > > > a) When a developer commites ConfigurationOf to a particular > repo, it > > makes sure the #lastVersion answer the correct one. > > b) When a developer commites ConfigurationOf to a particular > repo, it > > makes sure the #load will load the correct version. > > > > I think that for Pharo 1.0 and Pharo 1.1 there is little we > can do as > they are already outhere. > > No...I think it is possible. It doesn't care they are out there. > Continue reaeding my answer. > > > The will continue referencing > MetacelloRepository forever. And in that repo there are all > the possible > dependencies they need. So they need no change in the > infrastructure. > > Now, if we forget about 1.0 and 1.1 and concentrate in 1.2, > then we can > make a big change. I propose: > > I wouldn't forget about 1.0 and 1.1 > > > 1. Add to the image (maybe SystemVersion current > metacelloRepository) a > getter that returns the standardized string pointing to the > correct > metacello repository for the image: > > SystemVersion>>metacelloRepository > ^ 'MetaRepoForPharo12' > > And then all the series of Pharo releases based on that > PharoCore image > will point to MetaRepoPharo12 (PharoCore 1.2, PharoCore 1.2.1, > PharoCore > 1.2.2, Pharo 1.2, Pharo 1.2.1, Pharo 1.2.4, etc. They are the > same > release family and supposedly "binary" compatible). > > For PharoCore 1.3, that string should be changed to > > SystemVersion>>metacelloRepository > ^ 'MetaRepoForPharo13' > > and so on. > > That is the base image and derived images for Pharo. > > Now to the tools, Gofer, GoferProjectLoader and Metacello. > > Gofer > ------ > add a universe method (this name is overloaded so a better > name is > wanted, maybe metacelloRepository or pharoRepository) so that > we can do: > > Gofer new > universe; "or metacelloRepository or pharoRepository" > project: 'ConfigurationOfMagma"; > load. > > The universe (or whatever its name be) just uses SystemVersion > current > metacelloRepository to get everything from the correct > repository. > > GoferProjectLoader > ------------------ > This could be improved to get every package (that is, a > metacello > configuration) from the correct repository by delegating to > gofer new > universe and avoiding to resolve itself the repository for the > image. > Also, if GoferProjectLoader is part of the core image, then > maybe gofer > shouldn't have the universe functionality, but > GoferProjectLoader should > have it, and only use gofer to fetch the monticello packages. > This way I > think is cleaner, because Gofer is only used as a medium to > get things > and knows nothing about universes and repositories depending > on a given > image release. > > > All you mention here has sense to LOAD projects. And I agree this > changes could be only for Pharo 1.2 (like the change in > SystemVersion). > But someone should be able to do everything by code. For example, in > Pharo 1.0 I could do: > > Gofer new > repository: 'pharoRepository10" > project: 'ConfigurationOfMagma"; > load. > > But I think this is a further step. We need to FIRST think how to > WRITE the configuration. And how to load it with Metacello. I don't > care Gofer neither Loader for the first step. > > Metacello > ------------- > This is the most difficult part. > - Right now, Metacello hardcodes repository paths in the > references to > other projects. This isn't bad, but an alternative should be > provided. > That is, when referencing external projects like: > > project: 'Refactoring-Core' with: [ > spec > className: 'ConfigurationOfRefactoringBrowser'; > loads: #('Refactoring-Core' ); > file: 'ConfigurationOfRefactoringBrowser'; > repository: > 'http://www.squeaksource.com/MetacelloRepository' ]; > > > it should understand the alternative: > > project: 'Refactoring-Core' with: [ > spec > > universe; "Or metacelloRepository or whatever" > className: 'ConfigurationOfRefactoringBrowser'; > loads: #('Refactoring-Core' ); > > file: 'ConfigurationOfRefactoringBrowser' ]; > > So that a configuration could resolve all their references > from the same > pharo repository. This implies of course that the maintainer > assures > that all the referenced ConfigurationOfXXX are actually > available in the > repository referenced by SystemVersion current > metacelloRepository. > > > But we need to change that...in addition, there are confs that also > work in squeak...soo.. > > Of course nothing prevents for a configuration to reference a > project > outside the "universe" repository, but that is a decision of > the > maintainer. > > I think that this is the least disruptive way of integrating > Metacello > Repositories to next Pharo release. > > This preserves backwards compatibility and eases the way of > installing > packages in future releases. > > What do you think? > > I think that we should do is a piece of code that does the following: > > - Take a ConfiguraitonOfXXX and do a "publish in Pharo Repository" > - This can propmt which Pharo version, or directly which > PharoRepository > - Then it will ask which VERSION should be loaded in the already > selected Pharo version > - It should be asked WHICH group (optional) > > Once this is done, the code has to do the following: > > - Iterates all the project and packages referenced and COPY ALL OF > THEM into the same repository. Or maybe we can have another repo. > This will copy all the .mzc of the project and its dependencies. With > this you will make sure that you have EVERYTHING you need to load it. > > - take that ConfigurationOfXXX and automatically compile a class side > #load that based in your answers, does the correct job. > In addition, this method should do a repositoryOverride: with the > selected repository. > Example: > > load > | version | > version := self project version: selectedVersion. > version repositoryOverrides: selectedPharoRepository. > version load: selectedGroup. > > Maybe it can implement a particular load: that recieves the common > parameter > > > > Then, if you are in Pharo 1.0 the only thing you have to do is to > explore the repository PharoRepository10 and browse the confs....you > select the one you want and load it (with Gofer or Monticello > Browser). Once that is done, you just evaluate: > > ConfiguarationOfXXX load. > > and that's all. > > What do you think ? I like the idea, but it requires a lot of effort in building the tool, that does that. Maybe INRIA could sponsor some student hours just to build this tool so that is ready for the 1.2 release. > Dale? > > > > Cheers > > -- > > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > 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 -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Aug. 13, 2010

Re: [Pharo-project] [SPAM] Re: Gravatar and Website (was little pictures of you )

by laurent laffont

On Fri, Aug 13, 2010 at 5:03 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > > On 13 Aug 2010, at 14:03, laurent laffont wrote: > > > On Fri, Aug 13, 2010 at 12:55 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > > send them the code for pharo :) > > > > > > Kata for better code ? (sorry German) > > > > |md5 url| > > md5 := MD5 new hashStream: (ReadStream on: 'gsa(a)arsol.net'). > > url := String streamContents: [:aStream| > > aStream > nextPutAll: 'http://www.gravatar.com/avatar/'. > > md5 do: > [:aByte| > > > aStream nextPutAll: aByte hex asLowercase]]. > > (ImageMorph fromStream: > > (url asUrl retrieveContents contentStream)) openInWorld. > > > > Laurent > > I really like code that speaks for itself, like this example ! > Great, Laurent. > > It can even be written shorter, like this: > > | md5 url | > md5 := MD5 hashMessage: 'gsa(a)arsol.net'. > url := ('http://www.gravatar.com/avatar/', md5 hex) asUrl. > (ImageMorph fromStream: url retrieveContents contentStream) openInWorld. > I was looking for such brevity, cool ! Laurent > > Sven > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 13, 2010

Re: [Pharo-project] [Moose-dev] Re: [Survey] Assess the cycles in your software

by Tudor Girba

I apologize for not doing it earlier. I will do it until Tuesday. Cheers, Doru On 13 Aug 2010, at 16:33, Laval Jannik wrote: > Hi all, > > A (second) reminder for people who wants to participate. > We need help from the community. > > Cheers, > Jannik > > On Jul 19, 2010, at 08:36 , Laval Jannik wrote: > >> Hi Pharoers, and Smalltalkers in general, >> >> Have you seen waited to assess the cycles in your software? Now you >> can :) >> >> We request some of you to perform an experiment using DSM to see >> your software package structure and to fix cycles between packages. >> Our tool shows dependencies between packages and highlight some bad >> dependencies generating structure cycles. It also helps to >> understand dependencies. >> >> Your goal is to fill a survey using our tool. >> I prepared a mini-tutorial about DSM and eDSM. It can help you to >> understand the visualization tool. >> >> To ease the use of our tool, I loaded it in a PharoCore1.2. And >> there are two archives available: >> - the first contains an image with our tool with a model of Pharo >> loaded in it, so you can play with our tool on pharo itself. It can >> be downloaded here: http://dl.dropbox.com/u/7739334/ >> dsmWithPharo.zip. Pay attention, the image is slow. >> - the second contains the same thing without the model of Pharo. >> Here, you have to load your code, then populate a moose model and >> use the tool. It can be downloaded here: http://dl.dropbox.com/u/7739334/dsmWithoutPharo.zip >> The two archives contain the tutorial and the survey. If you are a >> pharo integrator, we suggest you to take the one with Pharo model >> loaded, else the other. >> >> To use our tool, load your tool in Pharo. Then do "MoosePanel >> open", and import your software in Moose by "import from Smalltalk >> image". When it is imported, select your project in the list on the >> left of MoosePanel, and select "all model packages" on the list on >> center. >> >> Then, you have two choices: >> - you can scan all your project: right click on "all model >> packages" and do DSM. >> - or select "all model packages" then select some packages in the >> next list and right click, do DSM. >> >> After that, you can perform the survey (with reading of the >> tutorial). We need your answers for the end of August. So, you have >> two months to do it. >> >> If you have any question, just let me know. >> >> Best regards, >> Jannik. >> >> --- >> Jannik Laval >> PhD Student - Rmod Team - INRIA >> Certified Project Management Associate (IPMA) >> http://www.jannik-laval.eu >> http://rmod.lille.inria.fr >> --- >> > > --- > Jannik Laval > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "What is more important: To be happy, or to make happy?"

Aug. 13, 2010