September 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Is there a way to use rename refactor while preserving whitespace formatting in refactored methods?

by StÃ©phane Ducasse

Lukas Gwenael changed the RBParser and AST to preserve code formatting. He never understood why nobody did look at what he did. Now when marcus will be in the team I would really like to have a look so that the work on gwenael is not lost because he worked 4 months on that. But if someone is interested it would be good to check. Stef On Sep 20, 2009, at 9:16 AM, Lukas Renggli wrote: >> Hi, I am using Pharo with the default browser, which is the >> OmniBrowser. When I >> right-click on a message name in the right-most panel and choose >> "rename >> refactor" from the menu, enter the new name and accept, the message >> sends are >> renamed, but the whitespace formatting in those refactored methods >> is not >> preserved. Is there any way at present to do this while keeping the >> formatting >> intact? > > Automatic refactoring that preserve the formatting are extremely > difficult to implement. In a common case, like with the rewrite engine > that the refactoring browser is using internally, this is not really > feasible. It is much easier to write your own formatter that formats > as you like, even if writing a working formatter is not trivial > either. > > For details listen to what the original authors of the Refactoring > Browser say about code formatting: > <http://www.cincomsmalltalk.com/blog/blogView?entry=3426663681>. > > 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

Sept. 20, 2009

Re: [Pharo-project] Gofer vs Installer

by StÃ©phane Ducasse

Definitively not well woken up yet :) > from > source.lukasrenggli.com/flair > > I'm about to write a chapter on it for PharoByexample2 > > Stef > > > On Sep 20, 2009, at 8:30 AM, Schwab,Wilhelm K wrote: > >> Sounds great! Is it downloadable? >> >> >> -----Original Message----- >> From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr >> ] On Behalf Of Lukas Renggli >> Sent: Sunday, September 20, 2009 1:18 AM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] Gofer vs Installer >> >>> Seaside 2.9 includes a tool that helps to manage packages, and >>> _somewhere_ I have an image with that loaded and ready for >>> shameless plagairism. This seems like such a common task that >>> there must be some good tools to handle it?? >> >> That's exactly Gofer. Seaside 3 is one of the reasons why I wrote it. >> >> Lukas >> >>> >>> Bill >>> >>> >>> -----Original Message----- >>> From: pharo-project-bounces(a)lists.gforge.inria.fr >>> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of >>> StÃ©phane Ducasse >>> Sent: Saturday, September 19, 2009 4:07 PM >>> To: Pharo-project(a)lists.gforge.inria.fr >>> Subject: Re: [Pharo-project] Gofer vs Installer >>> >>>>> >>>>> >>>>>> goals? >>>>> >>>>> Perform MC actions (load, update, merge, revert, commit, diff, >>>>> recompile) on a set of packages. >>>> >>>> So, not like Installer that can load packages from everywhere, >>>> Gofer >>>> will concentrate on MC? What about ScriptLoader? >>> >>> ScriptLoader will certainly use gofer to install packages instead of >>> installer >>> >>>> Stephane has mentioned Gofer before. Is in the plans to support >>>> only >>>> MC packages for Pharo and to use Gofer as the tool for load them on >>>> pharo. >>> >>> Yes. >>> Because in pharo we do not use anything else besides on changeset >>> to kick in the load. >>> >>>> Or nothing has been decided yet? It is considered? >>>>> >>>>>> implementation? >>>>> >>>>> Focus on keeping the system clean, e.g. no empty categories/ >>>>> protocols, properly ordered categories/protocols, no duplicated >>>>> repositories, etc. >>>> >>>> Installer can't do that? Is a question, I don't know much about the >>>> internals of Installer. >>> >>> Compared to sometimes ago they were cleaned but >>>> >>>>> >>>>>> speed? >>>>> >>>>> Not optimized yet. >>>>> >>>>>> license? >>>>> >>>>> MIT >>>> >>>> Can you please give us a big picture of the role Gofer will have? >>> >>> After discussion at Esug between dale, lukas and me listening :) >>> it seems that Metacello will use Gofer to load packages. >>> >>> Now I think that you should give a try to Gofer and report what is >>> missing or not. >>> I have some behvaior I would really like to have (that are specific >>> to ScriptLoader like tell me which packages have changed since a >>> given marked period). >>> >>> >>> >>>> >>>>> >>>>> Lukas >>>> >>>> Thanks >>>> -- >>>> 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 >>> >>> _______________________________________________ >>> 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 >> >> _______________________________________________ >> 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

Sept. 20, 2009

