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

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

by Mariano Martinez Peck

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. > It would be nice that you could help with the testing. But so far, all the configuration of our stuff is in Metacello configurations. If you see the script I used to create the PharoDev image, I just used the ConfigurationOfMetacello. The same with Seaide. The idea is to use that. With this we can also collaborate with Gemstone, Squeak and Metacello. If you test and report issues every month for the Dev image, trying to load Seaside with the configuration, it is exactly the same as having the web image. So, please, report your real problem (right now you just said it didn't work) to Metacello mailing list, copy also Pharo if you want, so that people can help and fix the problems. > I won't get very far with that if Seaside won't load. > > As Seaside people to write a Configuration that loads in Pharo. Moose people build their own. Glass the same. But I guess they will told you the same as me. > > > ------------------------------ > *From:* pharo-project-bounces(a)lists.gforge.inria.fr [mailto: > pharo-project-bounces(a)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(a)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(a)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 >

Jan. 9, 2010

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

by Schwab,Wilhelm K

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<mailto:bschwab@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> [mailto:pharo-project-bounces@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<mailto:Pharo-project@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<mailto:bschwab@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> [mailto:pharo-project-bounces@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<mailto:Pharo-project@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<mailto:miguel.coba@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<mailto:Pharo-project@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<mailto:Pharo-project@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<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 9, 2010

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

by Mariano Martinez Peck

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(a)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(a)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 >

Jan. 9, 2010

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

by Mariano Martinez Peck

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 ? Cheers Mariano 2010/1/9 Benoit St-Jean <bstjean(a)yahoo.com> > Win XP, SP3 > > Here are the test results, see screenshot attached: > > > > ----------------- > Benoit St-Jean > Yahoo! Messenger: bstjean > Blog: lamneth.wordpress.com > A standpoint is an intellectual horizon of radius zero. > (Albert Einstein) > > ------------------------------ > Instant message from any web browser! Try the new * Yahoo! Canada > Messenger for the Web BETA*<http://ca.messenger.yahoo.com/webmessengerpromo.php> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 9, 2010

Re: [Pharo-project] OSProcess

by StÃ©phane Ducasse

;) I asked because I'm using for coral. But people will see. Stef On Jan 9, 2010, at 10:18 PM, David T. Lewis wrote: > On Sat, Jan 09, 2010 at 10:07:17PM +0100, St?phane Ducasse wrote: >> >> On Jan 9, 2010, at 6:26 PM, David T. Lewis wrote: >> >>> Yes, OSProcess is designed to work on Windows also. However, the functionality >>> is limited on Windows and the plugin is not distributed with the Windows VM, so >>> for most people this is not a practical solution. >> >> do you know why? >> Because this would be cool. > > Well, the functionality on Windows was always limited, and people could > always use FFI to start external programs, so I think it has not seemed > very important. > > I wrote OSProcess with a goal of having it work on multiple operating > systems, even though it is doing very platform-specific things. The > design worked well and has been fairly successful, but I have to admit > that I do not personally use Windows very much, and I have not put > much effort into making the Windows version more useful. It's just > one of those projects that's been sitting on my to-do list for way > too long ;-) > > Dave > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 9, 2010

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

by Schwab,Wilhelm K

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. 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<mailto:bschwab@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> [mailto:pharo-project-bounces@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<mailto:Pharo-project@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<mailto:miguel.coba@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<mailto:Pharo-project@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<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 9, 2010

[Pharo-project] rss code.google problem

by StÃ©phane Ducasse

Hi I was used to read the updates of the issue using the rss stream of code.google..... Now when I click on the Read more link about the issue in my rss reader I get http://code.google.com/None/None/issues/detail?id=1765 which means that I cannot go there... do you have the same behavior? Stef

Jan. 9, 2010

Re: [Pharo-project] OSProcess

by David T. Lewis

On Sat, Jan 09, 2010 at 10:07:17PM +0100, St?phane Ducasse wrote: > > On Jan 9, 2010, at 6:26 PM, David T. Lewis wrote: > > > Yes, OSProcess is designed to work on Windows also. However, the functionality > > is limited on Windows and the plugin is not distributed with the Windows VM, so > > for most people this is not a practical solution. > > do you know why? > Because this would be cool. Well, the functionality on Windows was always limited, and people could always use FFI to start external programs, so I think it has not seemed very important. I wrote OSProcess with a goal of having it work on multiple operating systems, even though it is doing very platform-specific things. The design worked well and has been fairly successful, but I have to admit that I do not personally use Windows very much, and I have not put much effort into making the Windows version more useful. It's just one of those projects that's been sitting on my to-do list for way too long ;-) Dave

Jan. 9, 2010

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

by Benoit St-Jean

Win XP, SP3 Here are the test results, see screenshot attached: ----------------- Benoit St-Jean Yahoo! Messenger: bstjean Blog: lamneth.wordpress.com A standpoint is an intellectual horizon of radius zero. (Albert Einstein) __________________________________________________________________ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now http://ca.toolbar.yahoo.com.

Jan. 9, 2010

Re: [Pharo-project] [ANN] Hudson continuous integration server support

by StÃ©phane Ducasse

can add a page on the wiki to mention it. Stef On Jan 9, 2010, at 10:04 PM, Mariano Martinez Peck wrote: > Cool. I commited the bash scripts files to: > > https://scm.gforge.inria.fr/svn/pharo/BuildImages > > cheers > > mariano > > On Sat, Jan 9, 2010 at 9:53 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > mariano this is public on the web site :) > on forge page of the pharo project at inria. > https://gforge.inria.fr/scm/?group_id=1299 > Normal svn > > svn checkout svn://scm.gforge.inria.fr/svn/pharo > svn checkout --username login https://scm.gforge.inria.fr/svn/pharo > > :) > > On Jan 9, 2010, at 5:02 PM, Mariano Martinez Peck wrote: > > > > > > > On Sat, Jan 9, 2010 at 4:54 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > we could host that using the pharo svn account at inria gforge > > > > > > Stef: would you mind sending me in a private email all the information about Pharo SVN ? > > > > I refactor (support for Mac OS, cleanup squeak stuff and old stuff ) Damien's bash scripts to build images and I want to start to version them. > > > > Cheers > > > > Mariano > > > > Stef > > > > On Jan 9, 2010, at 3:31 PM, Lukas Renggli wrote: > > > > >>> So here's a new idea. Keep the package-cache from the previous build, > > >>> and make sure the build image can make use of it -- I'm not sure of the > > >>> Gofer/Monticello details. > > >> > > >> Yeah, Gofer would benefit from the package cache. As far as I know > > >> Hudson however cleans the workspace with every new build. I don't know > > >> how the package cache could be saved over. > > > > > > I do keep a global package-cache now, we'll see tomorrow if the builds > > > are faster. > > > > > > I've departed quite a bit from the scripts of Yanni. I generalize > > > everything into a single script that can then be parametrized from > > > Hudson. I have everything in a private Git repository. How can I > > > contribute it back? > > > > > > Lukas > > > > > > > > > > > > > > >> > > >> Lukas > > >> > > >> -- > > >> Lukas Renggli > > >> http://www.lukas-renggli.ch > > >> > > > > > > > > > > > > -- > > > 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 > > > _______________________________________________ > 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. 9, 2010