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

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Lukas Renggli

> Lukas is the official maintainer of the OB package for Pharo. > Therefore I assume OB should be loaded from his repository... Lukas? Well, not really "official" maintainer. I need a browser that does not get in my way all the time. Therefor I integrated the refactoring tools and fixed all the OB problems in Pharo. I shouldn't do it, I don't have time for that. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 10, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by StÃ©phane Ducasse

sure we understood it like that :) On Jan 10, 2010, at 2:16 PM, Matthias Berth wrote: > Bill, > > > all I wanted to do with that snippet was to help you install seaside. > I did not want to pretend that this is the 'blessed' way of doing it > ;-) > > Cheers > > Matthias > > On Sun, Jan 10, 2010 at 12:35 AM, Schwab,Wilhelm K > <bschwab(a)anest.ufl.edu> wrote: >> Matthias, >> >> That appears to have worked. Let's see, we have Installer, ScriptLoader, Configuration*, Gofer, etc., and now Loader =:0 I'm guilty too, because I ended up writing Migrate in self defense. Clearly something is missing in package management or we would not have so many different solutions to strongly overlapping problems. >> >> I will have to repeat this because >> >> Loader new load: 'Pharo' version: '1.0-rc2.10505'. >> >> did not seem to do much - makes me wonder whether I really ran it. If not, then it appears not to be necessary for Seaside to at least load. >> >> If this is in fact the correct way to install Seaside (I submit we need direction on that, unless you or Esteban are the authoritative source??), then it needs to get a link on the download page. Therein, we should refer to (Smalltalk at:#Loader) rather than directly to Loader. >> >> Please convey my thanks and respect to Esteban - not sure I want to know *how* this works :) >> >> Thanks!! >> >> Bill >> >> >> >> -----Original Message----- >> From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Matthias Berth >> Sent: Saturday, January 09, 2010 6:09 PM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 >> >> Hi Bill, >> >> this one works for me with the current pharo core 1.0 rc1, update upto 10505 >> >> "execute this:" >> Gofer new >> squeaksource: 'Loader'; >> package: 'Loader'; >> load. >> "then this" >> Loader new load: 'Pharo' version: '1.0-rc2.10505'. >> "then this" >> Loader new >> load: 'Seaside28' version: '2.8.4.2' >> >> The "Loader new load: 'Pharo' version: '1.0-rc2.10505'." loads a lot of additional pharo packages. I guess you won't need that just to get seaside working. >> >> Ask Esteban Lorenzano for details about hw this works :) >> >> Cheers >> >> Matthias >> >> 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: >>> Two can be tired of this. I could just use the official Seaside >>> images, but I thought it might be nice to help with testing the >>> monthly images. I won't get very far with that if Seaside won't load. >>> >>> >>> ________________________________ >>> From: pharo-project-bounces(a)lists.gforge.inria.fr >>> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of >>> Mariano Martinez Peck >>> Sent: Saturday, January 09, 2010 4:38 PM >>> To: Pharo-project(a)lists.gforge.inria.fr >>> Subject: Re: [Pharo-project] [BetaTesting] [ANN] >>> Pharo1.0-10505-rc1dev10.01.1 >>> >>> >>> >>> 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> >>>> >>>> Mariano, >>>> >>>> The reason I objected (and continue to do so) to clobbering the web >>>> image is that complete chaos of how to install things comes into >>>> play. Assuming that I know what YOU said on the subject is a stretch >>>> to say the least: try a search engine on the subject. >>>> >>> >>> I am a bit tired of this. I will answer for the last time and I hope >>> you >>> understand: Do you want seaside ? >>> >>> 1) Volunteer yourself to build Web images. It is easy to ask, but what >>> about doing? >>> >>> 2) Take the Web Image before, analize how seaside was installed and do >>> it by yourself. I cannot take it more than half an hour. >>> >>> 3) Use official seaside image >>> >>> 4) Report what doesn't work with the ConfigurationOfSeaside in >>> Metacello mailing list so that everybody can collaborate and fix it. >>> If you see that mailing list, I did exactly that. Just saying "doesn't work" does not help. >>> >>> Cheers >>> >>> Mariano >>> >>>> >>>> BTW, it does not work. There is very little I can do until Seaside loads. >>>> >>>> Bill >>>> >>>> ________________________________ >>>> From: pharo-project-bounces(a)lists.gforge.inria.fr >>>> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of >>>> Mariano Martinez Peck >>>> Sent: Saturday, January 09, 2010 4:08 PM >>>> To: Pharo-project(a)lists.gforge.inria.fr >>>> Subject: Re: [Pharo-project] [BetaTesting] [ANN] >>>> Pharo1.0-10505-rc1dev10.01.1 >>>> >>>> >>>> >>>> 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> >>>>> >>>>> Gofer seaside28 load >>>>> >>>> >>>> I didn't say that. I said: >>>> >>>> Gofer new >>>> squeaksource: 'MetacelloRepository'; >>>> package: 'ConfigurationOfSeaside28'; >>>> load. >>>> >>>> (Smalltalk at: #ConfigurationOfSeaside28) load >>>> >>>> And I also said I was not sure of this is working. >>>> >>>> Cheers >>>> >>>> Mariano >>>> >>>>> >>>>> does not work. What is the correct way to install Seaside - I can't >>>>> do much w/o it. >>>>> >>>>> ________________________________ >>>>> From: pharo-project-bounces(a)lists.gforge.inria.fr >>>>> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of >>>>> Mariano Martinez Peck >>>>> Sent: Saturday, January 09, 2010 3:01 PM >>>>> To: Pharo-project(a)lists.gforge.inria.fr >>>>> Subject: Re: [Pharo-project] [BetaTesting] [ANN] >>>>> Pharo1.0-10505-rc1dev10.01.1 >>>>> >>>>> >>>>> >>>>> 2010/1/9 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> >>>>>> >>>>>> Hi Mariano, >>>>>> >>>>>> good job. Some feedback. >>>>>> >>>>>> The installScript has unused variables and your proxy settings exposed. >>>>>> Maybe this should be deleted from the final build. >>>>>> >>>>> >>>>> hahahahah I knew I was going to forget about that :( Thanks. Some >>>>> bash guru that help me to automatize this? I would like something >>>>> that automatically removes that from the file if it is found. >>>>> Can you help me Miguel ? >>>>> >>>>>> >>>>>> Shouldn't be this a RC 2? because there is a new build process and >>>>>> has nothing to do with the RC1? >>>>>> >>>>> >>>>> I thought about putting it RC2, actually, I was going to do that. >>>>> But as the PharoCore was named rc1, I din't want to name it rc2 >>>>> because maybe it was confusing. >>>>> I am not sure, thus. What do you think ? >>>>> >>>>>> >>>>>> Also, the changes files, shouldn't be compressed for each RC and >>>>>> for the final release? >>>>> >>>>> Excellent point. Do you rather to Smalltalk >> condenseChanges ? It >>>>> can be perfectly added. Right now, we are doing all this: >>>>> >>>>> >>>>> MCFileBasedRepository flushAllCaches. >>>>> MCDefinition clearInstances. >>>>> Smalltalk removeEmptyMessageCategories. >>>>> Utilities cleanseOtherworldlySteppers. >>>>> Undeclared removeUnreferencedKeys. >>>>> Categorizer sortAllCategories. >>>>> Symbol compactSymbolTable. >>>>> Smalltalk at: #ReleaseBuilderDeveloper ifPresent: [:builder | >>>>> builder new fixObsoleteReferences]. >>>>> RequiredSelectors initialize. >>>>> ProvidedSelectors initialize. >>>>> LocalSends initialize. >>>>> Smalltalk organization removeEmptyCategories. >>>>> SystemBrowser removeObsolete. >>>>> TheWorldMenu removeObsolete. >>>>> AppRegistry removeObsolete. >>>>> Set rehashAllSets. >>>>> Smalltalk cleanOutUndeclared. >>>>> Smalltalk garbageCollect. >>>>> >>>>> >>>>> Do you think something else should be addded? Maybe we can reuse >>>>> ScriptLoader cleanings ? >>>>> >>>>> >>>>>> >>>>>> Also, the packages.txt file talks about PharoCore1.0 (#10505). Has >>>>>> someone thought about the name shown in System->About: >>>>>> >>>>>> PharoCore1.0rc1 >>>>>> Latest update: #10505 >>>>>> >>>>>> Because this is not a PharoCore image. Shouldn't this read >>>>>> something like >>>>>> >>>>>> Pharo 1.0 Dev image. >>>>>> Based on PharoCore1.0rc1 >>>>>> Latest update: #10505 >>>>>> >>>>> >>>>> Yes, that's true. I agree. At least it was not "my falt" as it was >>>>> already like that. But I am agree we should change that. However, I >>>>> don't know how to do it. >>>>> Maybe something related to SystemVersion? Any help ? >>>>> >>>>> >>>>>> >>>>>> What about the disabling of software updates in the Pharo dev/web >>>>>> images? Will this be implemented or a careful update stream will be >>>>>> made in order to not break a dev image with overrides (real >>>>>> difficult I think). >>>>>> >>>>> >>>>> Maybe. But in addition, sometimes there are bugs that updating just >>>>> fix them. I am not sure if I want to disable. I rather warn people about it. >>>>> Do you know if we break some overrrides doing an update? >>>>> >>>>>> >>>>>> Maybe all this setup can be put in a post-script in the >>>>>> ConfigurationOfPharo class. >>>>> >>>>> It is. We have pre and post do its. So, no problem :) >>>>> >>>>>> >>>>>> That's all for now. I'm going to use this image to work the >>>>>> following days. >>>>>> >>>>>> >>>>>> Cheers and keep the good work. >>>>>> >>>>> >>>>> Thanks Miguel for the excellent feedback. Let's hope to build better >>>>> images! >>>>> >>>>> Mariano >>>>> >>>>> >>>>>> >>>>>> -- >>>>>> 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 >> >> _______________________________________________ >> 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

Jan. 10, 2010

Re: [Pharo-project] Categorizing method extension with pragma

by StÃ©phane Ducasse

yes now we should pay attention about metadata in the methods. Now what we can have also is that the ***package*** knows the extension this is what my dead slowing making progress impelemntation is doing. On Jan 10, 2010, at 2:08 PM, CÃ©drick BÃ©ler wrote: > Hi, > > Just a 2 cents thought on method extension. > > Why not associating a pragma instead of using the package name prefixed by a star ? > > Say there is a package named MyPackage and I override a method in String or add a new one. What I'd like is keeping the original method category name (or find an appropriate one) instead of using *mypackage. For instance: > > String>>aMethod > <package: MyPackage> > ... > ... > ^result > > > Then, we would have to adapt monticello for that purpose. We could also use dynamic protocols to get the list of extension method by package. > > What does other think ? I find it could be a good starting point to deal with packages. > > > > -- > CÃ©drick > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 10, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by StÃ©phane Ducasse

+1 Stef On Jan 10, 2010, at 2:13 PM, Lukas Renggli wrote: >> Adrian: Most of the failing tests are from OB. Someone said Lukas made all >> those tests green, but they are commited in his repo. Someone should merge >> that with the wiresong repo. If no one merge that, I don't know what to do: >> or remove them or keep them. > > Use the code from my repository. However, there are currently 4 broken > tests as you can see on the build server > <http://hudson.lukas-renggli.ch/job/Development/lastCompletedBuild/testRepor…>. > Looks like some kind of a side-effect on the headless linux VM, > because I don't observe them in my image. > > 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

Jan. 10, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Mariano Martinez Peck

On Sun, Jan 10, 2010 at 2:16 PM, Matthias Berth < matthias.berth(a)googlemail.com> wrote: > Bill, > > > all I wanted to do with that snippet was to help you install seaside. > I did not want to pretend that this is the 'blessed' way of doing it > ;-) > > Thanks Matthias, and it was very useful, indeed. We just want to get clear with the intentions of Pharo and each project :) > Cheers > > Matthias > > On Sun, Jan 10, 2010 at 12:35 AM, Schwab,Wilhelm K > <bschwab(a)anest.ufl.edu> wrote: > > Matthias, > > > > That appears to have worked. Let's see, we have Installer, ScriptLoader, > Configuration*, Gofer, etc., and now Loader =:0 I'm guilty too, because I > ended up writing Migrate in self defense. Clearly something is missing in > package management or we would not have so many different solutions to > strongly overlapping problems. > > > > I will have to repeat this because > > > > Loader new load: 'Pharo' version: '1.0-rc2.10505'. > > > > did not seem to do much - makes me wonder whether I really ran it. If > not, then it appears not to be necessary for Seaside to at least load. > > > > If this is in fact the correct way to install Seaside (I submit we need > direction on that, unless you or Esteban are the authoritative source??), > then it needs to get a link on the download page. Therein, we should refer > to (Smalltalk at:#Loader) rather than directly to Loader. > > > > Please convey my thanks and respect to Esteban - not sure I want to know > *how* this works :) > > > > Thanks!! > > > > Bill > > > > > > > > -----Original Message----- > > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto: > pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Matthias Berth > > Sent: Saturday, January 09, 2010 6:09 PM > > To: Pharo-project(a)lists.gforge.inria.fr > > Subject: Re: [Pharo-project] [BetaTesting] [ANN] > Pharo1.0-10505-rc1dev10.01.1 > > > > Hi Bill, > > > > this one works for me with the current pharo core 1.0 rc1, update upto > 10505 > > > > "execute this:" > > Gofer new > > squeaksource: 'Loader'; > > package: 'Loader'; > > load. > > "then this" > > Loader new load: 'Pharo' version: '1.0-rc2.10505'. > > "then this" > > Loader new > > load: 'Seaside28' version: '2.8.4.2' > > > > The "Loader new load: 'Pharo' version: '1.0-rc2.10505'." loads a lot of > additional pharo packages. I guess you won't need that just to get seaside > working. > > > > Ask Esteban Lorenzano for details about hw this works :) > > > > Cheers > > > > Matthias > > > > 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: > >> Two can be tired of this. I could just use the official Seaside > >> images, but I thought it might be nice to help with testing the > >> monthly images. I won't get very far with that if Seaside won't load. > >> > >> > >> ________________________________ > >> From: pharo-project-bounces(a)lists.gforge.inria.fr > >> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of > >> Mariano Martinez Peck > >> Sent: Saturday, January 09, 2010 4:38 PM > >> To: Pharo-project(a)lists.gforge.inria.fr > >> Subject: Re: [Pharo-project] [BetaTesting] [ANN] > >> Pharo1.0-10505-rc1dev10.01.1 > >> > >> > >> > >> 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> > >>> > >>> Mariano, > >>> > >>> The reason I objected (and continue to do so) to clobbering the web > >>> image is that complete chaos of how to install things comes into > >>> play. Assuming that I know what YOU said on the subject is a stretch > >>> to say the least: try a search engine on the subject. > >>> > >> > >> I am a bit tired of this. I will answer for the last time and I hope > >> you > >> understand: Do you want seaside ? > >> > >> 1) Volunteer yourself to build Web images. It is easy to ask, but what > >> about doing? > >> > >> 2) Take the Web Image before, analize how seaside was installed and do > >> it by yourself. I cannot take it more than half an hour. > >> > >> 3) Use official seaside image > >> > >> 4) Report what doesn't work with the ConfigurationOfSeaside in > >> Metacello mailing list so that everybody can collaborate and fix it. > >> If you see that mailing list, I did exactly that. Just saying "doesn't > work" does not help. > >> > >> Cheers > >> > >> Mariano > >> > >>> > >>> BTW, it does not work. There is very little I can do until Seaside > loads. > >>> > >>> Bill > >>> > >>> ________________________________ > >>> From: pharo-project-bounces(a)lists.gforge.inria.fr > >>> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of > >>> Mariano Martinez Peck > >>> Sent: Saturday, January 09, 2010 4:08 PM > >>> To: Pharo-project(a)lists.gforge.inria.fr > >>> Subject: Re: [Pharo-project] [BetaTesting] [ANN] > >>> Pharo1.0-10505-rc1dev10.01.1 > >>> > >>> > >>> > >>> 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> > >>>> > >>>> Gofer seaside28 load > >>>> > >>> > >>> I didn't say that. I said: > >>> > >>> Gofer new > >>> squeaksource: 'MetacelloRepository'; > >>> package: 'ConfigurationOfSeaside28'; > >>> load. > >>> > >>> (Smalltalk at: #ConfigurationOfSeaside28) load > >>> > >>> And I also said I was not sure of this is working. > >>> > >>> Cheers > >>> > >>> Mariano > >>> > >>>> > >>>> does not work. What is the correct way to install Seaside - I can't > >>>> do much w/o it. > >>>> > >>>> ________________________________ > >>>> From: pharo-project-bounces(a)lists.gforge.inria.fr > >>>> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of > >>>> Mariano Martinez Peck > >>>> Sent: Saturday, January 09, 2010 3:01 PM > >>>> To: Pharo-project(a)lists.gforge.inria.fr > >>>> Subject: Re: [Pharo-project] [BetaTesting] [ANN] > >>>> Pharo1.0-10505-rc1dev10.01.1 > >>>> > >>>> > >>>> > >>>> 2010/1/9 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > >>>>> > >>>>> Hi Mariano, > >>>>> > >>>>> good job. Some feedback. > >>>>> > >>>>> The installScript has unused variables and your proxy settings > exposed. > >>>>> Maybe this should be deleted from the final build. > >>>>> > >>>> > >>>> hahahahah I knew I was going to forget about that :( Thanks. Some > >>>> bash guru that help me to automatize this? I would like something > >>>> that automatically removes that from the file if it is found. > >>>> Can you help me Miguel ? > >>>> > >>>>> > >>>>> Shouldn't be this a RC 2? because there is a new build process and > >>>>> has nothing to do with the RC1? > >>>>> > >>>> > >>>> I thought about putting it RC2, actually, I was going to do that. > >>>> But as the PharoCore was named rc1, I din't want to name it rc2 > >>>> because maybe it was confusing. > >>>> I am not sure, thus. What do you think ? > >>>> > >>>>> > >>>>> Also, the changes files, shouldn't be compressed for each RC and > >>>>> for the final release? > >>>> > >>>> Excellent point. Do you rather to Smalltalk >> condenseChanges ? It > >>>> can be perfectly added. Right now, we are doing all this: > >>>> > >>>> > >>>> MCFileBasedRepository flushAllCaches. > >>>> MCDefinition clearInstances. > >>>> Smalltalk removeEmptyMessageCategories. > >>>> Utilities cleanseOtherworldlySteppers. > >>>> Undeclared removeUnreferencedKeys. > >>>> Categorizer sortAllCategories. > >>>> Symbol compactSymbolTable. > >>>> Smalltalk at: #ReleaseBuilderDeveloper ifPresent: [:builder | > >>>> builder new fixObsoleteReferences]. > >>>> RequiredSelectors initialize. > >>>> ProvidedSelectors initialize. > >>>> LocalSends initialize. > >>>> Smalltalk organization removeEmptyCategories. > >>>> SystemBrowser removeObsolete. > >>>> TheWorldMenu removeObsolete. > >>>> AppRegistry removeObsolete. > >>>> Set rehashAllSets. > >>>> Smalltalk cleanOutUndeclared. > >>>> Smalltalk garbageCollect. > >>>> > >>>> > >>>> Do you think something else should be addded? Maybe we can reuse > >>>> ScriptLoader cleanings ? > >>>> > >>>> > >>>>> > >>>>> Also, the packages.txt file talks about PharoCore1.0 (#10505). Has > >>>>> someone thought about the name shown in System->About: > >>>>> > >>>>> PharoCore1.0rc1 > >>>>> Latest update: #10505 > >>>>> > >>>>> Because this is not a PharoCore image. Shouldn't this read > >>>>> something like > >>>>> > >>>>> Pharo 1.0 Dev image. > >>>>> Based on PharoCore1.0rc1 > >>>>> Latest update: #10505 > >>>>> > >>>> > >>>> Yes, that's true. I agree. At least it was not "my falt" as it was > >>>> already like that. But I am agree we should change that. However, I > >>>> don't know how to do it. > >>>> Maybe something related to SystemVersion? Any help ? > >>>> > >>>> > >>>>> > >>>>> What about the disabling of software updates in the Pharo dev/web > >>>>> images? Will this be implemented or a careful update stream will be > >>>>> made in order to not break a dev image with overrides (real > >>>>> difficult I think). > >>>>> > >>>> > >>>> Maybe. But in addition, sometimes there are bugs that updating just > >>>> fix them. I am not sure if I want to disable. I rather warn people > about it. > >>>> Do you know if we break some overrrides doing an update? > >>>> > >>>>> > >>>>> Maybe all this setup can be put in a post-script in the > >>>>> ConfigurationOfPharo class. > >>>> > >>>> It is. We have pre and post do its. So, no problem :) > >>>> > >>>>> > >>>>> That's all for now. I'm going to use this image to work the > >>>>> following days. > >>>>> > >>>>> > >>>>> Cheers and keep the good work. > >>>>> > >>>> > >>>> Thanks Miguel for the excellent feedback. Let's hope to build better > >>>> images! > >>>> > >>>> Mariano > >>>> > >>>> > >>>>> > >>>>> -- > >>>>> 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 > > > > _______________________________________________ > > 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 >

Jan. 10, 2010

[Pharo-project] System -> About in Dev images

by Mariano Martinez Peck

Hi folks: If you take a Dev image and go to " System->About " you get something like: PharoCore1.0rc1 Latest update: #10505 However, I would like to show something like this for example: Pharo1.0-10505-rc1dev10.01.1 PharoCore1.0rc1 Latest update: #10505 Do you know how we can change this? How can I set that name when building a PharoDev image? Is this related to SystemVersion ?? We need to have this fixed for the official 1.0 release. Cheers Mariano

Jan. 10, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Matthias Berth

Bill, all I wanted to do with that snippet was to help you install seaside. I did not want to pretend that this is the 'blessed' way of doing it ;-) Cheers Matthias On Sun, Jan 10, 2010 at 12:35 AM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Matthias, > > That appears to have worked. Â Let's see, we have Installer, ScriptLoader, Configuration*, Gofer, etc., and now Loader =:0 Â I'm guilty too, because I ended up writing Migrate in self defense. Â Clearly something is missing in package management or we would not have so many different solutions to strongly overlapping problems. > > I will have to repeat this because > > Â Loader new load: 'Pharo' version: '1.0-rc2.10505'. > > did not seem to do much - makes me wonder whether I really ran it. Â If not, then it appears not to be necessary for Seaside to at least load. > > If this is in fact the correct way to install Seaside (I submit we need direction on that, unless you or Esteban are the authoritative source??), then it needs to get a link on the download page. Â Therein, we should refer to (Smalltalk at:#Loader) rather than directly to Loader. > > Please convey my thanks and respect to Esteban - not sure I want to know *how* this works :) > > Thanks!! > > Bill > > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Matthias Berth > Sent: Saturday, January 09, 2010 6:09 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 > > Hi Bill, > > this one works for me with the current pharo core 1.0 rc1, update upto 10505 > > "execute this:" > Gofer new > Â Â Â squeaksource: 'Loader'; > Â Â Â package: 'Loader'; > Â Â Â load. > "then this" > Loader new load: 'Pharo' version: '1.0-rc2.10505'. > "then this" > Loader new > Â Â Â load: 'Seaside28' version: '2.8.4.2' > > The "Loader new load: 'Pharo' version: '1.0-rc2.10505'." loads a lot of additional pharo packages. I guess you won't need that just to get seaside working. > > Ask Esteban Lorenzano for details about hw this works :) > > Cheers > > Matthias > > 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: >> Two can be tired of this.Â I could just use the official Seaside >> images, but I thought it might be nice to help with testing the >> monthly images.Â I won't get very far with that if Seaside won't load. >> >> >> ________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr >> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of >> Mariano Martinez Peck >> Sent: Saturday, January 09, 2010 4:38 PM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] [BetaTesting] [ANN] >> Pharo1.0-10505-rc1dev10.01.1 >> >> >> >> 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> >>> >>> Mariano, >>> >>> The reason I objected (and continue to do so) to clobbering the web >>> image is that complete chaos of how to install things comes into >>> play.Â Assuming that I know what YOU said on the subject is a stretch >>> to say the least: try a search engine on the subject. >>> >> >> I am a bit tired of this. I will answer for the last time and I hope >> you >> understand: Do you want seaside ? >> >> 1) Volunteer yourself to build Web images. It is easy to ask, but what >> about doing? >> >> 2) Take the Web Image before, analize how seaside was installed and do >> it by yourself. I cannot take it more than half an hour. >> >> 3) Use official seaside image >> >> 4) Report what doesn't work with the ConfigurationOfSeaside in >> Metacello mailing list so that everybody can collaborate and fix it. >> If you see that mailing list, I did exactly that. Just saying "doesn't work"Â does not help. >> >> Cheers >> >> Mariano >> >>> >>> BTW, it does not work.Â There is very little I can do until Seaside loads. >>> >>> Bill >>> >>> ________________________________ >>> From: pharo-project-bounces(a)lists.gforge.inria.fr >>> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of >>> Mariano Martinez Peck >>> Sent: Saturday, January 09, 2010 4:08 PM >>> To: Pharo-project(a)lists.gforge.inria.fr >>> Subject: Re: [Pharo-project] [BetaTesting] [ANN] >>> Pharo1.0-10505-rc1dev10.01.1 >>> >>> >>> >>> 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> >>>> >>>> Gofer seaside28 load >>>> >>> >>> I didn't say that. I said: >>> >>> Gofer new >>> Â Â Â squeaksource: 'MetacelloRepository'; >>> Â Â Â package: 'ConfigurationOfSeaside28'; >>> Â Â Â load. >>> >>> (Smalltalk at: #ConfigurationOfSeaside28) load >>> >>> And I also said I was not sure of this is working. >>> >>> Cheers >>> >>> Mariano >>> >>>> >>>> does not work.Â What is the correct way to install Seaside - I can't >>>> do much w/o it. >>>> >>>> ________________________________ >>>> From: pharo-project-bounces(a)lists.gforge.inria.fr >>>> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of >>>> Mariano Martinez Peck >>>> Sent: Saturday, January 09, 2010 3:01 PM >>>> To: Pharo-project(a)lists.gforge.inria.fr >>>> Subject: Re: [Pharo-project] [BetaTesting] [ANN] >>>> Pharo1.0-10505-rc1dev10.01.1 >>>> >>>> >>>> >>>> 2010/1/9 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> >>>>> >>>>> Hi Mariano, >>>>> >>>>> good job. Some feedback. >>>>> >>>>> The installScript has unused variables and your proxy settings exposed. >>>>> Maybe this should be deleted from the final build. >>>>> >>>> >>>> hahahahah I knew I was going to forget about that :( Thanks. Some >>>> bash guru that help me to automatize this? I would like something >>>> that automatically removes that from the file if it is found. >>>> Can you help me Miguel ? >>>> >>>>> >>>>> Shouldn't be this a RC 2? because there is a new build process and >>>>> has nothing to do with the RC1? >>>>> >>>> >>>> I thought about putting it RC2, actually, I was going to do that. >>>> But as the PharoCore was named rc1, I din't want to name it rc2 >>>> because maybe it was confusing. >>>> I am not sure, thus. What do you think ? >>>> >>>>> >>>>> Also, the changes files, shouldn't be compressed for each RC and >>>>> for the final release? >>>> >>>> Excellent point. Do you rather to Smalltalk >> condenseChanges ?Â It >>>> can be perfectly added. Right now, we are doing all this: >>>> >>>> >>>> Â Â Â MCFileBasedRepository flushAllCaches. >>>> Â Â Â MCDefinition clearInstances. >>>> Â Â Â Smalltalk removeEmptyMessageCategories. >>>> Â Â Â Utilities cleanseOtherworldlySteppers. >>>> Â Â Â Undeclared removeUnreferencedKeys. >>>> Â Â Â Categorizer sortAllCategories. >>>> Â Â Â Symbol compactSymbolTable. >>>> Â Â Â Smalltalk at: #ReleaseBuilderDeveloper ifPresent: [:builder | >>>> builder new fixObsoleteReferences]. >>>> Â Â Â RequiredSelectors initialize. >>>> Â Â Â ProvidedSelectors initialize. >>>> Â Â Â LocalSends initialize. >>>> Â Â Â Smalltalk organization removeEmptyCategories. >>>> Â Â Â SystemBrowser removeObsolete. >>>> Â Â Â TheWorldMenu removeObsolete. >>>> Â Â Â AppRegistry removeObsolete. >>>> Â Â Â Set rehashAllSets. >>>> Â Â Â Smalltalk cleanOutUndeclared. >>>> Â Â Â Smalltalk garbageCollect. >>>> >>>> >>>> Do you think something else should be addded?Â Â Maybe we can reuse >>>> ScriptLoader cleanings ? >>>> >>>> >>>>> >>>>> Also, the packages.txt file talks about PharoCore1.0 (#10505). Has >>>>> someone thought about the name shown in System->About: >>>>> >>>>> PharoCore1.0rc1 >>>>> Latest update: #10505 >>>>> >>>>> Because this is not a PharoCore image. Shouldn't this read >>>>> something like >>>>> >>>>> Pharo 1.0 Dev image. >>>>> Based on PharoCore1.0rc1 >>>>> Latest update: #10505 >>>>> >>>> >>>> Yes, that's true. I agree. At least it was not "my falt" as it was >>>> already like that. But I am agree we should change that. However, I >>>> don't know how to do it. >>>> Maybe something related to SystemVersion? Any help ? >>>> >>>> >>>>> >>>>> What about the disabling of software updates in the Pharo dev/web >>>>> images? Will this be implemented or a careful update stream will be >>>>> made in order to not break a dev image with overrides (real >>>>> difficult I think). >>>>> >>>> >>>> Maybe. But in addition, sometimes there are bugs that updating just >>>> fix them. I am not sure if I want to disable. I rather warn people about it. >>>> Do you know if we break some overrrides doing an update? >>>> >>>>> >>>>> Maybe all this setup can be put in a post-script in the >>>>> ConfigurationOfPharo class. >>>> >>>> It is. We have pre and post do its. So, no problem :) >>>> >>>>> >>>>> That's all for now. I'm going to use this image to work the >>>>> following days. >>>>> >>>>> >>>>> Cheers and keep the good work. >>>>> >>>> >>>> Thanks Miguel for the excellent feedback. Let's hope to build better >>>> images! >>>> >>>> Mariano >>>> >>>> >>>>> >>>>> -- >>>>> 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 10, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Adrian Lienhard

Lukas is the official maintainer of the OB package for Pharo. Therefore I assume OB should be loaded from his repository... Lukas? Cheers, Adrian PS: I don't know why testFinalizationOfEquals sometimes fails (also in PharoCore) PPS: Fixing testSymbolTableM6812 is on my todo list (it needs a change in PharoCore) On Jan 10, 2010, at 14:05 , Mariano Martinez Peck wrote: > > > On Sun, Jan 10, 2010 at 11:34 AM, Adrian Lienhard <adi(a)netstyle.ch> > wrote: > > On Jan 9, 2010, at 22:32 , Mariano Martinez Peck wrote: > > > Thanks Benoit for the report and taking the time to run all the > > tests. I > > already knew that there are a lot failing tests. Unfortunately, > > there is not > > too much I can do: > > > > 1) Maintainers of packages with failures can tell me if they are > > failing for > > "my fault". I mean, because I don't load a dependency or something > > like > > that. And if this is the case, I can fix that. > > > > 2) I can remove all the packages that have failing tests -> I think > > we will > > load very few packages. > > > > 3) We should ask maintainers to fix them. Of course, there are > > packages that > > even don't have maintainers. > > > > thoughts about this ? > > Some time ago I individually talked with each maintainer and > eventually we managed to get all tests pass. That was with the > previous build of the Pharo image that Damien did. Now, I don't know > which additional tests you have loaded (?) but either these need to be > fixed or we should not load them. We want all tests to be green for > the release. > > > Adrian: Most of the failing tests are from OB. Someone said Lukas > made all those tests green, but they are commited in his repo. > Someone should merge that with the wiresong repo. If no one merge > that, I don't know what to do: or remove them or keep them. > > The only 3 tests no related with OB that are failing are: > > ObjectFinalizerTests >> testFinalizationOfEquals > > This one is failure, but running it again, it is green. Any idea? > > ReleaseTest >> testUndeclared > > failes. > > WeakSetInspectorTest >> testSymbolTableM6812 > > Related to NewInspector. I cc Frederic. > > Cheers > > Mariano > > Cheers, > Adrian > > _______________________________________________ > 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

Jan. 10, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Lukas Renggli

> Adrian: Most of the failing tests are from OB. Someone said Lukas made all > those tests green, but they are commited in his repo. Someone should merge > that with the wiresong repo. If no one merge that, I don't know what to do: > or remove them or keep them. Use the code from my repository. However, there are currently 4 broken tests as you can see on the build server <http://hudson.lukas-renggli.ch/job/Development/lastCompletedBuild/testRepor…>. Looks like some kind of a side-effect on the headless linux VM, because I don't observe them in my image. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 10, 2010

[Pharo-project] Categorizing method extension with pragma

by CÃ©drick BÃ©ler

Hi, Just a 2 cents thought on method extension. Why not associating a pragma instead of using the package name prefixed by a star ? Say there is a package named MyPackage and I override a method in String or add a new one. What I'd like is keeping the original method category name (or find an appropriate one) instead of using *mypackage. For instance: String>>aMethod <package: MyPackage> ... ... ^result Then, we would have to adapt monticello for that purpose. We could also use dynamic protocols to get the list of extension method by package. What does other think ? I find it could be a good starting point to deal with packages. -- CÃ©drick

Jan. 10, 2010