Re: [Pharo-project] Is there a way to use rename refactor while preserving whitespace formatting in refactored methods?

by Lukas Renggli

> Hi, I am using Pharo with the default browser, which is the OmniBrowser. When I > right-click on a message name in the right-most panel and choose "rename > refactor" from the menu, enter the new name and accept, the message sends are > renamed, but the whitespace formatting in those refactored methods is not > preserved. Is there any way at present to do this while keeping the formatting > intact? Automatic refactoring that preserve the formatting are extremely difficult to implement. In a common case, like with the rewrite engine that the refactoring browser is using internally, this is not really feasible. It is much easier to write your own formatter that formats as you like, even if writing a working formatter is not trivial either. For details listen to what the original authors of the Refactoring Browser say about code formatting: <http://www.cincomsmalltalk.com/blog/blogView?entry=3426663681>. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Sept. 20, 2009

Re: [Pharo-project] Gofer vs Installer

by Lukas Renggli

ScriptLoader loadLatestPackage: 'Gofer' from: 'http://source.lukas-renggli.ch/flair'. 2009/9/20 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: > Sounds great! Â Is it downloadable? > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Lukas Renggli > Sent: Sunday, September 20, 2009 1:18 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Gofer vs Installer > >> Â Seaside 2.9 includes a tool that helps to manage packages, and _somewhere_ I have an image with that loaded and ready for shameless plagairism. Â This seems like such a common task that there must be some good tools to handle it?? > > That's exactly Gofer. Seaside 3 is one of the reasons why I wrote it. > > Lukas > >> >> Bill >> >> >> -----Original Message----- >> From: pharo-project-bounces(a)lists.gforge.inria.fr >> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of >> StÃ©phane Ducasse >> Sent: Saturday, September 19, 2009 4:07 PM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] Gofer vs Installer >> >>>> >>>> >>>>> goals? >>>> >>>> Perform MC actions (load, update, merge, revert, commit, diff, >>>> recompile) on a set of packages. >>> >>> So, not like Installer that can load packages from everywhere, Gofer >>> will concentrate on MC? What about ScriptLoader? >> >> ScriptLoader will certainly use gofer to install packages instead of >> installer >> >>> Stephane has mentioned Gofer before. Is in the plans to support only >>> MC packages for Pharo and to use Gofer as the tool for load them on >>> pharo. >> >> Yes. >> Because in pharo we do not use anything else besides on changeset to kick in the load. >> >>> Or nothing has been decided yet? It is considered? >>>> >>>>> implementation? >>>> >>>> Focus on keeping the system clean, e.g. no empty categories/ >>>> protocols, properly ordered categories/protocols, no duplicated >>>> repositories, etc. >>> >>> Installer can't do that? Is a question, I don't know much about the >>> internals of Installer. >> >> Compared to sometimes ago they were cleaned but >>> >>>> >>>>> speed? >>>> >>>> Not optimized yet. >>>> >>>>> license? >>>> >>>> MIT >>> >>> Can you please give us a big picture of the role Gofer will have? >> >> After discussion at Â Esug between dale, lukas and me listening :) it seems that Metacello will use Gofer to load packages. >> >> Now I think that you should give a try to Gofer and report what is missing or not. >> I have some behvaior I would really like to have (that are specific to ScriptLoader like tell me which packages have changed since a given marked period). >> >> >> >>> >>>> >>>> Lukas >>> >>> Thanks >>> -- >>> 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 >> >> _______________________________________________ >> 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 > > _______________________________________________ > 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 http://www.lukas-renggli.ch

Sept. 20, 2009

Re: [Pharo-project] Gofer vs Installer

by Lukas Renggli

> I've done that, but my understanding is that "all" it does is show the methods that are packaged. Â I am hoping for something that would sniff out the methods that I have altered and are not in packages that I (somehow) claim to own. Â It seems like it would be really easy to miss important work and that it should be relatively easy to create something that scans for at-risk code. Â One thing I can enivision would compare a list of packages with user-owned methods in the system; anything that is not in one of the packages goes in a method browser with commands to package them in likely places. The refactoring Code Checker reliably detects unpackaged code, see Possible Bugs > Unpackaged Code. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Sept. 20, 2009

Re: [Pharo-project] Gofer vs Installer

by StÃ©phane Ducasse

