[Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
Hi Folks/Beta-Testers! I have prepare a new PharoDev image. This image, has same differences with the previous ones that you should know: 1) This is the first Dev image I ever prepare. I adapt to Mac OS Damien's bash scripts to build them and I also cleanup all the Squeak stuff from those bash scripts. So, maybe there are some problems. Forgive me if this is the case. I would like you to check, not only the Image in itself but also the zip. The package.txt, changelog, the fonts, etc. 2) This image puts TrueType fonts again. We won't put StrikeFonts or DejaVu package until there is big bug with them. We know those fonts are faster, but still a bit buggy. If you fix those issues, cool! 3) This image DOES NOT include O2. I know there are a lot of people who use it (mostly in Moose), but unfortunately, this was a decision taken. O2 depends and overrides OB making this more unstable sometimes. The same as the TrueType, we will put O2 again when this can be perfectly load in a PharoCore image without anything about OB. Sorry, but we rather affect only O2 users and not all. If you want packages support, then help in O2 development. 4) In previous Dev images only tests from PharoCore were included. Now, it also includes the tests from the external packages loaded. 5) This image was build using Metacello configurations. If you want, compare the installScript.st from this image to the previous one. 6) There is no Web image this time. If you want to install Seaside 2.8.4 evaluate: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside28'; load. (Smalltalk at: #ConfigurationOfSeaside28) load And if you want Seaside 3.0 evaluate: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load. (Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion However, I am not sure if this is perfectly working in Pharo. Ok .... Here is the link: https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1.... I will wait a couple of days now and I will also start to use this image for my development. If there are issues, report them. If we have big issues, this image is not release. On the other hand, if it works well, we release it.
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. Shouldn't be this a RC 2? because there is a new build process and has nothing to do with the RC1? Also, the changes files, shouldn't be compressed for each RC and for the final release? 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 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 all this setup can be put in a post-script in the ConfigurationOfPharo class. That's all for now. I'm going to use this image to work the following days. Cheers and keep the good work. -- Miguel Cobá http://miguel.leugim.com.mx
2010/1/9 Miguel Enrique Cobá Martinez <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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Gofer seaside28 load does not work. What is the correct way to install Seaside - I can't do much w/o it. ________________________________ From: 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@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@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@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
2010/1/9 Schwab,Wilhelm K <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@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@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@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
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@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@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 2010/1/9 Schwab,Wilhelm K <bschwab@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@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@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@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@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@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
2010/1/9 Schwab,Wilhelm K <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@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@lists.gforge.inria.fr *Subject:* Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@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@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
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@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@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 2010/1/9 Schwab,Wilhelm K <bschwab@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@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@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@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@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@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@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@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@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@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
2010/1/9 Schwab,Wilhelm K <bschwab@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@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@lists.gforge.inria.fr *Subject:* Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@lists.gforge.inria.fr *Subject:* Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@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@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
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@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@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@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@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@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
El dom, 10-01-2010 a las 00:08 +0100, Matthias Berth escribió:
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.
But isn't the loader alpha yet? I mean, I am really expecting for Esteban to release it because is more concise to write commands, but the issue here is the testing of the 1.0 release of pharo with the current available/stable tools, that is, monticello, gofer and metacello. Cheers -- Miguel Cobá http://miguel.leugim.com.mx
2010/1/10 Miguel Enrique Cobá Martinez <miguel.coba@gmail.com>
El dom, 10-01-2010 a las 00:08 +0100, Matthias Berth escribió:
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.
But isn't the loader alpha yet?
Maybe even before. Hoever, it does not make sense. Loader is just a simplifier API to metacello. If Loader works with Seaside2.8, ConfigurationOfSeaside28 MUST work too.
I mean, I am really expecting for Esteban to release it because is more concise to write commands, but the issue here is the testing of the 1.0 release of pharo with the current available/stable tools, that is, monticello, gofer and metacello.
Yes, please. Let's try to use this tools first. When we are stable enough we start with another ones. Cheers Mariano Cheers
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Mariano, Whether it makes sense or not, try it yourself. Either Loader is more than you think it is, or it does something that is critical to allowing Metacello to succeed. Bill ________________________________ From: 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 6:37 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 2010/1/10 Miguel Enrique Cobá Martinez <miguel.coba@gmail.com<mailto:miguel.coba@gmail.com>> El dom, 10-01-2010 a las 00:08 +0100, Matthias Berth escribió:
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.
But isn't the loader alpha yet? Maybe even before. Hoever, it does not make sense. Loader is just a simplifier API to metacello. If Loader works with Seaside2.8, ConfigurationOfSeaside28 MUST work too. I mean, I am really expecting for Esteban to release it because is more concise to write commands, but the issue here is the testing of the 1.0 release of pharo with the current available/stable tools, that is, monticello, gofer and metacello. Yes, please. Let's try to use this tools first. When we are stable enough we start with another ones. Cheers Mariano Cheers -- Miguel Cobá http://miguel.leugim.com.mx _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
2010/1/10 Schwab,Wilhelm K <bschwab@anest.ufl.edu>
Mariano,
Whether it makes sense or not, try it yourself. Either Loader is more than you think it is, or it does something that is critical to allowing Metacello to succeed.
Can you try this and tell me if it works: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside28'; load. ((Smalltalk at: #ConfigurationOfSeaside28) project version: '2.8.4.2') load
Bill
------------------------------ *From:* 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 6:37 PM
*To:* Pharo-project@lists.gforge.inria.fr *Subject:* Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/10 Miguel Enrique Cobá Martinez <miguel.coba@gmail.com>
El dom, 10-01-2010 a las 00:08 +0100, Matthias Berth escribió:
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.
But isn't the loader alpha yet?
Maybe even before. Hoever, it does not make sense. Loader is just a simplifier API to metacello. If Loader works with Seaside2.8, ConfigurationOfSeaside28 MUST work too.
I mean, I am really expecting for Esteban to release it because is more concise to write commands, but the issue here is the testing of the 1.0 release of pharo with the current available/stable tools, that is, monticello, gofer and metacello.
Yes, please. Let's try to use this tools first. When we are stable enough we start with another ones.
Cheers
Mariano
Cheers
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
That does work. As with the Loader solution, it prompts for the user name and password; other solutions available trap those and provide reasonable defaults, which is nice for automated builds. ________________________________ From: 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 7:34 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 2010/1/10 Schwab,Wilhelm K <bschwab@anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> Mariano, Whether it makes sense or not, try it yourself. Either Loader is more than you think it is, or it does something that is critical to allowing Metacello to succeed. Can you try this and tell me if it works: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside28'; load. ((Smalltalk at: #ConfigurationOfSeaside28) project version: '2.8.4.2') load Bill ________________________________ From: pharo-project-bounces@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 6:37 PM To: Pharo-project@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/10 Miguel Enrique Cobá Martinez <miguel.coba@gmail.com<mailto:miguel.coba@gmail.com>> El dom, 10-01-2010 a las 00:08 +0100, Matthias Berth escribió:
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.
But isn't the loader alpha yet? Maybe even before. Hoever, it does not make sense. Loader is just a simplifier API to metacello. If Loader works with Seaside2.8, ConfigurationOfSeaside28 MUST work too. I mean, I am really expecting for Esteban to release it because is more concise to write commands, but the issue here is the testing of the 1.0 release of pharo with the current available/stable tools, that is, monticello, gofer and metacello. Yes, please. Let's try to use this tools first. When we are stable enough we start with another ones. Cheers Mariano Cheers -- Miguel Cobá http://miguel.leugim.com.mx _______________________________________________ Pharo-project mailing list Pharo-project@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@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
2010/1/10 Schwab,Wilhelm K <bschwab@anest.ufl.edu>
That does work.
You see ? It was a matter of the version, no more than that. Now you have your PharoWeb image :)
As with the Loader solution, it prompts for the user name and password; other solutions available trap those and provide reasonable defaults, which is nice for automated builds.
Yes true. However, maybe other people rather to put a real username and password. I think this is more flexible. It would be cool to hear opinions.
------------------------------ *From:* 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 7:34 PM
*To:* Pharo-project@lists.gforge.inria.fr *Subject:* Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/10 Schwab,Wilhelm K <bschwab@anest.ufl.edu>
Mariano,
Whether it makes sense or not, try it yourself. Either Loader is more than you think it is, or it does something that is critical to allowing Metacello to succeed.
Can you try this and tell me if it works:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside28'; load.
((Smalltalk at: #ConfigurationOfSeaside28) project version: '2.8.4.2') load
Bill
------------------------------ *From:* 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 6:37 PM
*To:* Pharo-project@lists.gforge.inria.fr *Subject:* Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/10 Miguel Enrique Cobá Martinez <miguel.coba@gmail.com>
El dom, 10-01-2010 a las 00:08 +0100, Matthias Berth escribió:
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.
But isn't the loader alpha yet?
Maybe even before. Hoever, it does not make sense. Loader is just a simplifier API to metacello. If Loader works with Seaside2.8, ConfigurationOfSeaside28 MUST work too.
I mean, I am really expecting for Esteban to release it because is more concise to write commands, but the issue here is the testing of the 1.0 release of pharo with the current available/stable tools, that is, monticello, gofer and metacello.
Yes, please. Let's try to use this tools first. When we are stable enough we start with another ones.
Cheers
Mariano
Cheers
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
this raises the interesting question of headless build testing in presence of popup. So we should have a way to control them from metacello ? On Jan 10, 2010, at 1:52 AM, Mariano Martinez Peck wrote:
2010/1/10 Schwab,Wilhelm K <bschwab@anest.ufl.edu> That does work.
You see ? It was a matter of the version, no more than that. Now you have your PharoWeb image :)
As with the Loader solution, it prompts for the user name and password; other solutions available trap those and provide reasonable defaults, which is nice for automated builds.
Yes true. However, maybe other people rather to put a real username and password. I think this is more flexible. It would be cool to hear opinions.
From: 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 7:34 PM
To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/10 Schwab,Wilhelm K <bschwab@anest.ufl.edu> Mariano,
Whether it makes sense or not, try it yourself. Either Loader is more than you think it is, or it does something that is critical to allowing Metacello to succeed.
Can you try this and tell me if it works:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside28'; load.
((Smalltalk at: #ConfigurationOfSeaside28) project version: '2.8.4.2') load
Bill
From: 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 6:37 PM
To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/10 Miguel Enrique Cobá Martinez <miguel.coba@gmail.com> El dom, 10-01-2010 a las 00:08 +0100, Matthias Berth escribió:
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.
But isn't the loader alpha yet?
Maybe even before. Hoever, it does not make sense. Loader is just a simplifier API to metacello. If Loader works with Seaside2.8, ConfigurationOfSeaside28 MUST work too.
I mean, I am really expecting for Esteban to release it because is more concise to write commands, but the issue here is the testing of the 1.0 release of pharo with the current available/stable tools, that is, monticello, gofer and metacello.
Yes, please. Let's try to use this tools first. When we are stable enough we start with another ones.
Cheers
Mariano
Cheers
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Miguel, My concern is over testing of the RC images. Whether Loader is alpha or not seems a little less important than providing what people will need in order to test. As a friend of mine would say, "don't make it hard on people to help you." I will gladly download a web image, run something in production, or run an alpha installer. The important thing is to have a clear message and a working solution to the problem. Bill -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Miguel Enrique Cobá Martinez Sent: Saturday, January 09, 2010 6:21 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 El dom, 10-01-2010 a las 00:08 +0100, Matthias Berth escribió:
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.
But isn't the loader alpha yet? I mean, I am really expecting for Esteban to release it because is more concise to write commands, but the issue here is the testing of the 1.0 release of pharo with the current available/stable tools, that is, monticello, gofer and metacello. Cheers -- Miguel Cobá http://miguel.leugim.com.mx _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
El sáb, 09-01-2010 a las 18:58 -0500, Schwab,Wilhelm K escribió:
Miguel,
My concern is over testing of the RC images. Whether Loader is alpha or not seems a little less important than providing what people will need in order to test. As a friend of mine would say, "don't make it hard on people to help you."
I will gladly download a web image, run something in production, or run an alpha installer. The important thing is to have a clear message and a working solution to the problem.
Bill
Yes, but Loader hasn't been announced yet. That is the point. Lets concentrate in Gofer/Metacello that is the _blessed_ way to install in Pharo 1.0 Cheers
-----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Miguel Enrique Cobá Martinez Sent: Saturday, January 09, 2010 6:21 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
El dom, 10-01-2010 a las 00:08 +0100, Matthias Berth escribió:
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.
But isn't the loader alpha yet?
I mean, I am really expecting for Esteban to release it because is more concise to write commands, but the issue here is the testing of the 1.0 release of pharo with the current available/stable tools, that is, monticello, gofer and metacello.
Cheers
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Miguel Cobá http://miguel.leugim.com.mx
Whatever you guys want, so long as it indeed works. With the explicit version, ConfigurationOfSeaside28 seems to do the trick. I suggest adding a link to the downloads page with code for FFI and Seaside for starters. Another idea would be to add class methods to Gofer that use Metacello. The existing #seaside28 should be rewritten or removed. Bill -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Miguel Enrique Cobá Martinez Sent: Saturday, January 09, 2010 7:45 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 El sáb, 09-01-2010 a las 18:58 -0500, Schwab,Wilhelm K escribió:
Miguel,
My concern is over testing of the RC images. Whether Loader is alpha or not seems a little less important than providing what people will need in order to test. As a friend of mine would say, "don't make it hard on people to help you."
I will gladly download a web image, run something in production, or run an alpha installer. The important thing is to have a clear message and a working solution to the problem.
Bill
Yes, but Loader hasn't been announced yet. That is the point. Lets concentrate in Gofer/Metacello that is the _blessed_ way to install in Pharo 1.0 Cheers
-----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Miguel Enrique Cobá Martinez Sent: Saturday, January 09, 2010 6:21 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
El dom, 10-01-2010 a las 00:08 +0100, Matthias Berth escribió:
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.
But isn't the loader alpha yet?
I mean, I am really expecting for Esteban to release it because is more concise to write commands, but the issue here is the testing of the 1.0 release of pharo with the current available/stable tools, that is, monticello, gofer and metacello.
Cheers
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Miguel Cobá http://miguel.leugim.com.mx _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Sun, Jan 10, 2010 at 1:57 AM, Schwab,Wilhelm K <bschwab@anest.ufl.edu>wrote:
Whatever you guys want, so long as it indeed works. With the explicit version, ConfigurationOfSeaside28 seems to do the trick. I suggest adding a link to the downloads page with code for FFI and Seaside for starters.
Ok. I will add that piece of code in my next Ann and maybe Adrian can add something to the website. We should also try ConfigurationOfSeaside30 and how does it works, although I am almost sure it works. To try to install the latest version: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load. ((Smalltalk at: #ConfigurationOfSeaside30) load Cheers Mariano
Another idea would be to add class methods to Gofer that use Metacello. The existing #seaside28 should be rewritten or removed.
Yes, true. However, this was already discussed, and the conclusion was that it has no sense because we will then have Loader. But, you can read the thread in this mailing list with subject "Metacello configurations for Pharo" Cheers Mariano
Bill
-----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto: pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Miguel Enrique Cobá Martinez Sent: Saturday, January 09, 2010 7:45 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
El sáb, 09-01-2010 a las 18:58 -0500, Schwab,Wilhelm K escribió:
Miguel,
My concern is over testing of the RC images. Whether Loader is alpha or not seems a little less important than providing what people will need in order to test. As a friend of mine would say, "don't make it hard on people to help you."
I will gladly download a web image, run something in production, or run an alpha installer. The important thing is to have a clear message and a working solution to the problem.
Bill
Yes, but Loader hasn't been announced yet. That is the point. Lets concentrate in Gofer/Metacello that is the _blessed_ way to install in Pharo 1.0
Cheers
-----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Miguel Enrique Cobá Martinez Sent: Saturday, January 09, 2010 6:21 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
El dom, 10-01-2010 a las 00:08 +0100, Matthias Berth escribió:
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.
But isn't the loader alpha yet?
I mean, I am really expecting for Esteban to release it because is more
concise to write commands, but the issue here is the testing of the 1.0 release of pharo with the current available/stable tools, that is, monticello, gofer and metacello.
Cheers
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Why does 2.8 need an explicit version, but 3.0 does not? Beyond that, the 3.0 install runs, but I'm getting ready to cut it off - Seaside 3.0 _can't_ be big enough to justify the work that is happening (I hope). It might be stuck in a loop, because I have seen myriad progress bars that got nowhere close to completion. Re user name and password, #load prompts #loadUser:password: - no prompts Bill ________________________________ From: 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 8:08 PM To: Pharo-project@lists.gforge.inria.fr Cc: Adrian Lienhard Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 On Sun, Jan 10, 2010 at 1:57 AM, Schwab,Wilhelm K <bschwab@anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> wrote: Whatever you guys want, so long as it indeed works. With the explicit version, ConfigurationOfSeaside28 seems to do the trick. I suggest adding a link to the downloads page with code for FFI and Seaside for starters. Ok. I will add that piece of code in my next Ann and maybe Adrian can add something to the website. We should also try ConfigurationOfSeaside30 and how does it works, although I am almost sure it works. To try to install the latest version: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load. ((Smalltalk at: #ConfigurationOfSeaside30) load Cheers Mariano Another idea would be to add class methods to Gofer that use Metacello. The existing #seaside28 should be rewritten or removed. Yes, true. However, this was already discussed, and the conclusion was that it has no sense because we will then have Loader. But, you can read the thread in this mailing list with subject "Metacello configurations for Pharo" Cheers Mariano Bill -----Original Message----- From: pharo-project-bounces@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 Miguel Enrique Cobá Martinez Sent: Saturday, January 09, 2010 7:45 PM To: Pharo-project@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 El sáb, 09-01-2010 a las 18:58 -0500, Schwab,Wilhelm K escribió:
Miguel,
My concern is over testing of the RC images. Whether Loader is alpha or not seems a little less important than providing what people will need in order to test. As a friend of mine would say, "don't make it hard on people to help you."
I will gladly download a web image, run something in production, or run an alpha installer. The important thing is to have a clear message and a working solution to the problem.
Bill
Yes, but Loader hasn't been announced yet. That is the point. Lets concentrate in Gofer/Metacello that is the _blessed_ way to install in Pharo 1.0 Cheers
-----Original Message----- From: pharo-project-bounces@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 Miguel Enrique Cobá Martinez Sent: Saturday, January 09, 2010 6:21 PM To: Pharo-project@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
El dom, 10-01-2010 a las 00:08 +0100, Matthias Berth escribió:
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.
But isn't the loader alpha yet?
I mean, I am really expecting for Esteban to release it because is more concise to write commands, but the issue here is the testing of the 1.0 release of pharo with the current available/stable tools, that is, monticello, gofer and metacello.
Cheers
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@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@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Miguel Cobá http://miguel.leugim.com.mx _______________________________________________ Pharo-project mailing list Pharo-project@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@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
+1
Whatever you guys want, so long as it indeed works. With the explicit version, ConfigurationOfSeaside28 seems to do the trick. I suggest adding a link to the downloads page with code for FFI and Seaside for starters.
Another idea would be to add class methods to Gofer that use Metacello. The existing #seaside28 should be rewritten or removed.
Bill
On 2010-01-09 20:21:19 -0300, Miguel Enrique Cobá Martinez <miguel.coba@gmail.com> said:
El dom, 10-01-2010 a las 00:08 +0100, Matthias Berth escribió:
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.
But isn't the loader alpha yet?
I mean, I am really expecting for Esteban to release it because is more concise to write commands, but the issue here is the testing of the 1.0 release of pharo with the current available/stable tools, that is, monticello, gofer and metacello.
Cheers
Yes it is alpha... but just because the lack of testing and documentation (and some complex functionality). I sent a script to Matthias I was using to prepare an image for something private... and at the same time test a little the loader package. I think is very usable now, but as I said, It lacks a lot of testing and documentation, but you can tryit if you want, a little early feedback can be very useful ;) The package has been refactored following Stef suggestions, now you should do something like this: Gofer new squeaksource: 'Loader': package: 'GoferProjectLoader'; load. Gofer project load: 'Seaside28' version: '2.8.4.2'. Cheers, Esteban pd: and now I'm going to prepare my backpack and go out on vacations, or my girlfriend will kill me :P
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@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@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@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@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@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@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@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Sun, Jan 10, 2010 at 12:35 AM, Schwab,Wilhelm K <bschwab@anest.ufl.edu>wrote:
Matthias,
That appears to have worked. Let's see, we have Installer, ScriptLoader,
ScriptLoader is for internal use. If you use it, you are doing something wrong. You should not even be aware of that.
Configuration*,
Is the package managment. If you don't want to have to install all of the dependencies of all packages, and you don't want stable versions, don't use it.
Gofer,
If you don't want to automate your downloads, don't use it. You can use the Monticello Browser if you want.
etc., and now Loader =:0
Loader is not even in beta. And it is just a wrap to make Metacello easier.
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 :)
Esteban is in holidays for 2 weeks. In summary, in my point of view, we now have to concentrate in use Metacello configurations. How you download your ConfXX is your problem. If you want to use Gofer, use it, if don't, user Monticello Browser. Don't use ScriptLoader. Loader shouldn't be used until we are more stable. Cheers Mariano
Thanks!!
Bill
-----Original Message----- From: pharo-project-bounces@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@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@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@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@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@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@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Mariano, I'm aware of ScriptLoader because it is in the image, and presumably I was either told to use it or turned it up by browsing, perhaps for something that would load FFI. If the image is missing critical pieces (FFI, Seaside, etc.), do not be surprised when people resort to search engines and browsers, and might find broken code or things that you do not want them to use. Bill ________________________________ From: 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 7:05 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 On Sun, Jan 10, 2010 at 12:35 AM, Schwab,Wilhelm K <bschwab@anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> wrote: Matthias, That appears to have worked. Let's see, we have Installer, ScriptLoader, ScriptLoader is for internal use. If you use it, you are doing something wrong. You should not even be aware of that. Configuration*, Is the package managment. If you don't want to have to install all of the dependencies of all packages, and you don't want stable versions, don't use it. Gofer, If you don't want to automate your downloads, don't use it. You can use the Monticello Browser if you want. etc., and now Loader =:0 Loader is not even in beta. And it is just a wrap to make Metacello easier. 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 :) Esteban is in holidays for 2 weeks. In summary, in my point of view, we now have to concentrate in use Metacello configurations. How you download your ConfXX is your problem. If you want to use Gofer, use it, if don't, user Monticello Browser. Don't use ScriptLoader. Loader shouldn't be used until we are more stable. Cheers Mariano Thanks!! Bill -----Original Message----- From: pharo-project-bounces@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 Matthias Berth Sent: Saturday, January 09, 2010 6:09 PM To: Pharo-project@lists.gforge.inria.fr<mailto:Pharo-project@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@anest.ufl.edu<mailto:bschwab@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@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:38 PM To: Pharo-project@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@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@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@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@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@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@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@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@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@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@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@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@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@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
2010/1/10 Schwab,Wilhelm K <bschwab@anest.ufl.edu>
Mariano,
I'm aware of ScriptLoader because it is in the image, and presumably I was either told to use it or turned it up by browsing, perhaps for something that would load FFI. If the image is missing critical pieces (FFI, Seaside, etc.), do not be surprised when people resort to search engines and browsers, and might find broken code or things that you do not want them to use.
Yes, true. I didn't mean that YOU were doing something wrong, but that there WERE something wrong. In addition, we have already wrote a ConfigurationOfFFI. Just evaluate: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfFFI'; load. ((Smalltalk at: #ConfigurationOfFFI) project version:'1.0') load Cheers Mariano
Bill
------------------------------ *From:* 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 7:05 PM
*To:* Pharo-project@lists.gforge.inria.fr *Subject:* Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
On Sun, Jan 10, 2010 at 12:35 AM, Schwab,Wilhelm K <bschwab@anest.ufl.edu>wrote:
Matthias,
That appears to have worked. Let's see, we have Installer, ScriptLoader,
ScriptLoader is for internal use. If you use it, you are doing something wrong. You should not even be aware of that.
Configuration*,
Is the package managment. If you don't want to have to install all of the dependencies of all packages, and you don't want stable versions, don't use it.
Gofer,
If you don't want to automate your downloads, don't use it. You can use the Monticello Browser if you want.
etc., and now Loader =:0
Loader is not even in beta. And it is just a wrap to make Metacello easier.
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 :)
Esteban is in holidays for 2 weeks.
In summary, in my point of view, we now have to concentrate in use Metacello configurations. How you download your ConfXX is your problem. If you want to use Gofer, use it, if don't, user Monticello Browser. Don't use ScriptLoader. Loader shouldn't be used until we are more stable.
Cheers
Mariano
Thanks!!
Bill
-----Original Message----- From: pharo-project-bounces@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@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@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@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@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@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@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Very good - I will get that into Migrate. Bill ________________________________ From: 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 7:37 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 2010/1/10 Schwab,Wilhelm K <bschwab@anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> Mariano, I'm aware of ScriptLoader because it is in the image, and presumably I was either told to use it or turned it up by browsing, perhaps for something that would load FFI. If the image is missing critical pieces (FFI, Seaside, etc.), do not be surprised when people resort to search engines and browsers, and might find broken code or things that you do not want them to use. Yes, true. I didn't mean that YOU were doing something wrong, but that there WERE something wrong. In addition, we have already wrote a ConfigurationOfFFI. Just evaluate: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfFFI'; load. ((Smalltalk at: #ConfigurationOfFFI) project version:'1.0') load Cheers Mariano Bill ________________________________ From: pharo-project-bounces@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 7:05 PM To: Pharo-project@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 On Sun, Jan 10, 2010 at 12:35 AM, Schwab,Wilhelm K <bschwab@anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> wrote: Matthias, That appears to have worked. Let's see, we have Installer, ScriptLoader, ScriptLoader is for internal use. If you use it, you are doing something wrong. You should not even be aware of that. Configuration*, Is the package managment. If you don't want to have to install all of the dependencies of all packages, and you don't want stable versions, don't use it. Gofer, If you don't want to automate your downloads, don't use it. You can use the Monticello Browser if you want. etc., and now Loader =:0 Loader is not even in beta. And it is just a wrap to make Metacello easier. 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 :) Esteban is in holidays for 2 weeks. In summary, in my point of view, we now have to concentrate in use Metacello configurations. How you download your ConfXX is your problem. If you want to use Gofer, use it, if don't, user Monticello Browser. Don't use ScriptLoader. Loader shouldn't be used until we are more stable. Cheers Mariano Thanks!! Bill -----Original Message----- From: pharo-project-bounces@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 Matthias Berth Sent: Saturday, January 09, 2010 6:09 PM To: Pharo-project@lists.gforge.inria.fr<mailto:Pharo-project@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@anest.ufl.edu<mailto:bschwab@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@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:38 PM To: Pharo-project@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@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@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@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@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@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@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@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@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@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@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@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@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@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@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
2010/1/10 Schwab,Wilhelm K <bschwab@anest.ufl.edu>
Very good - I will get that into Migrate.
Cool. I recommend you that check all the available projects in MetacelloRepository and help to write the ones that are missing for you. Cheers Mariano
Bill
------------------------------ *From:* 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 7:37 PM
*To:* Pharo-project@lists.gforge.inria.fr *Subject:* Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/10 Schwab,Wilhelm K <bschwab@anest.ufl.edu>
Mariano,
I'm aware of ScriptLoader because it is in the image, and presumably I was either told to use it or turned it up by browsing, perhaps for something that would load FFI. If the image is missing critical pieces (FFI, Seaside, etc.), do not be surprised when people resort to search engines and browsers, and might find broken code or things that you do not want them to use.
Yes, true. I didn't mean that YOU were doing something wrong, but that there WERE something wrong.
In addition, we have already wrote a ConfigurationOfFFI. Just evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfFFI'; load.
((Smalltalk at: #ConfigurationOfFFI) project version:'1.0') load
Cheers
Mariano
Bill
------------------------------ *From:* 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 7:05 PM
*To:* Pharo-project@lists.gforge.inria.fr *Subject:* Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
On Sun, Jan 10, 2010 at 12:35 AM, Schwab,Wilhelm K <bschwab@anest.ufl.edu
wrote:
Matthias,
That appears to have worked. Let's see, we have Installer, ScriptLoader,
ScriptLoader is for internal use. If you use it, you are doing something wrong. You should not even be aware of that.
Configuration*,
Is the package managment. If you don't want to have to install all of the dependencies of all packages, and you don't want stable versions, don't use it.
Gofer,
If you don't want to automate your downloads, don't use it. You can use the Monticello Browser if you want.
etc., and now Loader =:0
Loader is not even in beta. And it is just a wrap to make Metacello easier.
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 :)
Esteban is in holidays for 2 weeks.
In summary, in my point of view, we now have to concentrate in use Metacello configurations. How you download your ConfXX is your problem. If you want to use Gofer, use it, if don't, user Monticello Browser. Don't use ScriptLoader. Loader shouldn't be used until we are more stable.
Cheers
Mariano
Thanks!!
Bill
-----Original Message----- From: pharo-project-bounces@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@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@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@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@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@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@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
El sáb, 09-01-2010 a las 19:19 -0500, Schwab,Wilhelm K escribió:
Mariano,
I'm aware of ScriptLoader because it is in the image, and presumably I was either told to use it or turned it up by browsing, perhaps for something that would load FFI. If the image is missing critical pieces (FFI, Seaside, etc.), do not be surprised when people resort to search engines and browsers, and might find broken code or things that you do not want them to use.
As I understand it, ScriptLoader will be deprecated and removed from images with the advent of Gofer/Metacello. Loader is a way to access Gofer/Metacello in a less verbose way. As stated before, isn't even beta, so don't use it for real apps, unless you're helping Esteban with feedback. So, for pharo the way to go is Gofer and Metacello at least for release 1.0. Cheers
Bill
______________________________________________________________________ From: 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 7:05 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
On Sun, Jan 10, 2010 at 12:35 AM, Schwab,Wilhelm K <bschwab@anest.ufl.edu> wrote: Matthias,
That appears to have worked. Let's see, we have Installer, ScriptLoader,
ScriptLoader is for internal use. If you use it, you are doing something wrong. You should not even be aware of that.
Configuration*,
Is the package managment. If you don't want to have to install all of the dependencies of all packages, and you don't want stable versions, don't use it.
Gofer,
If you don't want to automate your downloads, don't use it. You can use the Monticello Browser if you want.
etc., and now Loader =:0
Loader is not even in beta. And it is just a wrap to make Metacello easier.
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 :)
Esteban is in holidays for 2 weeks.
In summary, in my point of view, we now have to concentrate in use Metacello configurations. How you download your ConfXX is your problem. If you want to use Gofer, use it, if don't, user Monticello Browser. Don't use ScriptLoader. Loader shouldn't be used until we are more stable.
Cheers
Mariano
Thanks!!
Bill
-----Original Message----- From: pharo-project-bounces@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@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@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@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@lists.gforge.inria.fr > Subject: Re: [Pharo-project] [BetaTesting] [ANN] > Pharo1.0-10505-rc1dev10.01.1 > > > > 2010/1/9 Schwab,Wilhelm K <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@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@lists.gforge.inria.fr >> Subject: Re: [Pharo-project] [BetaTesting] [ANN] >> Pharo1.0-10505-rc1dev10.01.1 >> >> >> >> 2010/1/9 Schwab,Wilhelm K <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@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@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@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@lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project@lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project@lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Miguel Cobá http://miguel.leugim.com.mx
As I understand it, ScriptLoader will be deprecated and removed from images with the advent of Gofer/Metacello.
Yes may be not tomorrow because we have a lot of nice=ugly behavior but yes this is the idea.
Loader is a way to access Gofer/Metacello in a less verbose way. As stated before, isn't even beta, so don't use it for real apps, unless you're helping Esteban with feedback.
So, for pharo the way to go is Gofer and Metacello at least for release 1.0.
Yes Especially since I would like to see if conceptually Loader is not just a special subclass of Gofer GoferConfigLoader to shirnk the vocabulary
+1
That appears to have worked. Let's see, we have Installer, ScriptLoader,
ScriptLoader is for internal use. If you use it, you are doing something wrong. You should not even be aware of that.
Configuration*,
Is the package managment. If you don't want to have to install all of the dependencies of all packages, and you don't want stable versions, don't use it.
Gofer,
If you don't want to automate your downloads, don't use it. You can use the Monticello Browser if you want.
etc., and now Loader =:0
Loader is not even in beta. And it is just a wrap to make Metacello easier.
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 :)
Esteban is in holidays for 2 weeks.
In summary, in my point of view, we now have to concentrate in use Metacello configurations. How you download your ConfXX is your problem. If you want to use Gofer, use it, if don't, user Monticello Browser. Don't use ScriptLoader. Loader shouldn't be used until we are more stable.
Cheers
Mariano
Thanks!!
Bill
-----Original Message----- From: pharo-project-bounces@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@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@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@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@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@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@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
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@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@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@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@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@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@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@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@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Sun, Jan 10, 2010 at 2:16 PM, Matthias Berth < matthias.berth@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@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@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@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@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@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@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@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@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
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@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@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@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@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@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@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
2010/1/9 Schwab,Wilhelm K <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@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@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@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Gofer seaside28 load
does not work. What is the correct way to install Seaside - I can't do much w/o it.
"Does not work" doesn't say much. Can you be more specific? Lukas -- Lukas Renggli http://www.lukas-renggli.ch
El sáb, 09-01-2010 a las 21:00 +0100, Mariano Martinez Peck escribió:
2010/1/9 Miguel Enrique Cobá Martinez <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 ?
Maybe you can use two scripts, one for configuring the proxy and other for the gofer/metacello configuration. Then before zipping the files, delete the proxy settings one. Also, don't the settings remain configured in the image on the snapshot:andQuit message. If so, a post-script to clear the parameter is needed too.
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 ?
I think that is good to have a RC2. Also this shows progress to the public.
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:
I don't know the exact message to condense changes, but if it is that then yes, should be added near the end of the other instructions.
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.
Respect to this list, and maybe this should be a ticket. Shouldn't be better to have an established message to cleanup the image on release. Something like the cleanUpForImageRelease but generalized and then, the classes that need to do something like this, they implement that message. So on release a new image version you only call something like Smalltalk cleanUpForImageRelease. and inside it search all the classes that implements the message and call them. So, your post-script becomes a single line and each package is responsible of putting inside its own cleanUpForImageRelease whatever needed to initialize itself. But well, just an idea for subsequent releases.
Do you think something else should be addded? Maybe we can reuse ScriptLoader cleanings ?
Yes, and also the GarbageCollector parameters that John McIntosh is preparing. This must be part of Pharo 1.0 without doubts.
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.
Yes, both options have pros and cons. Pros - Can fix bugs after release - Can aply improvements to the image after release. Cons - Can mess the image of someone by overwriting some overridden method. - Can accidentally update more than intended in someone's image Should we vote?
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
Cheers -- Miguel Cobá http://miguel.leugim.com.mx
2010/1/9 Miguel Enrique Cobá Martinez <miguel.coba@gmail.com>
El sáb, 09-01-2010 a las 21:00 +0100, Mariano Martinez Peck escribió:
2010/1/9 Miguel Enrique Cobá Martinez <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 ?
Maybe you can use two scripts, one for configuring the proxy and other for the gofer/metacello configuration. Then before zipping the files, delete the proxy settings one. Also, don't the settings remain configured in the image on the snapshot:andQuit message. If so, a post-script to clear the parameter is needed too.
Thanks Miguel. I really appreciate this kind of feedback. It is fixed now.
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 ?
I think that is good to have a RC2. Also this shows progress to the public.
Ok, next release will be rc2.
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:
I don't know the exact message to condense changes, but if it is that then yes, should be added near the end of the other instructions.
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.
Respect to this list, and maybe this should be a ticket. Shouldn't be better to have an established message to cleanup the image on release. Something like the cleanUpForImageRelease but generalized and then, the classes that need to do something like this, they implement that message.
So on release a new image version you only call something like
Smalltalk cleanUpForImageRelease.
It is already in ScriptLoader >> cleanUpForRelease I will try to look at the differences with ImageForDevelopers >> cleanUpMemory and see what can I do.
and inside it search all the classes that implements the message and call them. So, your post-script becomes a single line and each package is responsible of putting inside its own cleanUpForImageRelease whatever needed to initialize itself. But well, just an idea for subsequent releases.
Do you think something else should be addded? Maybe we can reuse ScriptLoader cleanings ?
Yes, and also the GarbageCollector parameters that John McIntosh is preparing. This must be part of Pharo 1.0 without doubts.
I am now aware of this.
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.
Yes, both options have pros and cons.
Pros - Can fix bugs after release - Can aply improvements to the image after release.
Cons - Can mess the image of someone by overwriting some overridden method. - Can accidentally update more than intended in someone's image
Should we vote?
yes, send a separate email with this to hear opinions.
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
Cheers
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Respect to this list, and maybe this should be a ticket. Shouldn't be better to have an established message to cleanup the image on release. Something like the cleanUpForImageRelease but generalized and then, the classes that need to do something like this, they implement that message.
So on release a new image version you only call something like
Smalltalk cleanUpForImageRelease.
It is already in ScriptLoader >> cleanUpForRelease
miguel proposes modular cleanUpForRelease solution. Keith in kernel extensions propose that and we should have a look at what he did I remember reading his code and making a report on the wiki.
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 ?
I think that is good to have a RC2. Also this shows progress to the public.
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:
I don't know the exact message to condense changes, but if it is that then yes, should be added near the end of the other instructions.
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.
Respect to this list, and maybe this should be a ticket. Shouldn't be better to have an established message to cleanup the image on release. Something like the cleanUpForImageRelease but generalized and then, the classes that need to do something like this, they implement that message.
So on release a new image version you only call something like
Smalltalk cleanUpForImageRelease.
yes this would be good
and inside it search all the classes that implements the message and call them. So, your post-script becomes a single line and each package is responsible of putting inside its own cleanUpForImageRelease whatever needed to initialize itself. But well, just an idea for subsequent releases.
Do you think something else should be addded? Maybe we can reuse ScriptLoader cleanings ?
Yes, and also the GarbageCollector parameters that John McIntosh is preparing. This must be part of Pharo 1.0 without doubts.
yes
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.
Yes, both options have pros and cons.
Pros - Can fix bugs after release - Can aply improvements to the image after release.
Cons - Can mess the image of someone by overwriting some overridden method. - Can accidentally update more than intended in someone's image
Should we vote?
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
Cheers
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
http://code.google.com/p/pharo/issues/detail?id=1778 Stef On Jan 9, 2010, at 11:59 PM, Miguel Enrique Cobá Martinez wrote:
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.
Respect to this list, and maybe this should be a ticket. Shouldn't be better to have an established message to cleanup the image on release. Something like the cleanUpForImageRelease but generalized and then, the classes that need to do something like this, they implement that message.
So on release a new image version you only call something like
Smalltalk cleanUpForImageRelease.
and inside it search all the classes that implements the message and call them. So, your post-script becomes a single line and each package is responsible of putting inside its own cleanUpForImageRelease whatever needed to initialize itself. But well, just an idea for subsequent releases.
Do you think something else should be addded? Maybe we can reuse ScriptLoader cleanings ?
Yes, and also the GarbageCollector parameters that John McIntosh is preparing. This must be part of Pharo 1.0 without doubts.
I don't know where is this work. Can you please open a ticket and label it as 1.0 and puting the link to the thread ? Thanks Mariano
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.
Yes, both options have pros and cons.
Pros - Can fix bugs after release - Can aply improvements to the image after release.
Cons - Can mess the image of someone by overwriting some overridden method. - Can accidentally update more than intended in someone's image
Should we vote?
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
Cheers
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
I don't know where is this work. Can you please open a ticket and label it as 1.0 and puting the link to the thread ?
http://code.google.com/p/pharo/issues/detail?id=1808
-- Miguel Cobá http://miguel.leugim.com.mx
On Jan 9, 2010, at 8:39 PM, Miguel Enrique Cobá Martinez wrote:
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.
Shouldn't be this a RC 2? because there is a new build process and has nothing to do with the RC1?
yes rc2 mariano pharo-rc2 is not a problem
Also, the changes files, shouldn't be compressed for each RC and for the final release?
Yes probably.
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
This is on the todo of marcus to come up with a HUGE list of actions we did in pharo 1.0 :) in a better way than the update cryptic log.
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
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).
Yeap another interesting point. May be disabling is the easiest solution :)
Maybe all this setup can be put in a post-script in the ConfigurationOfPharo class.
That's all for now. I'm going to use this image to work the following days.
Cheers and keep the good work.
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Also, the changes files, shouldn't be compressed for each RC and for the
final release?
In addition to do a Smalltalk condenseChanges is it necessary to do also a Smalltalk condenseSources ? I ask because I have really no idea. Thanks Mariano
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
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 all this setup can be put in a post-script in the ConfigurationOfPharo class.
That's all for now. I'm going to use this image to work the following days.
Cheers and keep the good work.
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Jan 11, 2010, at 4:37 PM, Mariano Martinez Peck wrote:
Also, the changes files, shouldn't be compressed for each RC and for the final release?
In addition to do a Smalltalk condenseChanges is it necessary to do also a Smalltalk condenseSources ? I ask because I have really no idea.
No, we did that when going RC1... there is already a PharoV10.sources. Marcus
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.
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@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
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. Cheers, Adrian
On Sun, Jan 10, 2010 at 11:34 AM, Adrian Lienhard <adi@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
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/testReport...>. 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
+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/testReport...>. 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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Sun, Jan 10, 2010 at 2:13 PM, Lukas Renggli <renggli@gmail.com> 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/testReport...
. Looks like some kind of a side-effect on the headless linux VM, because I don't observe them in my image.
Lukas: I had most of the tests in red until I install the package OB-Fake Do you know which packages from OB require OB-Fake? After that I have only two tests failing :) - testPushAlpaBeta - testUpdatesSelection The same it is here: http://hudson.lukas-renggli.ch/job/Development/lastCompletedBuild/testReport... :) Thanks Mariano
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Lukas: I had most of the tests in red until I install the package OB-Fake Do you know which packages from OB require OB-Fake?
OB-Fake is a fake view. It is used by all tests that do not test another view (morphic or web).
After that I have only two tests failing :)
- testPushAlpaBeta - testUpdatesSelection
The same it is here: http://hudson.lukas-renggli.ch/job/Development/lastCompletedBuild/testReport...
I fixed the other two bugs, they were caused by a bug in the hudson test runner. Don't know the matter with these buggers. Will have a look later tonight.
:)
Thanks
Mariano
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch
On Sun, Jan 10, 2010 at 5:02 PM, Lukas Renggli <renggli@gmail.com> wrote:
Lukas: I had most of the tests in red until I install the package OB-Fake Do you know which packages from OB require OB-Fake?
OB-Fake is a fake view. It is used by all tests that do not test another view (morphic or web).
Cooool! thanks Lukas :)
After that I have only two tests failing :)
- testPushAlpaBeta - testUpdatesSelection
The same it is here: http://hudson.lukas-renggli.ch/job/Development/lastCompletedBuild/testReport...
I fixed the other two bugs, they were caused by a bug in the hudson test runner. Don't know the matter with these buggers. Will have a look later tonight.
Excellent.
:)
Thanks
Mariano
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
After that I have only two tests failing :)
- testPushAlpaBeta - testUpdatesSelection
The same it is here: http://hudson.lukas-renggli.ch/job/Development/lastCompletedBuild/testReport...
I fixed the other two bugs, they were caused by a bug in the hudson test runner. Don't know the matter with these buggers. Will have a look later tonight.
I cannot reproduce these two bugs. They always appear on the build server, but they pass when I download the exactly same image. Always. Can you debug them? Lukas
:)
Thanks
Mariano
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch
-- Lukas Renggli http://www.lukas-renggli.ch
On Sun, Jan 10, 2010 at 9:45 PM, Lukas Renggli <renggli@gmail.com> wrote:
After that I have only two tests failing :)
- testPushAlpaBeta - testUpdatesSelection
The same it is here: http://hudson.lukas-renggli.ch/job/Development/lastCompletedBuild/testReport...
I fixed the other two bugs, they were caused by a bug in the hudson test runner. Don't know the matter with these buggers. Will have a look later tonight.
I cannot reproduce these two bugs. They always appear on the build server, but they pass when I download the exactly same image. Always.
Can you debug them?
Sure. testPushAlphaBeta fails in self assertSelectionIs: 1. because in assertSelectionIs: anInteger you can see that anInteger and index are both 1, but the button answer false to the message isOn testUpdateSelection fails in self assertSelectionIs: 2 because in assertSelectionIs: anInteger and index are both 2 but isOn returns false.. Som, it seems both issue are due to the same. Let me know what else can I test. Cheers Mariano
Lukas
:)
Thanks
Mariano
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Can you debug them?
Sure. testPushAlphaBeta fails in self assertSelectionIs: 1. because in assertSelectionIs: anInteger
you can see that anInteger and index are both 1, but the button answer false to the message isOn
testUpdateSelection fails in self assertSelectionIs: 2 because in assertSelectionIs: anInteger and index are both 2 but isOn returns false..
Som, it seems both issue are due to the same.
Let me know what else can I test.
I don't know, I was assuming what you said, but I cannot reproduce it. I guess we have to ignore it for now. Lukas
Cheers
Mariano
Lukas
:)
Thanks
Mariano
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch
On Sun, Jan 10, 2010 at 11:05 PM, Lukas Renggli <renggli@gmail.com> wrote:
Can you debug them?
Sure. testPushAlphaBeta fails in self assertSelectionIs: 1. because in assertSelectionIs: anInteger
you can see that anInteger and index are both 1, but the button answer false to the message isOn
testUpdateSelection fails in self assertSelectionIs: 2 because in assertSelectionIs: anInteger and index are both 2 but isOn returns false..
Som, it seems both issue are due to the same.
Let me know what else can I test.
I don't know, I was assuming what you said, but I cannot reproduce it.
I can reproduce with this way (maybe it help you): - download the latest PharoCore 1.0 and upload to 10505 - Evaluate: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfOmniBrowser'; load. (ConfigurationOfOmniBrowser project version: '1.1') load: #('Dev' 'Dev Tests' ) You should be able to debug it. I guess we have to ignore it for now.
Yes, no problem at all. We are much better :)
Lukas
Cheers
Mariano
Lukas
:)
Thanks
Mariano
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
I guess we have to ignore it for now.
Yes, no problem at all. We are much better :)
Ok, I found the reason and fixed it. It only appeared when one of the Polymorph themes was activated. I was building with the default theme and then switched to the standard theme before I saved. That's why I could not reproduce. Lukas -- Lukas Renggli http://www.lukas-renggli.ch
Thanks Doru for the feedback!!! Now I hope to create a new one during the week with all the feedback I received and using Lukas OB. Thanks Lukas for the fix!!! This is cool :) On Sun, Jan 10, 2010 at 11:37 PM, Lukas Renggli <renggli@gmail.com> wrote:
I guess we have to ignore it for now.
Yes, no problem at all. We are much better :)
Ok, I found the reason and fixed it. It only appeared when one of the Polymorph themes was activated. I was building with the default theme and then switched to the standard theme before I saved. That's why I could not reproduce.
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
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@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
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
On Sun, Jan 10, 2010 at 2:15 PM, Adrian Lienhard <adi@netstyle.ch> wrote:
Lukas is the official maintainer of the OB package for Pharo. Therefore I assume OB should be loaded from his repository... Lukas?
Wait...this is not a little decision. This is really big. Because a lot of people commits stuff to wiresong repository. How this will be merged ? where people that wants to contribute to OB should commit ?
Cheers, Adrian
PS: I don't know why testFinalizationOfEquals sometimes fails (also in PharoCore)
I created the issue: http://code.google.com/p/pharo/issues/detail?id=1771
PPS: Fixing testSymbolTableM6812 is on my todo list (it needs a change in PharoCore)
Cool. I created the issue: http://code.google.com/p/pharo/issues/detail?id=1772
On Jan 10, 2010, at 14:05 , Mariano Martinez Peck wrote:
On Sun, Jan 10, 2010 at 11:34 AM, Adrian Lienhard <adi@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Lukas is the official maintainer of the OB package for Pharo. Therefore I assume OB should be loaded from his repository... Lukas?
Wait...this is not a little decision. This is really big. Because a lot of people commits stuff to wiresong repository. How this will be merged ? where people that wants to contribute to OB should commit ?
You ask a maintainer to pull your changes from your or a separate public repository. Like about any other open-source project does. Linux. Pharo. Seaside. It does not work when everybody publishes random changes to a repository that everybody else is pulling from. Even if this looks like really open open open-source, it is the inferno. This is how you can turn in no time an excellent piece of software with hundreds of tests into battlefield of bugs, broken tests, and messed up design. Lukas - Lukas Renggli http://www.lukas-renggli.ch
Very true!! -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Lukas Renggli Sent: Sunday, January 10, 2010 8:49 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
Lukas is the official maintainer of the OB package for Pharo. Therefore I assume OB should be loaded from his repository... Lukas?
Wait...this is not a little decision. This is really big. Because a lot of people commits stuff to wiresong repository. How this will be merged ? where people that wants to contribute to OB should commit ?
You ask a maintainer to pull your changes from your or a separate public repository. Like about any other open-source project does. Linux. Pharo. Seaside. It does not work when everybody publishes random changes to a repository that everybody else is pulling from. Even if this looks like really open open open-source, it is the inferno. This is how you can turn in no time an excellent piece of software with hundreds of tests into battlefield of bugs, broken tests, and messed up design. Lukas - Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Sun, Jan 10, 2010 at 2:49 PM, Lukas Renggli <renggli@gmail.com> wrote:
Lukas is the official maintainer of the OB package for Pharo. Therefore I assume OB should be loaded from his repository... Lukas?
Wait...this is not a little decision. This is really big. Because a lot of people commits stuff to wiresong repository. How this will be merged ? where people that wants to contribute to OB should commit ?
You ask a maintainer to pull your changes from your or a separate public repository. Like about any other open-source project does. Linux. Pharo. Seaside.
It does not work when everybody publishes random changes to a repository that everybody else is pulling from. Even if this looks like really open open open-source, it is the inferno. This is how you can turn in no time an excellent piece of software with hundreds of tests into battlefield of bugs, broken tests, and messed up design.
I am agree. Now, suppose that "public repository" is wiresong. My main concern is that I don't want to "loose" those commits people do (maybe even from squeak) to that repository. So, someone should take care to integrate to Lukas OB repository the changes that are worth from wiresong repo. We will be able to handle this ?
Lukas
- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Jan 10, 2010, at 14:35 , Mariano Martinez Peck wrote:
On Sun, Jan 10, 2010 at 2:15 PM, Adrian Lienhard <adi@netstyle.ch> wrote:
Lukas is the official maintainer of the OB package for Pharo. Therefore I assume OB should be loaded from his repository... Lukas?
Wait...this is not a little decision. This is really big. Because a lot of people commits stuff to wiresong repository. How this will be merged ? where people that wants to contribute to OB should commit ?
Until somebody steps up as a maintainer to provide an official OmniBrowser for Pharo, Lukas' version is the best bet we have. As he sais, he is not an "official" maintainer, but it worked out very well so far. Since Lukas uses OB all day and knows how to fix its bugs, we get a stable browser. Therefore, I strongly suggest to continue this way, i.e., to use Lukas' OB version. I'm sure that Lukas will consider external fixes and enhancements and merge them into his line if appropriate. Cheers, Adrian
On Sun, Jan 10, 2010 at 3:22 PM, Adrian Lienhard <adi@netstyle.ch> wrote:
On Jan 10, 2010, at 14:35 , Mariano Martinez Peck wrote:
On Sun, Jan 10, 2010 at 2:15 PM, Adrian Lienhard <adi@netstyle.ch> wrote:
Lukas is the official maintainer of the OB package for Pharo. Therefore I assume OB should be loaded from his repository... Lukas?
Wait...this is not a little decision. This is really big. Because a lot of people commits stuff to wiresong repository. How this will be merged ? where people that wants to contribute to OB should commit ?
Until somebody steps up as a maintainer to provide an official OmniBrowser for Pharo, Lukas' version is the best bet we have. As he sais, he is not an "official" maintainer, but it worked out very well so far. Since Lukas uses OB all day and knows how to fix its bugs, we get a stable browser.
Therefore, I strongly suggest to continue this way, i.e., to use Lukas' OB version. I'm sure that Lukas will consider external fixes and enhancements and merge them into his line if appropriate.
Sorry Andrian, I sent my last email before this one ;) Ok...I will do a test to build a new Dev image using OB from Lukas repository. Cheers Mariano
Cheers, Adrian
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
6) There is no Web image this time. If you want to install Seaside 2.8.4 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside28'; load.
(Smalltalk at: #ConfigurationOfSeaside28) load
Tried to install seaside 2.8 with this snippet in the image you published. It gives me an error: MessageNotUnderstood: receiver of "load" is nil when executing: (Smalltalk at: #ConfigurationOfSeaside28) load The method complaining is: MetacelloMCProject(MetacelloProject)>> latestVersion specifically, this part: (self map values select: [:version | (excluded includes: version blessing) not ]) detectMax: [:version | version ] the select gives an empty list and the detectMax returns nil. the excluded temp var has: #(#development #broken #baseline) and the versions of Seaside are blessed as development. Cheers -- Miguel Cobá http://miguel.leugim.com.mx
Hi, Moose loads well and the tests work as expected. I will try to work with this image for a while, although it kills me not to see the packages :). Cheers, Doru On 9 Jan 2010, at 18:13, Mariano Martinez Peck wrote:
Hi Folks/Beta-Testers!
I have prepare a new PharoDev image. This image, has same differences with the previous ones that you should know:
1) This is the first Dev image I ever prepare. I adapt to Mac OS Damien's bash scripts to build them and I also cleanup all the Squeak stuff from those bash scripts. So, maybe there are some problems. Forgive me if this is the case. I would like you to check, not only the Image in itself but also the zip. The package.txt, changelog, the fonts, etc.
2) This image puts TrueType fonts again. We won't put StrikeFonts or DejaVu package until there is big bug with them. We know those fonts are faster, but still a bit buggy. If you fix those issues, cool!
3) This image DOES NOT include O2. I know there are a lot of people who use it (mostly in Moose), but unfortunately, this was a decision taken. O2 depends and overrides OB making this more unstable sometimes. The same as the TrueType, we will put O2 again when this can be perfectly load in a PharoCore image without anything about OB. Sorry, but we rather affect only O2 users and not all. If you want packages support, then help in O2 development.
4) In previous Dev images only tests from PharoCore were included. Now, it also includes the tests from the external packages loaded.
5) This image was build using Metacello configurations. If you want, compare the installScript.st from this image to the previous one.
6) There is no Web image this time. If you want to install Seaside 2.8.4 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside28'; load.
(Smalltalk at: #ConfigurationOfSeaside28) load
And if you want Seaside 3.0 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load.
(Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion
However, I am not sure if this is perfectly working in Pharo.
Ok .... Here is the link: https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1....
I will wait a couple of days now and I will also start to use this image for my development. If there are issues, report them. If we have big issues, this image is not release. On the other hand, if it works well, we release it. _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- www.tudorgirba.com "Problem solving should be concentrated on describing the problem in a way that is relevant for the solution."
On Sun, Jan 10, 2010 at 2:50 PM, Tudor Girba <tudor.girba@gmail.com> wrote:
Hi,
Moose loads well and the tests work as expected.
Cool. Thanks for reporting Doru.
I will try to work with this image for a while, although it kills me not to see the packages :).
Yes, I know. I miss packages too. Alexandre said he was going to work a bit with David to fix the current problems in O2. If this is done, you will then be able to evaluate: (ConfigurationOfPharo project version: '1.0-rc2.10505.2') load: 'StandardDevImageWithO2' But we need that someone fix that first. Thanks Mariano Cheers,
Doru
On 9 Jan 2010, at 18:13, Mariano Martinez Peck wrote:
Hi Folks/Beta-Testers!
I have prepare a new PharoDev image. This image, has same differences with the previous ones that you should know:
1) This is the first Dev image I ever prepare. I adapt to Mac OS Damien's bash scripts to build them and I also cleanup all the Squeak stuff from those bash scripts. So, maybe there are some problems. Forgive me if this is the case. I would like you to check, not only the Image in itself but also the zip. The package.txt, changelog, the fonts, etc.
2) This image puts TrueType fonts again. We won't put StrikeFonts or DejaVu package until there is big bug with them. We know those fonts are faster, but still a bit buggy. If you fix those issues, cool!
3) This image DOES NOT include O2. I know there are a lot of people who use it (mostly in Moose), but unfortunately, this was a decision taken. O2 depends and overrides OB making this more unstable sometimes. The same as the TrueType, we will put O2 again when this can be perfectly load in a PharoCore image without anything about OB. Sorry, but we rather affect only O2 users and not all. If you want packages support, then help in O2 development.
4) In previous Dev images only tests from PharoCore were included. Now, it also includes the tests from the external packages loaded.
5) This image was build using Metacello configurations. If you want, compare the installScript.st from this image to the previous one.
6) There is no Web image this time. If you want to install Seaside 2.8.4 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside28'; load.
(Smalltalk at: #ConfigurationOfSeaside28) load
And if you want Seaside 3.0 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load.
(Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion
However, I am not sure if this is perfectly working in Pharo.
Ok .... Here is the link: https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1....
I will wait a couple of days now and I will also start to use this image for my development. If there are issues, report them. If we have big issues, this image is not release. On the other hand, if it works well, we release it. _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- www.tudorgirba.com
"Problem solving should be concentrated on describing the problem in a way that is relevant for the solution."
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Ok, I installed it and made a some-kind "web" image (Loading Seaside28 and Pier). The seaside and pier metacello configurations needs to specify the version because there is no stable version declared. The configuration line to install seaside is: (ConfigurationOfSeaside28 project version: '2.8.4.2') load. So far, is working pretty good :) Cheers, Esteban On 2010-01-09 14:13:40 -0300, Mariano Martinez Peck <marianopeck@gmail.com> said:
Hi Folks/Beta-Testers!
I have prepare a new PharoDev image. This image, has same differences with the previous ones that you should know:
1) This is the first Dev image I ever prepare. I adapt to Mac OS Damien's bash scripts to build them and I also cleanup all the Squeak stuff from those bash scripts. So, maybe there are some problems. Forgive me if this is the case. I would like you to check, not only the Image in itself but also the zip. The package.txt, changelog, the fonts, etc.
2) This image puts TrueType fonts again. We won't put StrikeFonts or DejaVu package until there is big bug with them. We know those fonts are faster, but still a bit buggy. If you fix those issues, cool!
3) This image DOES NOT include O2. I know there are a lot of people who use it (mostly in Moose), but unfortunately, this was a decision taken. O2 depends and overrides OB making this more unstable sometimes. The same as the TrueType, we will put O2 again when this can be perfectly load in a PharoCore image without anything about OB. Sorry, but we rather affect only O2 users and not all. If you want packages support, then help in O2 development.
4) In previous Dev images only tests from PharoCore were included. Now, it also includes the tests from the external packages loaded.
5) This image was build using Metacello configurations. If you want, compare the installScript.st from this image to the previous one.
6) There is no Web image this time. If you want to install Seaside 2.8.4 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside28'; load.
(Smalltalk at: #ConfigurationOfSeaside28) load
And if you want Seaside 3.0 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load.
(Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion
However, I am not sure if this is perfectly working in Pharo.
Ok .... Here is the link: https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1....
I will wait a couple of days now and I will also start to use this image for my development. If there are issues, report them. If we have big issues, this image is not release. On the other hand, if it works well, we release it.
Hi Folks/Beta-Testers!<br><br>I have prepare a new PharoDev image. This ima= ge, has same differences with the previous ones that you should know:<br><b= r>1) This is the first Dev image I ever prepare. I adapt to Mac OS Damien&#= 39;s bash scripts to build them and I also cleanup all the Squeak stuff fro= m those bash scripts. So, maybe there are some problems. Forgive me if this= is the case. I would like you to check, not only the Image in itself but a= lso the zip. The package.txt, changelog, the fonts, etc. <br>
<br>2) This image puts TrueType fonts again. We won't put StrikeFonts o= r DejaVu package until there is big bug with them. We know those fonts are = faster, but still a bit buggy. If you fix those issues, cool!<br><br>3) Thi= s image DOES NOT include O2. I know there are a lot of people who use it (m= ostly in Moose), but unfortunately, this was a decision taken. O2 depends a= nd overrides OB making this more unstable sometimes. The same as the TrueTy= pe, we will put O2 again when this can be perfectly load in a PharoCore ima= ge without anything about OB.<br>
Sorry, but we rather affect only O2 users and not all. If you want packages= support, then help in O2 development.<br><br>4) In previous Dev images onl= y tests from PharoCore were included. Now, it also includes the tests from = the external packages loaded.<br>
<br>5) This image was build using Metacello configurations. If you want, co= mpare the installScript.st from this image to the previous one. <br><br>6) = There is no Web image this time. If you want to install Seaside 2.8.4 evalu= ate:<br>
<br>Gofer new<br>=A0=A0=A0 squeaksource: 'MetacelloRepository';<br>= =A0=A0=A0 package: 'ConfigurationOfSeaside28';<br>=A0=A0=A0 load.<b= r>=A0=A0=A0 <br>(Smalltalk at: #ConfigurationOfSeaside28) load<br><br>And i= f you want Seaside 3.0 evaluate:<br>
<br>Gofer new<br>=A0=A0=A0 squeaksource: 'MetacelloRepository';<br>= =A0=A0=A0 package: 'ConfigurationOfSeaside30';<br>=A0=A0=A0 load.<b= r>=A0=A0=A0 <br>(Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion= <br><br>However, I am not sure if this is perfectly working in Pharo. <br> <br><br><br> Ok .... Here is the link:=A0 <a href=3D"https://gforge.inria.fr/frs/downloa= d.php/25156/pharo1.0-10505-rc1dev10.01.1.zip" target=3D"_blank">https://gfo= rge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1.zip</a><br=
<br>I will wait a couple of days now and I will also start to use this imag= e for my development. If there are issues, report them. If we have big issu= es, this image is not release. On the other hand, if it works well, we rele= ase it. <br>
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Hi, It looks like Metacello-Platform and Ocompletion are dirty. Any reason for why the changes are not in the Monticello repository? Cheers, Doru On 9 Jan 2010, at 18:13, Mariano Martinez Peck wrote:
Hi Folks/Beta-Testers!
I have prepare a new PharoDev image. This image, has same differences with the previous ones that you should know:
1) This is the first Dev image I ever prepare. I adapt to Mac OS Damien's bash scripts to build them and I also cleanup all the Squeak stuff from those bash scripts. So, maybe there are some problems. Forgive me if this is the case. I would like you to check, not only the Image in itself but also the zip. The package.txt, changelog, the fonts, etc.
2) This image puts TrueType fonts again. We won't put StrikeFonts or DejaVu package until there is big bug with them. We know those fonts are faster, but still a bit buggy. If you fix those issues, cool!
3) This image DOES NOT include O2. I know there are a lot of people who use it (mostly in Moose), but unfortunately, this was a decision taken. O2 depends and overrides OB making this more unstable sometimes. The same as the TrueType, we will put O2 again when this can be perfectly load in a PharoCore image without anything about OB. Sorry, but we rather affect only O2 users and not all. If you want packages support, then help in O2 development.
4) In previous Dev images only tests from PharoCore were included. Now, it also includes the tests from the external packages loaded.
5) This image was build using Metacello configurations. If you want, compare the installScript.st from this image to the previous one.
6) There is no Web image this time. If you want to install Seaside 2.8.4 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside28'; load.
(Smalltalk at: #ConfigurationOfSeaside28) load
And if you want Seaside 3.0 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load.
(Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion
However, I am not sure if this is perfectly working in Pharo.
Ok .... Here is the link: https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1....
I will wait a couple of days now and I will also start to use this image for my development. If there are issues, report them. If we have big issues, this image is not release. On the other hand, if it works well, we release it. _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- www.tudorgirba.com "Every thing has its own flow."
On Sun, Jan 10, 2010 at 5:58 PM, Tudor Girba <tudor.girba@gmail.com> wrote:
Hi,
It looks like Metacello-Platform and Ocompletion are dirty. Any reason for why the changes are not in the Monticello repository?
Thanks Doru for the report. For Metacello-Platform, it is correct it is dirty. I am having some problems with the progress bar when running Pharo from comman d line and build the images. We are trying to fix this with Dale but for the moment (as I needed to build Pharo image) I disable the posgress bar in that way. Regarding OCompletion, I have no idea at all. I cc Romain to see if he can help us. Cheers Mariano
Cheers, Doru
On 9 Jan 2010, at 18:13, Mariano Martinez Peck wrote:
Hi Folks/Beta-Testers!
I have prepare a new PharoDev image. This image, has same differences with the previous ones that you should know:
1) This is the first Dev image I ever prepare. I adapt to Mac OS Damien's bash scripts to build them and I also cleanup all the Squeak stuff from those bash scripts. So, maybe there are some problems. Forgive me if this is the case. I would like you to check, not only the Image in itself but also the zip. The package.txt, changelog, the fonts, etc.
2) This image puts TrueType fonts again. We won't put StrikeFonts or DejaVu package until there is big bug with them. We know those fonts are faster, but still a bit buggy. If you fix those issues, cool!
3) This image DOES NOT include O2. I know there are a lot of people who use it (mostly in Moose), but unfortunately, this was a decision taken. O2 depends and overrides OB making this more unstable sometimes. The same as the TrueType, we will put O2 again when this can be perfectly load in a PharoCore image without anything about OB. Sorry, but we rather affect only O2 users and not all. If you want packages support, then help in O2 development.
4) In previous Dev images only tests from PharoCore were included. Now, it also includes the tests from the external packages loaded.
5) This image was build using Metacello configurations. If you want, compare the installScript.st from this image to the previous one.
6) There is no Web image this time. If you want to install Seaside 2.8.4 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside28'; load.
(Smalltalk at: #ConfigurationOfSeaside28) load
And if you want Seaside 3.0 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load.
(Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion
However, I am not sure if this is perfectly working in Pharo.
Ok .... Here is the link: https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1....
I will wait a couple of days now and I will also start to use this image for my development. If there are issues, report them. If we have big issues, this image is not release. On the other hand, if it works well, we release it. _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- www.tudorgirba.com
"Every thing has its own flow."
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Mariano Martinez Peck wrote:
Hi Folks/Beta-Testers!
I have prepare a new PharoDev image. This image, has same differences with the previous ones that you should know:
1) This is the first Dev image I ever prepare. I adapt to Mac OS Damien's bash scripts to build them and I also cleanup all the Squeak stuff from those bash scripts. So, maybe there are some problems. Forgive me if this is the case. I would like you to check, not only the Image in itself but also the zip. The package.txt, changelog, the fonts, etc.
2) This image puts TrueType fonts again. We won't put StrikeFonts or DejaVu package until there is big bug with them. We know those fonts are faster, but still a bit buggy. If you fix those issues, cool!
3) This image DOES NOT include O2. I know there are a lot of people who use it (mostly in Moose), but unfortunately, this was a decision taken. O2 depends and overrides OB making this more unstable sometimes. The same as the TrueType, we will put O2 again when this can be perfectly load in a PharoCore image without anything about OB. Sorry, but we rather affect only O2 users and not all. If you want packages support, then help in O2 development.
4) In previous Dev images only tests from PharoCore were included. Now, it also includes the tests from the external packages loaded.
5) This image was build using Metacello configurations. If you want, compare the installScript.st from this image to the previous one.
6) There is no Web image this time. If you want to install Seaside 2.8.4 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside28'; load.
(Smalltalk at: #ConfigurationOfSeaside28) load
And if you want Seaside 3.0 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load.
(Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion
However, I am not sure if this is perfectly working in Pharo.
Ok .... Here is the link: https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1....
I will wait a couple of days now and I will also start to use this image for my development. If there are issues, report them. If we have big issues, this image is not release. On the other hand, if it works well, we release it.
Hi Mariano, great job. I was able to install Seaside 3 as per your instructions. Xubuntu 9.10. OB, refactoring, code critics all appear to be working faultlessly. I am impressed. The only concern is that it took some hours to download and install Seaside (albeit on a slow spare PC). And with occassional network glitches, I had to restart a method a few times from a debugger. So this would not be a practical proposition for a new Pharoer. Also the choice of fonts and theme makes for a better aesthetic result than the previous web image. For me, this is a much better image than that version. Thanks for all the work you have put into this, ...Stan -- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
On Sun, Jan 10, 2010 at 9:02 PM, Stan Shepherd <stan.shepherd414@gmail.com>wrote:
Mariano Martinez Peck wrote:
Hi Folks/Beta-Testers!
I have prepare a new PharoDev image. This image, has same differences
with
the previous ones that you should know:
1) This is the first Dev image I ever prepare. I adapt to Mac OS Damien's bash scripts to build them and I also cleanup all the Squeak stuff from those bash scripts. So, maybe there are some problems. Forgive me if this is the case. I would like you to check, not only the Image in itself but also the zip. The package.txt, changelog, the fonts, etc.
2) This image puts TrueType fonts again. We won't put StrikeFonts or DejaVu package until there is big bug with them. We know those fonts are faster, but still a bit buggy. If you fix those issues, cool!
3) This image DOES NOT include O2. I know there are a lot of people who use it (mostly in Moose), but unfortunately, this was a decision taken. O2 depends and overrides OB making this more unstable sometimes. The same as the TrueType, we will put O2 again when this can be perfectly load in a PharoCore image without anything about OB. Sorry, but we rather affect only O2 users and not all. If you want packages support, then help in O2 development.
4) In previous Dev images only tests from PharoCore were included. Now, it also includes the tests from the external packages loaded.
5) This image was build using Metacello configurations. If you want, compare the installScript.st from this image to the previous one.
6) There is no Web image this time. If you want to install Seaside 2.8.4 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside28'; load.
(Smalltalk at: #ConfigurationOfSeaside28) load
And if you want Seaside 3.0 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load.
(Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion
However, I am not sure if this is perfectly working in Pharo.
Ok .... Here is the link:
https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1....
I will wait a couple of days now and I will also start to use this image for my development. If there are issues, report them. If we have big issues, this image is not release. On the other hand, if it works well, we
release
it.
Hi Mariano, great job.
I was able to install Seaside 3 as per your instructions. Xubuntu 9.10.
Cool. Thanks for reporting. I will put that code in the next ANN email.
OB, refactoring, code critics all appear to be working faultlessly. I am impressed.
Excellent.
The only concern is that it took some hours
hours ? seriously ?
to download and install Seaside (albeit on a slow spare PC). And with occassional network glitches, I had to restart a method a few times from a debugger. So this would not be a practical proposition for a new Pharoer.
Yes, maybe you are right with this. Anyway, a new Pharoer would use Seaside one click. That's what I suggested.
Also the choice of fonts and theme makes for a better aesthetic result than
Thanks. But the choice was not only mine. We try to decide between all of us. That's why eveytime I have a question, I send an email to the mailing list and then we do what the mayority of the people says :)
the previous web image. For me, this is a much better image than that version.
Thanks for all the work you have put into this, ...Stan
You are welcome. Thanks for the report.
-- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Hi, I can now report that I worked 8 hours using the new dev image and I encountered no problems at all. Cheers, Doru On 10 Jan 2010, at 21:11, Mariano Martinez Peck wrote:
On Sun, Jan 10, 2010 at 9:02 PM, Stan Shepherd <stan.shepherd414@gmail.com
wrote:
Mariano Martinez Peck wrote:
Hi Folks/Beta-Testers!
I have prepare a new PharoDev image. This image, has same
differences with
the previous ones that you should know:
1) This is the first Dev image I ever prepare. I adapt to Mac OS Damien's bash scripts to build them and I also cleanup all the Squeak stuff from those bash scripts. So, maybe there are some problems. Forgive me if this is the case. I would like you to check, not only the Image in itself but also the zip. The package.txt, changelog, the fonts, etc.
2) This image puts TrueType fonts again. We won't put StrikeFonts or DejaVu package until there is big bug with them. We know those fonts are faster, but still a bit buggy. If you fix those issues, cool!
3) This image DOES NOT include O2. I know there are a lot of people who use it (mostly in Moose), but unfortunately, this was a decision taken. O2 depends and overrides OB making this more unstable sometimes. The same as the TrueType, we will put O2 again when this can be perfectly load in a PharoCore image without anything about OB. Sorry, but we rather affect only O2 users and not all. If you want packages support, then help in O2 development.
4) In previous Dev images only tests from PharoCore were included. Now, it also includes the tests from the external packages loaded.
5) This image was build using Metacello configurations. If you want, compare the installScript.st from this image to the previous one.
6) There is no Web image this time. If you want to install Seaside 2.8.4 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside28'; load.
(Smalltalk at: #ConfigurationOfSeaside28) load
And if you want Seaside 3.0 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load.
(Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion
However, I am not sure if this is perfectly working in Pharo.
Ok .... Here is the link: https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1....
I will wait a couple of days now and I will also start to use this image for my development. If there are issues, report them. If we have big issues, this image is not release. On the other hand, if it works well, we release it.
Hi Mariano, great job.
I was able to install Seaside 3 as per your instructions. Xubuntu 9.10.
Cool. Thanks for reporting. I will put that code in the next ANN email.
OB, refactoring, code critics all appear to be working faultlessly. I am impressed.
Excellent.
The only concern is that it took some hours
hours ? seriously ?
to download and install Seaside (albeit on a slow spare PC). And with occassional network glitches, I had to restart a method a few times from a debugger. So this would not be a practical proposition for a new Pharoer.
Yes, maybe you are right with this. Anyway, a new Pharoer would use Seaside one click. That's what I suggested.
Also the choice of fonts and theme makes for a better aesthetic result than
Thanks. But the choice was not only mine. We try to decide between all of us. That's why eveytime I have a question, I send an email to the mailing list and then we do what the mayority of the people says :)
the previous web image. For me, this is a much better image than that version.
Thanks for all the work you have put into this, ...Stan
You are welcome. Thanks for the report.
-- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- www.tudorgirba.com "Be rather willing to give than demanding to get."
Yeah, it should not have an effect on production. It is just the test that checked directly for the color to see if a button is highlighted and thus selected. The code is not used when running OB. I changed it to use some other magic morphic test that works with all themes. Lukas 2010/1/10 Tudor Girba <tudor.girba@gmail.com>:
Hi,
I can now report that I worked 8 hours using the new dev image and I encountered no problems at all.
Cheers, Doru
On 10 Jan 2010, at 21:11, Mariano Martinez Peck wrote:
On Sun, Jan 10, 2010 at 9:02 PM, Stan Shepherd <stan.shepherd414@gmail.com
wrote:
Mariano Martinez Peck wrote:
Hi Folks/Beta-Testers!
I have prepare a new PharoDev image. This image, has same
differences with
the previous ones that you should know:
1) This is the first Dev image I ever prepare. I adapt to Mac OS Damien's bash scripts to build them and I also cleanup all the Squeak stuff from those bash scripts. So, maybe there are some problems. Forgive me if this is the case. I would like you to check, not only the Image in itself but also the zip. The package.txt, changelog, the fonts, etc.
2) This image puts TrueType fonts again. We won't put StrikeFonts or DejaVu package until there is big bug with them. We know those fonts are faster, but still a bit buggy. If you fix those issues, cool!
3) This image DOES NOT include O2. I know there are a lot of people who use it (mostly in Moose), but unfortunately, this was a decision taken. O2 depends and overrides OB making this more unstable sometimes. The same as the TrueType, we will put O2 again when this can be perfectly load in a PharoCore image without anything about OB. Sorry, but we rather affect only O2 users and not all. If you want packages support, then help in O2 development.
4) In previous Dev images only tests from PharoCore were included. Now, it also includes the tests from the external packages loaded.
5) This image was build using Metacello configurations. If you want, compare the installScript.st from this image to the previous one.
6) There is no Web image this time. If you want to install Seaside 2.8.4 evaluate:
Gofer new   squeaksource: 'MetacelloRepository';   package: 'ConfigurationOfSeaside28';   load.
(Smalltalk at: #ConfigurationOfSeaside28) load
And if you want Seaside 3.0 evaluate:
Gofer new   squeaksource: 'MetacelloRepository';   package: 'ConfigurationOfSeaside30';   load.
(Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion
However, I am not sure if this is perfectly working in Pharo.
Ok .... Here is the link: https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1....
I will wait a couple of days now and I will also start to use this image for my development. If there are issues, report them. If we have big issues, this image is not release. On the other hand, if it works well, we release it.
Hi Mariano, great job.
I was able to install Seaside 3 as per your instructions. Â Xubuntu 9.10.
Cool. Thanks for reporting. I will put that code in the next ANN email.
OB, refactoring, code critics all appear to be working faultlessly. I am impressed.
Excellent.
The only concern is that it took some hours
hours ? seriously ?
to download and install Seaside (albeit on a slow spare PC). And with occassional network glitches, I had to restart a method a few times from a debugger. So this would not be a practical proposition for a new Pharoer.
Yes, maybe you are right with this. Anyway, a new Pharoer would use Seaside one click. That's what I suggested.
Also the choice of fonts and theme makes for a better aesthetic result than
Thanks. But the choice was not only mine. We try to decide between all of us. That's why eveytime I have a question, I send an email to the mailing list and then we do what the mayority of the people says :)
the previous web image. For me, this is a much better image than that version.
Thanks for all the work you have put into this, Â Â ...Stan
You are welcome. Thanks for the report.
-- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- www.tudorgirba.com
"Be rather willing to give than demanding to get."
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch
Mariano Martinez Peck wrote:
On Sun, Jan 10, 2010 at 9:02 PM, Stan Shepherd <stan.shepherd414@gmail.com>wrote:
The only concern is that it took some hours
hours ? seriously ?
to download and install Seaside (albeit on a slow spare PC). And with occassional network glitches, I had to restart a method a few times from a debugger.
Yes, it was 3 hr 29m on the old machine, but I don't know what percent it was halted due to network glitches. It would be really cool if it made say 3 retries when its HTTP gets failed. I ran overnight on main machine (Ubuntu 9.04, 3 GHz dual core 1GB ram, nominal 7Gb internet but other downloads running) with message tally - 71 minutes. ...Stan -- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
It would be cool if it didn't take 3+ hours to load. 2.8 is much more reasonable. Is 3 that much bigger, or is something wrong with the configuration? -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Stan Shepherd Sent: Monday, January 11, 2010 4:38 AM To: pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 Mariano Martinez Peck wrote:
On Sun, Jan 10, 2010 at 9:02 PM, Stan Shepherd <stan.shepherd414@gmail.com>wrote:
The only concern is that it took some hours
hours ? seriously ?
to download and install Seaside (albeit on a slow spare PC). And with occassional network glitches, I had to restart a method a few times from a debugger.
Yes, it was 3 hr 29m on the old machine, but I don't know what percent it was halted due to network glitches. It would be really cool if it made say 3 retries when its HTTP gets failed. I ran overnight on main machine (Ubuntu 9.04, 3 GHz dual core 1GB ram, nominal 7Gb internet but other downloads running) with message tally - 71 minutes. ...Stan -- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com. _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Mon, Jan 11, 2010 at 12:31 PM, Schwab,Wilhelm K <bschwab@anest.ufl.edu>wrote:
It would be cool if it didn't take 3+ hours to load. 2.8 is much more reasonable. Is 3 that much bigger, or is something wrong with the configuration?
Yes, it cannot take 3 hours. In my case, it takes no more than 15 minutes. Stan: the old machine was with Windows? do you have any antivirus working like NOD32 or something like that ?
-----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto: pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Stan Shepherd Sent: Monday, January 11, 2010 4:38 AM To: pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
Mariano Martinez Peck wrote:
On Sun, Jan 10, 2010 at 9:02 PM, Stan Shepherd <stan.shepherd414@gmail.com>wrote:
The only concern is that it took some hours
hours ? seriously ?
to download and install Seaside (albeit on a slow spare PC). And with occassional network glitches, I had to restart a method a few times from a debugger.
Yes, it was 3 hr 29m on the old machine, but I don't know what percent it was halted due to network glitches. It would be really cool if it made say 3 retries when its HTTP gets failed.
I ran overnight on main machine (Ubuntu 9.04, 3 GHz dual core 1GB ram, nominal 7Gb internet but other downloads running) with message tally - 71 minutes.
...Stan
-- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Mariano Martinez Peck wrote:
On Mon, Jan 11, 2010 at 12:31 PM, Schwab,Wilhelm K <bschwab@anest.ufl.edu>wrote:
It would be cool if it didn't take 3+ hours to load. 2.8 is much more reasonable. Is 3 that much bigger, or is something wrong with the configuration?
Yes, it cannot take 3 hours. In my case, it takes no more than 15 minutes. Stan: the old machine was with Windows? do you have any antivirus working like NOD32 or something like that ?
-----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto: pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Stan Shepherd Sent: Monday, January 11, 2010 4:38 AM To: pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
Mariano Martinez Peck wrote:
On Sun, Jan 10, 2010 at 9:02 PM, Stan Shepherd <stan.shepherd414@gmail.com>wrote:
The only concern is that it took some hours
hours ? seriously ?
to download and install Seaside (albeit on a slow spare PC). And with occassional network glitches, I had to restart a method a few times from a debugger.
Yes, it was 3 hr 29m on the old machine, but I don't know what percent it was halted due to network glitches. It would be really cool if it made say 3 retries when its HTTP gets failed.
I ran overnight on main machine (Ubuntu 9.04, 3 GHz dual core 1GB ram, nominal 7Gb internet but other downloads running) with message tally - 71 minutes.
...Stan
-- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Hi, don't get too hung up on the 3 hr+, it's a really old machine running Xubuntu I use to test my stuff runs lean. Better to look at the 'normal' machine's time of 71 minutes, vs 15. Ubuntu, with no nasties running. I previously reported that I find System update slow. Mariano, do you run in a folder with a package cache present? I run in a clean install, so it has to download everything. The process I use: create new folder seaside3buildTest2 paste and unzip a Seaside-3.0a5.app.zip one click http://n2.nabble.com/file/n4285691/loadprocess.txt loadprocess.txt , to have a full environment paste and unzip pharo1.0-10505-rc1dev10.01.1.zip copy pharo1.0-10505-rc1dev10.01.1.image .changes into Resources folder delete Seaside.image, .changes edit Seaside.sh to be pharo1.0-10505-rc1dev10.01.1.sh, opening pharo1.0-10505-rc1dev10.01.1.image pharo1.0-10505-rc1dev10.01.1.sh open with sh I find it most convenient to start with a one click image like that. MessageTally attached. Also found my first bug: MessageTally tallySends: [Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfRefactoringBrowser'; load]. Throws code simulation error in Project class>>spawnNewProcess UIProcess := [ [World doOneCycle. Processor yield. false] whileFalse: []. ] newProcess priority: Processor userSchedulingPriority. UIProcess resume ...Stan -- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
On Mon, Jan 11, 2010 at 3:41 PM, Stan Shepherd <stan.shepherd414@gmail.com>wrote:
Mariano Martinez Peck wrote:
On Mon, Jan 11, 2010 at 12:31 PM, Schwab,Wilhelm K <bschwab@anest.ufl.edu>wrote:
It would be cool if it didn't take 3+ hours to load. 2.8 is much more reasonable. Is 3 that much bigger, or is something wrong with the configuration?
Yes, it cannot take 3 hours. In my case, it takes no more than 15
minutes.
Stan: the old machine was with Windows? do you have any antivirus working like NOD32 or something like that ?
-----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto: pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Stan Shepherd Sent: Monday, January 11, 2010 4:38 AM To: pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
Mariano Martinez Peck wrote:
On Sun, Jan 10, 2010 at 9:02 PM, Stan Shepherd <stan.shepherd414@gmail.com>wrote:
The only concern is that it took some hours
hours ? seriously ?
to download and install Seaside (albeit on a slow spare PC). And with occassional network glitches, I had to restart a method a few times from a debugger.
Yes, it was 3 hr 29m on the old machine, but I don't know what percent
it
was halted due to network glitches. It would be really cool if it made say 3 retries when its HTTP gets failed.
I ran overnight on main machine (Ubuntu 9.04, 3 GHz dual core 1GB ram, nominal 7Gb internet but other downloads running) with message tally - 71 minutes.
...Stan
-- View this message in context:
http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p...
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Hi, don't get too hung up on the 3 hr+, it's a really old machine running Xubuntu I use to test my stuff runs lean. Better to look at the 'normal' machine's time of 71 minutes, vs 15. Ubuntu, with no nasties running.
I previously reported that I find System update slow.
Mariano, do you run in a folder with a package cache present? I run in a clean install, so it has to download everything.
The process I use: create new folder seaside3buildTest2 paste and unzip a Seaside-3.0a5.app.zip one click http://n2.nabble.com/file/n4285691/loadprocess.txt loadprocess.txt , to have a full environment paste and unzip pharo1.0-10505-rc1dev10.01.1.zip copy pharo1.0-10505-rc1dev10.01.1.image .changes into Resources folder delete Seaside.image, .changes edit Seaside.sh to be pharo1.0-10505-rc1dev10.01.1.sh, opening pharo1.0-10505-rc1dev10.01.1.image pharo1.0-10505-rc1dev10.01.1.sh open with sh
I find it most convenient to start with a one click image like that.
MessageTally attached.
Are you sure ? ;)
Also found my first bug:
MessageTally tallySends: [Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfRefactoringBrowser'; load].
Throws code simulation error
in Project class>>spawnNewProcess
UIProcess := [ [World doOneCycle. Processor yield. false] whileFalse: []. ] newProcess priority: Processor userSchedulingPriority. UIProcess resume
...Stan
-- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Mon, Jan 11, 2010 at 3:41 PM, Stan Shepherd <stan.shepherd414@gmail.com>wrote:
Mariano Martinez Peck wrote:
On Mon, Jan 11, 2010 at 12:31 PM, Schwab,Wilhelm K <bschwab@anest.ufl.edu>wrote:
It would be cool if it didn't take 3+ hours to load. 2.8 is much more reasonable. Is 3 that much bigger, or is something wrong with the configuration?
Stan: Can you test this again with the RC2 image? It will use a new Metacello version that uses a feature of Gofer that does some cache..and etc.. So, it should be much better. Can you test it and let me know? Thanks Mariano
Yes, it cannot take 3 hours. In my case, it takes no more than 15 minutes. Stan: the old machine was with Windows? do you have any antivirus working like NOD32 or something like that ?
-----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto: pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Stan Shepherd Sent: Monday, January 11, 2010 4:38 AM To: pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
Mariano Martinez Peck wrote:
On Sun, Jan 10, 2010 at 9:02 PM, Stan Shepherd <stan.shepherd414@gmail.com>wrote:
The only concern is that it took some hours
hours ? seriously ?
to download and install Seaside (albeit on a slow spare PC). And with occassional network glitches, I had to restart a method a few times from a debugger.
Yes, it was 3 hr 29m on the old machine, but I don't know what percent
it
was halted due to network glitches. It would be really cool if it made say 3 retries when its HTTP gets failed.
I ran overnight on main machine (Ubuntu 9.04, 3 GHz dual core 1GB ram, nominal 7Gb internet but other downloads running) with message tally - 71 minutes.
...Stan
-- View this message in context:
http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p...
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Hi, don't get too hung up on the 3 hr+, it's a really old machine running Xubuntu I use to test my stuff runs lean. Better to look at the 'normal' machine's time of 71 minutes, vs 15. Ubuntu, with no nasties running.
I previously reported that I find System update slow.
Mariano, do you run in a folder with a package cache present? I run in a clean install, so it has to download everything.
The process I use: create new folder seaside3buildTest2 paste and unzip a Seaside-3.0a5.app.zip one click http://n2.nabble.com/file/n4285691/loadprocess.txt loadprocess.txt , to have a full environment paste and unzip pharo1.0-10505-rc1dev10.01.1.zip copy pharo1.0-10505-rc1dev10.01.1.image .changes into Resources folder delete Seaside.image, .changes edit Seaside.sh to be pharo1.0-10505-rc1dev10.01.1.sh, opening pharo1.0-10505-rc1dev10.01.1.image pharo1.0-10505-rc1dev10.01.1.sh open with sh
I find it most convenient to start with a one click image like that.
MessageTally attached.
Also found my first bug:
MessageTally tallySends: [Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfRefactoringBrowser'; load].
Throws code simulation error
in Project class>>spawnNewProcess
UIProcess := [ [World doOneCycle. Processor yield. false] whileFalse: []. ] newProcess priority: Processor userSchedulingPriority. UIProcess resume
...Stan
-- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Hi Mariano, ConfigurationOfSeaside30-DaleHenrichs.123 is empty. Using 122, it loaded in 43 minutes, so a bit quicker. ...Stan -- View this message in context: http://n4.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp1295967p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Thanks for the testing Stan. On Wed, Jan 27, 2010 at 7:16 PM, Stan Shepherd <stan.shepherd414@gmail.com>wrote:
Hi Mariano,
ConfigurationOfSeaside30-DaleHenrichs.123 is empty. Using 122, it loaded in 43 minutes, so a bit quicker. ...Stan
-- View this message in context: http://n4.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp1295967p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Stan, I found Seaside 2.8 to install in a reasonable time. Did you time 3.0? I'm surprised it worked, and it is certainly not going to go over well if my experience is any indication of how long it should take. Bill -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Stan Shepherd Sent: Sunday, January 10, 2010 3:03 PM To: pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 Mariano Martinez Peck wrote:
Hi Folks/Beta-Testers!
I have prepare a new PharoDev image. This image, has same differences with the previous ones that you should know:
1) This is the first Dev image I ever prepare. I adapt to Mac OS Damien's bash scripts to build them and I also cleanup all the Squeak stuff from those bash scripts. So, maybe there are some problems. Forgive me if this is the case. I would like you to check, not only the Image in itself but also the zip. The package.txt, changelog, the fonts, etc.
2) This image puts TrueType fonts again. We won't put StrikeFonts or DejaVu package until there is big bug with them. We know those fonts are faster, but still a bit buggy. If you fix those issues, cool!
3) This image DOES NOT include O2. I know there are a lot of people who use it (mostly in Moose), but unfortunately, this was a decision taken. O2 depends and overrides OB making this more unstable sometimes. The same as the TrueType, we will put O2 again when this can be perfectly load in a PharoCore image without anything about OB. Sorry, but we rather affect only O2 users and not all. If you want packages support, then help in O2 development.
4) In previous Dev images only tests from PharoCore were included. Now, it also includes the tests from the external packages loaded.
5) This image was build using Metacello configurations. If you want, compare the installScript.st from this image to the previous one.
6) There is no Web image this time. If you want to install Seaside 2.8.4 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside28'; load.
(Smalltalk at: #ConfigurationOfSeaside28) load
And if you want Seaside 3.0 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load.
(Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion
However, I am not sure if this is perfectly working in Pharo.
Ok .... Here is the link: https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10 .01.1.zip
I will wait a couple of days now and I will also start to use this image for my development. If there are issues, report them. If we have big issues, this image is not release. On the other hand, if it works well, we release it.
Hi Mariano, great job. I was able to install Seaside 3 as per your instructions. Xubuntu 9.10. OB, refactoring, code critics all appear to be working faultlessly. I am impressed. The only concern is that it took some hours to download and install Seaside (albeit on a slow spare PC). And with occassional network glitches, I had to restart a method a few times from a debugger. So this would not be a practical proposition for a new Pharoer. Also the choice of fonts and theme makes for a better aesthetic result than the previous web image. For me, this is a much better image than that version. Thanks for all the work you have put into this, ...Stan -- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com. _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Mariano Martinez Peck wrote:
Hi Folks/Beta-Testers!
I have prepare a new PharoDev image. This image, has same differences with the previous ones that you should know:
1) This is the first Dev image I ever prepare. I adapt to Mac OS Damien's bash scripts to build them and I also cleanup all the Squeak stuff from those bash scripts. So, maybe there are some problems. Forgive me if this is the case. I would like you to check, not only the Image in itself but also the zip. The package.txt, changelog, the fonts, etc.
2) This image puts TrueType fonts again. We won't put StrikeFonts or DejaVu package until there is big bug with them. We know those fonts are faster, but still a bit buggy. If you fix those issues, cool!
3) This image DOES NOT include O2. I know there are a lot of people who use it (mostly in Moose), but unfortunately, this was a decision taken. O2 depends and overrides OB making this more unstable sometimes. The same as the TrueType, we will put O2 again when this can be perfectly load in a PharoCore image without anything about OB. Sorry, but we rather affect only O2 users and not all. If you want packages support, then help in O2 development.
4) In previous Dev images only tests from PharoCore were included. Now, it also includes the tests from the external packages loaded.
5) This image was build using Metacello configurations. If you want, compare the installScript.st from this image to the previous one.
6) There is no Web image this time. If you want to install Seaside 2.8.4 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside28'; load.
(Smalltalk at: #ConfigurationOfSeaside28) load
And if you want Seaside 3.0 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load.
(Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion
However, I am not sure if this is perfectly working in Pharo.
Ok .... Here is the link: https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1....
I will wait a couple of days now and I will also start to use this image for my development. If there are issues, report them. If we have big issues, this image is not release. On the other hand, if it works well, we release it.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Was there a reason you opted not to include RB spelling? I don't know how may people use it- I find it really handy, so my vote would be for inclusion. ...Stan -- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Was there a reason you opted not to include RB spelling? I don't know how may people use it- I find it really handy, so my vote would be for inclusion. ...Stan
Good question. I really appreacite the feedback. Thanks. No, actually the only reason is because I didn realize it :) because, I don't explicity load RB, it is loaded because as a dependency of OB-refactory, but it only needs the Refactoring-Core, not spelling, and that's why it wasen't loaded. However, it is really easy to change if we want. I just put the complete RB as requiered in in Pharo and that's all. In summary, no problem, if we want, I add it. I don't think even it is much problem to load it. And in the previous images it is was loaded, so, I like to idea to load it. What other things? cheers mariano
-- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Hi Stan, can you check if there is another package missing from the previous dev image ? Thanks! Mariano On Mon, Jan 11, 2010 at 9:45 PM, Stan Shepherd <stan.shepherd414@gmail.com>wrote:
Mariano Martinez Peck wrote:
Hi Folks/Beta-Testers!
I have prepare a new PharoDev image. This image, has same differences
with
the previous ones that you should know:
1) This is the first Dev image I ever prepare. I adapt to Mac OS Damien's bash scripts to build them and I also cleanup all the Squeak stuff from those bash scripts. So, maybe there are some problems. Forgive me if this is the case. I would like you to check, not only the Image in itself but also the zip. The package.txt, changelog, the fonts, etc.
2) This image puts TrueType fonts again. We won't put StrikeFonts or DejaVu package until there is big bug with them. We know those fonts are faster, but still a bit buggy. If you fix those issues, cool!
3) This image DOES NOT include O2. I know there are a lot of people who use it (mostly in Moose), but unfortunately, this was a decision taken. O2 depends and overrides OB making this more unstable sometimes. The same as the TrueType, we will put O2 again when this can be perfectly load in a PharoCore image without anything about OB. Sorry, but we rather affect only O2 users and not all. If you want packages support, then help in O2 development.
4) In previous Dev images only tests from PharoCore were included. Now, it also includes the tests from the external packages loaded.
5) This image was build using Metacello configurations. If you want, compare the installScript.st from this image to the previous one.
6) There is no Web image this time. If you want to install Seaside 2.8.4 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside28'; load.
(Smalltalk at: #ConfigurationOfSeaside28) load
And if you want Seaside 3.0 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load.
(Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion
However, I am not sure if this is perfectly working in Pharo.
Ok .... Here is the link:
https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1....
I will wait a couple of days now and I will also start to use this image for my development. If there are issues, report them. If we have big issues, this image is not release. On the other hand, if it works well, we
release
it.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Was there a reason you opted not to include RB spelling? I don't know how may people use it- I find it really handy, so my vote would be for inclusion. ...Stan
-- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Mariano Martinez Peck wrote:
Hi Stan, can you check if there is another package missing from the previous dev image ?
Thanks!
Mariano
Hi Mariano, attached is the list of differences from 10502 to 10505. All missing packages seem to relate to O2, except for Spelling. Is this what you meant? Cheers, ...Stan http://n2.nabble.com/file/n4288408/packagesDiff10502to10505.ods packagesDiff10502to10505.ods -- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
On Mon, Jan 11, 2010 at 10:56 PM, Stan Shepherd <stan.shepherd414@gmail.com>wrote:
Mariano Martinez Peck wrote:
Hi Stan, can you check if there is another package missing from the previous dev image ?
Thanks!
Mariano
Hi Mariano, attached
did you know about the Gmail feature (it is in Lab) that detects certain key words like "attached" or "attach" and when you are going to send an email, a popup brigns saying "Are you sure you don't have to attach something? " ;)
is the list of differences from 10502 to 10505. All missing packages seem to relate to O2, except for Spelling.
Is this what you meant?
But, yes, exactly that. Don't care that there is a changelog.txt for each dev images comparing exactly this, but I had a problem for the moment with that. Thanks a lot.
Cheers, ...Stan
http://n2.nabble.com/file/n4288408/packagesDiff10502to10505.ods packagesDiff10502to10505.ods
-- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Mariano Martinez Peck wrote:
On Mon, Jan 11, 2010 at 10:56 PM, Stan Shepherd <stan.shepherd414@gmail.com>wrote:
Mariano Martinez Peck wrote:
Hi Stan, can you check if there is another package missing from the previous dev image ?
Thanks!
Mariano
Hi Mariano, attached
did you know about the Gmail feature (it is in Lab) that detects certain key words like "attached" or "attach" and when you are going to send an email, a popup brigns saying "Are you sure you don't have to attach something? "
;)
is the list of differences from 10502 to 10505. All missing packages seem to relate to O2, except for Spelling.
Is this what you meant?
But, yes, exactly that. Don't care that there is a changelog.txt for each dev images comparing exactly this, but I had a problem for the moment with that.
Thanks a lot.
Cheers, ...Stan
http://n2.nabble.com/file/n4288408/packagesDiff10502to10505.ods packagesDiff10502to10505.ods
Hi, I only browse the forum through Nabble, and it's attaching fine. http://n2.nabble.com/file/n4288408/packagesDiff10502to10505.ods see: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-td4278312i... sorry if it's not coming through on email. Previous file is http://n2.nabble.com/file/n4285691/loadprocess.txt Do those links work? ...Stan -- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
On Mon, Jan 11, 2010 at 11:26 PM, Stan Shepherd <stan.shepherd414@gmail.com>wrote:
Mariano Martinez Peck wrote:
On Mon, Jan 11, 2010 at 10:56 PM, Stan Shepherd <stan.shepherd414@gmail.com>wrote:
Mariano Martinez Peck wrote:
Hi Stan, can you check if there is another package missing from the previous dev image ?
Thanks!
Mariano
Hi Mariano, attached
did you know about the Gmail feature (it is in Lab) that detects certain key words like "attached" or "attach" and when you are going to send an
email,
a popup brigns saying "Are you sure you don't have to attach something? "
;)
is the list of differences from 10502 to 10505. All missing packages seem to relate to O2, except for Spelling.
Is this what you meant?
But, yes, exactly that. Don't care that there is a changelog.txt for each dev images comparing exactly this, but I had a problem for the moment with that.
Thanks a lot.
Cheers, ...Stan
http://n2.nabble.com/file/n4288408/packagesDiff10502to10505.ods packagesDiff10502to10505.ods
Hi, I only browse the forum through Nabble, and it's attaching fine. http://n2.nabble.com/file/n4288408/packagesDiff10502to10505.ods
see:
http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-td4278312i...
sorry if it's not coming through on email.
Previous file is http://n2.nabble.com/file/n4285691/loadprocess.txt
Do those links work?
Sorry, I don't know why, I didn't receive the attach in the email. But a anyway, the links work perfect (I always forget to attach file) I have no idea what your problem is. Now I am confused: you have two things: you sent me the difference from the packages and also the stacktrace from messagetally. This piece of thread is from changes, but your links are for the MessageTally. Anyway, this thread is already too big. I would send a separate and clear mail to the mailing list to see if someone can help you. Thanks about the packages info and the testing. Cheers Mariano ...Stan
-- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Was there a reason you opted not to include RB spelling? I don't know how may people use it- I find it really handy, so my vote would be for inclusion.
if I remember it depends on some mac library
No, it does not depend on the mac primitive. I've implemented an alternative that works on all platforms, less performant and of a lesser quality, but it should basically work. Lukas -- Lukas Renggli http://www.lukas-renggli.ch
cool! You are really crazy :) On Jan 11, 2010, at 10:56 PM, Lukas Renggli wrote:
Was there a reason you opted not to include RB spelling? I don't know how may people use it- I find it really handy, so my vote would be for inclusion.
if I remember it depends on some mac library
No, it does not depend on the mac primitive. I've implemented an alternative that works on all platforms, less performant and of a lesser quality, but it should basically work.
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Stéphane Ducasse wrote:
Was there a reason you opted not to include RB spelling? I don't know how may people use it- I find it really handy, so my vote would be for inclusion.
if I remember it depends on some mac library
Stef
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
There is also an internal spell check, for other platforms. RBInternalSpellChecker. ...Stan -- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Actually Michael the RBInternalSpellChecker does use the macintosh spell checker plugin so it does reuse. But I think we had a unix or open source alternative? Someone could go look. I found on the iPhone the currently RBInternalSpellChecker took up lots of memory, and did a frightful unpack initialization process at startup time (many many seconds) on an iPhone. It was ditched... On 2010-01-11, at 2:01 PM, Michael Rueger wrote:
On 1/11/2010 10:59 PM, Stan Shepherd wrote:
There is also an internal spell check, for other platforms. RBInternalSpellChecker.
<broken record on> in Sophie we built a platform independent spell checker </broken record on>
;-)
Michael
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- =========================================================================== John M. McIntosh <johnmci@smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================
I found on the iPhone the currently  RBInternalSpellChecker took up lots of memory, and did a frightful unpack initialization process at startup time (many many seconds) on an iPhone. It was ditched...
That was fixed a long time ago. I flushed the cache on shutDown and it only reinitializes it again if it is used. Luka -- Lukas Renggli http://www.lukas-renggli.ch
On Mon, Jan 11, 2010 at 10:59 PM, Stan Shepherd <stan.shepherd414@gmail.com>wrote:
Stéphane Ducasse wrote:
Was there a reason you opted not to include RB spelling? I don't know
how
may people use it- I find it really handy, so my vote would be for inclusion.
if I remember it depends on some mac library
Stef
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
There is also an internal spell check, for other platforms. RBInternalSpellChecker.
How do you use it or enable it ? I have been using dev images for two years and I have ever seen a spell checker :(
...Stan
-- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-tp4278312p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
There is also an internal spell check, for other platforms. RBInternalSpellChecker.
How do you use it or enable it ? I have been using dev images for two years and I have ever seen a spell checker :(
This is an extension to SmallLint. Like Slime. It is run when you run code critics. Alternatively you can execute it like this: ORLintBrowser openRule: (RBCompositeLintRule rules: (RBCompositeLintRule rulesGroupedFor: RBSpellingRule) name: 'Spelling') environment: (BrowserEnvironment new forPackageNames: #('Kernel' 'Collections-Abstract')) Maybe I should add a menu to the already long refactoring commands? Lukas -- Lukas Renggli http://www.lukas-renggli.ch
This is an extension to SmallLint. Like Slime. It is run when you run code critics.
Alternatively you can execute it like this:
ORLintBrowser     openRule: (RBCompositeLintRule rules: (RBCompositeLintRule rulesGroupedFor: RBSpellingRule) name: 'Spelling')     environment: (BrowserEnvironment new forPackageNames: #('Kernel' 'Collections-Abstract'))
Maybe I should add a menu to the already long refactoring commands?
With Helvetia you get it live in the text editor as a wavy red line. Along with the other lint rules as a wavy yellow line. Lukas -- Lukas Renggli http://www.lukas-renggli.ch
On Mon, Jan 11, 2010 at 11:26 PM, Lukas Renggli <renggli@gmail.com> wrote:
This is an extension to SmallLint. Like Slime. It is run when you run code critics.
Alternatively you can execute it like this:
ORLintBrowser openRule: (RBCompositeLintRule rules: (RBCompositeLintRule rulesGroupedFor: RBSpellingRule) name: 'Spelling') environment: (BrowserEnvironment new forPackageNames: #('Kernel' 'Collections-Abstract'))
Maybe I should add a menu to the already long refactoring commands?
Yes, maybe this will be easier to use than having to run the lints.
With Helvetia you get it live in the text editor as a wavy red line.
Along with the other lint rules as a wavy yellow line.
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Jan 11, 2010, at 11:24 PM, Lukas Renggli wrote:
There is also an internal spell check, for other platforms. RBInternalSpellChecker.
How do you use it or enable it ? I have been using dev images for two years and I have ever seen a spell checker :(
This is an extension to SmallLint. Like Slime. It is run when you run code critics.
Alternatively you can execute it like this:
ORLintBrowser openRule: (RBCompositeLintRule rules: (RBCompositeLintRule rulesGroupedFor: RBSpellingRule) name: 'Spelling') environment: (BrowserEnvironment new forPackageNames: #('Kernel' 'Collections-Abstract'))
Maybe I should add a menu to the already long refactoring commands?
we should a panel and a better ui for rb and smalllint May be laurent screencast will create vocations :) Stef
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Thank you for your good work Mariano. I use your image for my development right now. The inspector is crashing in unexpected ways. Just try : #(1 2 3 4 5 6 7 9 10) inspect. and in the panel below on the right, just evaluate for example : 3+7 with CTRL-D several times. After a while, the following screen appears. 2010/1/10 Mariano Martinez Peck <marianopeck@gmail.com>:
Hi Folks/Beta-Testers!
I have prepare a new PharoDev image. This image, has same differences with the previous ones that you should know:
1) This is the first Dev image I ever prepare. I adapt to Mac OS Damien's bash scripts to build them and I also cleanup all the Squeak stuff from those bash scripts. So, maybe there are some problems. Forgive me if this is the case. I would like you to check, not only the Image in itself but also the zip. The package.txt, changelog, the fonts, etc.
2) This image puts TrueType fonts again. We won't put StrikeFonts or DejaVu package until there is big bug with them. We know those fonts are faster, but still a bit buggy. If you fix those issues, cool!
3) This image DOES NOT include O2. I know there are a lot of people who use it (mostly in Moose), but unfortunately, this was a decision taken. O2 depends and overrides OB making this more unstable sometimes. The same as the TrueType, we will put O2 again when this can be perfectly load in a PharoCore image without anything about OB. Sorry, but we rather affect only O2 users and not all. If you want packages support, then help in O2 development.
4) In previous Dev images only tests from PharoCore were included. Now, it also includes the tests from the external packages loaded.
5) This image was build using Metacello configurations. If you want, compare the installScript.st from this image to the previous one.
6) There is no Web image this time. If you want to install Seaside 2.8.4 evaluate:
Gofer new    squeaksource: 'MetacelloRepository';    package: 'ConfigurationOfSeaside28';    load.
(Smalltalk at: #ConfigurationOfSeaside28) load
And if you want Seaside 3.0 evaluate:
Gofer new    squeaksource: 'MetacelloRepository';    package: 'ConfigurationOfSeaside30';    load.
(Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion
However, I am not sure if this is perfectly working in Pharo.
Ok .... Here is the link: https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1....
I will wait a couple of days now and I will also start to use this image for my development. If there are issues, report them. If we have big issues, this image is not release. On the other hand, if it works well, we release it.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/
Hi:
2010/1/10 Mariano Martinez Peck <marianopeck@gmail.com>:
Hi Folks/Beta-Testers!
6) There is no Web image this time. If you want to install Seaside 2.8.4 evaluate:
Gofer new    squeaksource: 'MetacelloRepository';    package: 'ConfigurationOfSeaside28';    load.
(Smalltalk at: #ConfigurationOfSeaside28) load
And if you want Seaside 3.0 evaluate:
Gofer new    squeaksource: 'MetacelloRepository';    package: 'ConfigurationOfSeaside30';    load.
(Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion
However, I am not sure if this is perfectly working in Pharo.
I started today, with the intention of port a new system I'm developing directly to Seaside 3.0. All the installation seems to works ok, I must try more yet, but a thing I noticed is not included and should by (imho) is Magritte. Just my 0.02 Cheers. Germán.
After this mail I tried to install Magritte using "ConfigurationOfMagritte" from MetacelloRepository, but fails. This version of Magritte don't install with Seaside 3.0 ? Cheers. Germán. 2010/1/16 Germán Arduino <garduino@gmail.com>:
Hi:
2010/1/10 Mariano Martinez Peck <marianopeck@gmail.com>:
Hi Folks/Beta-Testers!
6) There is no Web image this time. If you want to install Seaside 2.8.4 evaluate:
Gofer new    squeaksource: 'MetacelloRepository';    package: 'ConfigurationOfSeaside28';    load.
(Smalltalk at: #ConfigurationOfSeaside28) load
And if you want Seaside 3.0 evaluate:
Gofer new    squeaksource: 'MetacelloRepository';    package: 'ConfigurationOfSeaside30';    load.
(Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion
However, I am not sure if this is perfectly working in Pharo.
I started today, with the intention of port a new system I'm developing directly to Seaside 3.0.
All the installation seems to works ok, I must try more yet, but a thing I noticed is not included and should by (imho) is Magritte.
Just my 0.02
Cheers. Germán.
Thanks Germán, you asked a very good question. I already asked Dale as soon as I read your email. I suggest you subscribe to metacello group as Dale is maintaining all Seaside related configurations. For the moment, would you mind trying this in this dev (clean): That will load Seaside 2.8 + Magritte (ConfigurationOfMagritte project version: '1.2.1') load: #('Magritte-Model' 'Magritte-Tests' 'Magritte-Seaside' ) I didn't found anything for 3.0 And for Pier + Magritte + Seaside 2.8 (ConfigurationOfPier project version: '1.2.1') load That's all I know for the moment. However, remember that you can install Seaside in other ways for the moment. For example you can look at the script used in the dev image before (I attach it if you want to look). However, all these configurations will be fixed soon. Thanks Mariano On Sat, Jan 16, 2010 at 5:52 PM, Germán Arduino <garduino@gmail.com> wrote:
After this mail I tried to install Magritte using "ConfigurationOfMagritte" from MetacelloRepository, but fails.
This version of Magritte don't install with Seaside 3.0 ?
Cheers. Germán.
2010/1/16 Germán Arduino <garduino@gmail.com>:
Hi:
2010/1/10 Mariano Martinez Peck <marianopeck@gmail.com>:
Hi Folks/Beta-Testers!
6) There is no Web image this time. If you want to install Seaside 2.8.4 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside28'; load.
(Smalltalk at: #ConfigurationOfSeaside28) load
And if you want Seaside 3.0 evaluate:
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load.
(Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion
However, I am not sure if this is perfectly working in Pharo.
I started today, with the intention of port a new system I'm developing directly to Seaside 3.0.
All the installation seems to works ok, I must try more yet, but a thing I noticed is not included and should by (imho) is Magritte.
Just my 0.02
Cheers. Germán.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Thanks by the response Mariano. As I've said before I'm not using yet Seaside 3.0, but as I'm developing a new system, wanted to try to port now when the system is being born. I'm also on Metacello list, will check about this. My question was because my systems use heavily Magritte and need to have it on 3.0 to try anything. Thanks. Germán. 2010/1/16 Mariano Martinez Peck <marianopeck@gmail.com>:
Thanks Germán, you asked a very good question. I already asked Dale as soon as I read your email. I suggest you subscribe to metacello group as Dale is maintaining all Seaside related configurations.
For the moment, would you mind trying this in this dev (clean):
That will load Seaside 2.8 + Magritte
(ConfigurationOfMagritte project version: '1.2.1') load: #('Magritte-Model' 'Magritte-Tests' 'Magritte-Seaside' )
I didn't found anything for 3.0
And for Pier + Magritte + Seaside 2.8
(ConfigurationOfPier project version: '1.2.1') load
That's all I know for the moment. However, remember that you can install Seaside in other ways for the moment. For example you can look at the script used in the dev image before (I attach it if you want to look). However, all these configurations will be fixed soon.
Thanks
Mariano
On Sat, Jan 16, 2010 at 5:52 PM, Germán Arduino <garduino@gmail.com> wrote:
After this mail I tried to install Magritte using "ConfigurationOfMagritte" from MetacelloRepository, but fails.
This version of Magritte don't install with Seaside 3.0 ?
Cheers. Germán.
2010/1/16 Germán Arduino <garduino@gmail.com>:
Hi:
2010/1/10 Mariano Martinez Peck <marianopeck@gmail.com>:
Hi Folks/Beta-Testers!
6) There is no Web image this time. If you want to install Seaside 2.8.4 evaluate:
Gofer new    squeaksource: 'MetacelloRepository';    package: 'ConfigurationOfSeaside28';    load.
(Smalltalk at: #ConfigurationOfSeaside28) load
And if you want Seaside 3.0 evaluate:
Gofer new    squeaksource: 'MetacelloRepository';    package: 'ConfigurationOfSeaside30';    load.
(Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion
However, I am not sure if this is perfectly working in Pharo.
I started today, with the intention of port a new system I'm developing directly to Seaside 3.0.
All the installation seems to works ok, I must try more yet, but a thing I noticed is not included and should by (imho) is Magritte.
Just my 0.02
Cheers. Germán.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (16)
-
Adrian Lienhard -
Benoit St-Jean -
Esteban Lorenzano -
Germán Arduino -
John M McIntosh -
Lukas Renggli -
Marcus Denker -
Mariano Martinez Peck -
Matthias Berth -
Michael Rueger -
Miguel Enrique Cobá Martinez -
Schwab,Wilhelm K -
Serge Stinckwich -
Stan Shepherd -
Stéphane Ducasse -
Tudor Girba