from source.lukasrenggli.com/flair I'm about to write a chapter on it for PharoByexample2 Stef On Sep 20, 2009, at 8:30 AM, Schwab,Wilhelm K wrote: > Sounds great! Is it downloadable? > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr > ] On Behalf Of Lukas Renggli > Sent: Sunday, September 20, 2009 1:18 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Gofer vs Installer > >> Seaside 2.9 includes a tool that helps to manage packages, and >> _somewhere_ I have an image with that loaded and ready for >> shameless plagairism. This seems like such a common task that >> there must be some good tools to handle it?? > > That's exactly Gofer. Seaside 3 is one of the reasons why I wrote it. > > Lukas > >> >> Bill >> >> >> -----Original Message----- >> From: pharo-project-bounces(a)lists.gforge.inria.fr >> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of >> StÃ©phane Ducasse >> Sent: Saturday, September 19, 2009 4:07 PM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] Gofer vs Installer >> >>>> >>>> >>>>> goals? >>>> >>>> Perform MC actions (load, update, merge, revert, commit, diff, >>>> recompile) on a set of packages. >>> >>> So, not like Installer that can load packages from everywhere, Gofer >>> will concentrate on MC? What about ScriptLoader? >> >> ScriptLoader will certainly use gofer to install packages instead of >> installer >> >>> Stephane has mentioned Gofer before. Is in the plans to support only >>> MC packages for Pharo and to use Gofer as the tool for load them on >>> pharo. >> >> Yes. >> Because in pharo we do not use anything else besides on changeset >> to kick in the load. >> >>> Or nothing has been decided yet? It is considered? >>>> >>>>> implementation? >>>> >>>> Focus on keeping the system clean, e.g. no empty categories/ >>>> protocols, properly ordered categories/protocols, no duplicated >>>> repositories, etc. >>> >>> Installer can't do that? Is a question, I don't know much about the >>> internals of Installer. >> >> Compared to sometimes ago they were cleaned but >>> >>>> >>>>> speed? >>>> >>>> Not optimized yet. >>>> >>>>> license? >>>> >>>> MIT >>> >>> Can you please give us a big picture of the role Gofer will have? >> >> After discussion at Esug between dale, lukas and me listening :) >> it seems that Metacello will use Gofer to load packages. >> >> Now I think that you should give a try to Gofer and report what is >> missing or not. >> I have some behvaior I would really like to have (that are specific >> to ScriptLoader like tell me which packages have changed since a >> given marked period). >> >> >> >>> >>>> >>>> Lukas >>> >>> Thanks >>> -- >>> 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 >> >> _______________________________________________ >> 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 > > _______________________________________________ > 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

Sept. 20, 2009

Re: [Pharo-project] Gofer vs Installer

by StÃ©phane Ducasse

Ok I will I do not have the snipped at hand that can check all the dirty methods. Could you add that to bug traker with a request for feature because indeed this is a nice one. Stef On Sep 20, 2009, at 8:24 AM, Schwab,Wilhelm K wrote: > Stef, > > I've done that, but my understanding is that "all" it does is show > the methods that are packaged. I am hoping for something that would > sniff out the methods that I have altered and are not in packages > that I (somehow) claim to own. It seems like it would be really > easy to miss important work and that it should be relatively easy to > create something that scans for at-risk code. One thing I can > enivision would compare a list of packages with user-owned methods > in the system; anything that is not in one of the packages goes in a > method browser with commands to package them in likely places. > > Bill > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr > ] On Behalf Of StÃ©phane Ducasse > Sent: Sunday, September 20, 2009 1:03 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Gofer vs Installer > > The first thing you can try is to check using the browse button of > MC that you extensions methods are well in your package. > > Stef > > On Sep 20, 2009, at 12:43 AM, Schwab,Wilhelm K wrote: > >> I'd like to put on my user hat for a moment. A big concern of mine >> is >> doing a good job of saving packages from one image and moving them to >> another. I have (hopefully) been keeping my install script current >> as >> I add new packages, but it currently relies on my being careful. >> >> Clearly having very good coverage with tests would help to check the >> health of any new image; I'm slowly working on that. It would be >> nice >> to have ways to check for packaging mistakes. A "smell" that comes >> to >> mind is any methods that I wrote but are not in packages in my load >> script. Is there anything that does such checks? Seaside >> 2.9 includes a tool that helps to manage packages, and _somewhere_ I >> have an image with that loaded and ready for shameless plagairism. >> This seems like such a common task that there must be some good tools >> to handle it?? >> >> Bill >> >> >> -----Original Message----- >> From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr >> ] On Behalf Of StÃ©phane Ducasse >> Sent: Saturday, September 19, 2009 4:07 PM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] Gofer vs Installer >> >>>> >>>> >>>>> goals? >>>> >>>> Perform MC actions (load, update, merge, revert, commit, diff, >>>> recompile) on a set of packages. >>> >>> So, not like Installer that can load packages from everywhere, Gofer >>> will concentrate on MC? What about ScriptLoader? >> >> ScriptLoader will certainly use gofer to install packages instead of >> installer >> >>> Stephane has mentioned Gofer before. Is in the plans to support only >>> MC packages for Pharo and to use Gofer as the tool for load them on >>> pharo. >> >> Yes. >> Because in pharo we do not use anything else besides on changeset to >> kick in the load. >> >>> Or nothing has been decided yet? It is considered? >>>> >>>>> implementation? >>>> >>>> Focus on keeping the system clean, e.g. no empty categories/ >>>> protocols, properly ordered categories/protocols, no duplicated >>>> repositories, etc. >>> >>> Installer can't do that? Is a question, I don't know much about the >>> internals of Installer. >> >> Compared to sometimes ago they were cleaned but >>> >>>> >>>>> speed? >>>> >>>> Not optimized yet. >>>> >>>>> license? >>>> >>>> MIT >>> >>> Can you please give us a big picture of the role Gofer will have? >> >> After discussion at Esug between dale, lukas and me listening :) it >> seems that Metacello will use Gofer to load packages. >> >> Now I think that you should give a try to Gofer and report what is >> missing or not. >> I have some behvaior I would really like to have (that are specific >> to ScriptLoader like tell me which packages have changed since a >> given marked period). >> >> >> >>> >>>> >>>> Lukas >>> >>> Thanks >>> -- >>> 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 >> >> _______________________________________________ >> 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

Sept. 20, 2009

Re: [Pharo-project] Gofer vs Installer

by Schwab,Wilhelm K

Sounds great! Is it downloadable? -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Lukas Renggli Sent: Sunday, September 20, 2009 1:18 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Gofer vs Installer > Â Seaside 2.9 includes a tool that helps to manage packages, and _somewhere_ I have an image with that loaded and ready for shameless plagairism. Â This seems like such a common task that there must be some good tools to handle it?? That's exactly Gofer. Seaside 3 is one of the reasons why I wrote it. Lukas > > Bill > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr > [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of > StÃ©phane Ducasse > Sent: Saturday, September 19, 2009 4:07 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Gofer vs Installer > >>> >>> >>>> goals? >>> >>> Perform MC actions (load, update, merge, revert, commit, diff, >>> recompile) on a set of packages. >> >> So, not like Installer that can load packages from everywhere, Gofer >> will concentrate on MC? What about ScriptLoader? > > ScriptLoader will certainly use gofer to install packages instead of > installer > >> Stephane has mentioned Gofer before. Is in the plans to support only >> MC packages for Pharo and to use Gofer as the tool for load them on >> pharo. > > Yes. > Because in pharo we do not use anything else besides on changeset to kick in the load. > >> Or nothing has been decided yet? It is considered? >>> >>>> implementation? >>> >>> Focus on keeping the system clean, e.g. no empty categories/ >>> protocols, properly ordered categories/protocols, no duplicated >>> repositories, etc. >> >> Installer can't do that? Is a question, I don't know much about the >> internals of Installer. > > Compared to sometimes ago they were cleaned but >> >>> >>>> speed? >>> >>> Not optimized yet. >>> >>>> license? >>> >>> MIT >> >> Can you please give us a big picture of the role Gofer will have? > > After discussion at Â Esug between dale, lukas and me listening :) it seems that Metacello will use Gofer to load packages. > > Now I think that you should give a try to Gofer and report what is missing or not. > I have some behvaior I would really like to have (that are specific to ScriptLoader like tell me which packages have changed since a given marked period). > > > >> >>> >>> Lukas >> >> Thanks >> -- >> 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 > > _______________________________________________ > 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 _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 20, 2009

Re: [Pharo-project] Gofer vs Installer

by Schwab,Wilhelm K

Stef, I've done that, but my understanding is that "all" it does is show the methods that are packaged. I am hoping for something that would sniff out the methods that I have altered and are not in packages that I (somehow) claim to own. It seems like it would be really easy to miss important work and that it should be relatively easy to create something that scans for at-risk code. One thing I can enivision would compare a list of packages with user-owned methods in the system; anything that is not in one of the packages goes in a method browser with commands to package them in likely places. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Sunday, September 20, 2009 1:03 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Gofer vs Installer The first thing you can try is to check using the browse button of MC that you extensions methods are well in your package. Stef On Sep 20, 2009, at 12:43 AM, Schwab,Wilhelm K wrote: > I'd like to put on my user hat for a moment. A big concern of mine is > doing a good job of saving packages from one image and moving them to > another. I have (hopefully) been keeping my install script current as > I add new packages, but it currently relies on my being careful. > > Clearly having very good coverage with tests would help to check the > health of any new image; I'm slowly working on that. It would be nice > to have ways to check for packaging mistakes. A "smell" that comes to > mind is any methods that I wrote but are not in packages in my load > script. Is there anything that does such checks? Seaside > 2.9 includes a tool that helps to manage packages, and _somewhere_ I > have an image with that loaded and ready for shameless plagairism. > This seems like such a common task that there must be some good tools > to handle it?? > > Bill > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr > ] On Behalf Of StÃ©phane Ducasse > Sent: Saturday, September 19, 2009 4:07 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Gofer vs Installer > >>> >>> >>>> goals? >>> >>> Perform MC actions (load, update, merge, revert, commit, diff, >>> recompile) on a set of packages. >> >> So, not like Installer that can load packages from everywhere, Gofer >> will concentrate on MC? What about ScriptLoader? > > ScriptLoader will certainly use gofer to install packages instead of > installer > >> Stephane has mentioned Gofer before. Is in the plans to support only >> MC packages for Pharo and to use Gofer as the tool for load them on >> pharo. > > Yes. > Because in pharo we do not use anything else besides on changeset to > kick in the load. > >> Or nothing has been decided yet? It is considered? >>> >>>> implementation? >>> >>> Focus on keeping the system clean, e.g. no empty categories/ >>> protocols, properly ordered categories/protocols, no duplicated >>> repositories, etc. >> >> Installer can't do that? Is a question, I don't know much about the >> internals of Installer. > > Compared to sometimes ago they were cleaned but >> >>> >>>> speed? >>> >>> Not optimized yet. >>> >>>> license? >>> >>> MIT >> >> Can you please give us a big picture of the role Gofer will have? > > After discussion at Esug between dale, lukas and me listening :) it > seems that Metacello will use Gofer to load packages. > > Now I think that you should give a try to Gofer and report what is > missing or not. > I have some behvaior I would really like to have (that are specific > to ScriptLoader like tell me which packages have changed since a > given marked period). > > > >> >>> >>> Lukas >> >> Thanks >> -- >> 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 > > _______________________________________________ > 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

Sept. 20, 2009

Re: [Pharo-project] Gofer vs Installer

by Lukas Renggli

> Â Seaside 2.9 includes a tool that helps to manage packages, and _somewhere_ I have an image with that loaded and ready for shameless plagairism. Â This seems like such a common task that there must be some good tools to handle it?? That's exactly Gofer. Seaside 3 is one of the reasons why I wrote it. Lukas > > Bill > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse > Sent: Saturday, September 19, 2009 4:07 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Gofer vs Installer > >>> >>> >>>> goals? >>> >>> Perform MC actions (load, update, merge, revert, commit, diff, >>> recompile) on a set of packages. >> >> So, not like Installer that can load packages from everywhere, Gofer >> will concentrate on MC? What about ScriptLoader? > > ScriptLoader will certainly use gofer to install packages instead of installer > >> Stephane has mentioned Gofer before. Is in the plans to support only >> MC packages for Pharo and to use Gofer as the tool for load them on >> pharo. > > Yes. > Because in pharo we do not use anything else besides on changeset to kick in the load. > >> Or nothing has been decided yet? It is considered? >>> >>>> implementation? >>> >>> Focus on keeping the system clean, e.g. no empty categories/ >>> protocols, properly ordered categories/protocols, no duplicated >>> repositories, etc. >> >> Installer can't do that? Is a question, I don't know much about the >> internals of Installer. > > Compared to sometimes ago they were cleaned but >> >>> >>>> speed? >>> >>> Not optimized yet. >>> >>>> license? >>> >>> MIT >> >> Can you please give us a big picture of the role Gofer will have? > > After discussion at Â Esug between dale, lukas and me listening :) it seems that Metacello will use Gofer to load packages. > > Now I think that you should give a try to Gofer and report what is missing or not. > I have some behvaior I would really like to have (that are specific to ScriptLoader like tell me which packages have changed since a given marked period). > > > >> >>> >>> Lukas >> >> Thanks >> -- >> 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 > > _______________________________________________ > 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

Sept. 20, 2009