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

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

by Lukas Renggli

>> After that I have only two tests failing :) >> >> - testPushAlpaBeta >> - testUpdatesSelection >> >> The same it is here: http://hudson.lukas-renggli.ch/job/Development/lastCompletedBuild/testRepor… > > 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(a)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

Jan. 10, 2010

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

by Mariano Martinez Peck

On Sun, Jan 10, 2010 at 9:10 PM, <csrabak(a)bol.com.br> wrote: > Em 10/01/2010 17:46, Mariano Martinez Peck <marianopeck(a)gmail.com> > escreveu: > > > On Sun, Jan 10, 2010 at 8:37 PM, <csrabak(a)bol.com.br> wrote: > > Em 10/01/2010 13:04, Mariano Martinez Peck <marianopeck(a)gmail.com> > > escreveu: > > > > > > > PharoCore1.0rc1 Latest update: #10505 > > > > OK. > > > > > > > And if I am in Pharo I would see > > > Pharo1.0-10505-rc1dev10.01.1 > > Isn't this ^^^^^ completely redundant with: > > > > > PharoCore1.0rc1 Latest update: #10505 <<<<<<<<<--- this? > > > > > > the problem is what I have already said. If the user did a system > > update, the core will be higher that the dev image, and not the > > same. > > I'm not so sure if I undertand this in full, so I'll test my > understanding: > > Do your assertion above means that an hypothetical: > > Pharo1.0-10505-rc1dev10.01.1 that after some updates ends up reponding > in System->About this: > > Pharo1.0-10505-rc1dev10.01.1 > PharoCore1.0rc1 Latest update: #10510 > > You say that it would be *different* than a brand new downloaded: > > Pharo1.0-10510-rc1dev10.01.1 > PharoCore1.0rc1 Latest update: #10510 > > Is it? > > Exactly. Maybe is just a little detail. I don't know. > > Maybe we can just don't care about this case or disable the system > > update in dev as we are discussing in another thread. > > As an after thought after seeing other posts on the issue, I think > more than a generic warning that "may break the image" the Monticello > comments and/or a simple explanation on the reasons and affected > packages *before* the update starts with an option to proceed or abort > is much in need. > > Yes, maybe. Then thing is that I am not sure in which cases it would break. Only in overrides? How many overrides do we have from external pacakges in Core stuff? I have no idea. > > -- > Cesar Rabak > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 10, 2010

Re: [Pharo-project] #11147 update breaks 1.1 dev image

by Mariano Martinez Peck

On Sun, Jan 10, 2010 at 9:02 PM, Martin McClure <martin(a)hand2mouse.com>wrote: > Mariano Martinez Peck wrote: > > My question is, do you really need a dev 1.1 image? It was removed from > > the website as most of the tools are not working yet in 1.1. > > > > Why you cannot use 1.0 dev ? > > I'm working on the hashed collection speedup, which I believe is only to > be integrated into 1.1. And the affected code has changed in 1.1, and > some of the code affected is not in the core, so I wanted to use an > up-to-date dev image. > > Let me see if I understood. There is some code that will be affected, not only for the core but also from external packages ? If this is correct, I will wait a bit until 1.0 is released, the tools are working in 1.1 and we start to build 1.1 Dev images. > But I guess I should just do a version for the 1.1 core, and each > additional package that would be affected can be updated independently > later. > > Yes, I guess. The other laternative is to try each Metacello configuration for each package and see if they work. Maybe I don't know, you want OCompletion, and that is working. So, giving a try is very easy. To look the current Metacello configurations, you can look in http://www.squeaksource.com/MetacelloRepository However, I really don't know even if Metacello is working in 1.1 images. Cheers Mariano > Thanks for the info, > > -Martin > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 10, 2010

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

by Schwab,Wilhelm K

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(a)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(a)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-tp4278312… Sent from the Pharo Smalltalk mailing list archive at Nabble.com. _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 10, 2010

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

by Mariano Martinez Peck

On Sun, Jan 10, 2010 at 9:02 PM, Stan Shepherd <stan.shepherd414(a)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-tp4278312… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 10, 2010

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

by csrabak＠bol.com.br

Em 10/01/2010 17:46, Mariano Martinez Peck <marianopeck(a)gmail.com> escreveu: > On Sun, Jan 10, 2010 at 8:37 PM, <csrabak(a)bol.com.br> wrote: > Em 10/01/2010 13:04, Mariano Martinez Peck <marianopeck(a)gmail.com> > escreveu: > > > > PharoCore1.0rc1 Latest update: #10505 > > OK. > > > > And if I am in Pharo I would see > > Pharo1.0-10505-rc1dev10.01.1 > Isn't this ^^^^^ completely redundant with: > > > PharoCore1.0rc1 Latest update: #10505 <<<<<<<<<--- this? > > > the problem is what I have already said. If the user did a system > update, the core will be higher that the dev image, and not the > same. I'm not so sure if I undertand this in full, so I'll test my understanding: Do your assertion above means that an hypothetical: Pharo1.0-10505-rc1dev10.01.1 that after some updates ends up reponding in System->About this: Pharo1.0-10505-rc1dev10.01.1 PharoCore1.0rc1 Latest update: #10510 You say that it would be *different* than a brand new downloaded: Pharo1.0-10510-rc1dev10.01.1 PharoCore1.0rc1 Latest update: #10510 Is it? > Maybe we can just don't care about this case or disable the system > update in dev as we are discussing in another thread. As an after thought after seeing other posts on the issue, I think more than a generic warning that "may break the image" the Monticello comments and/or a simple explanation on the reasons and affected packages *before* the update starts with an option to proceed or abort is much in need. -- Cesar Rabak

Jan. 10, 2010

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

by Stan Shepherd

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-tp4278312… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 10, 2010

Re: [Pharo-project] #11147 update breaks 1.1 dev image

by Martin McClure

Mariano Martinez Peck wrote: > My question is, do you really need a dev 1.1 image? It was removed from > the website as most of the tools are not working yet in 1.1. > > Why you cannot use 1.0 dev ? I'm working on the hashed collection speedup, which I believe is only to be integrated into 1.1. And the affected code has changed in 1.1, and some of the code affected is not in the core, so I wanted to use an up-to-date dev image. But I guess I should just do a version for the 1.1 core, and each additional package that would be affected can be updated independently later. Thanks for the info, -Martin

Jan. 10, 2010

Re: [Pharo-project] #11147 update breaks 1.1 dev image

by Mariano Martinez Peck

On Sun, Jan 10, 2010 at 8:54 PM, Alain Plantec <alain.plantec(a)free.fr>wrote: > Martin McClure a Ã©crit : > > Marcus Denker wrote: > > > >> 11147 > >> ----- > >> > >> Issue 1761: Unloadable-reloadable Services-Base + DeprecatedPreferences > packages (part 1 - 3) > >> > >> ... some packages are dirty. This will be fixed next, together with part > 4 and a cleanup of packages that > >> are defined wrongly. > >> > > > > When trying to update the latest downloaded 1.1-dev image (11112) it > > reaks on 11147 with MNU: AnObsoletePreferences class>>doesNotUnderstand: > > #preferenceAt:ifAbsent: > > > yes, the update is incomplete (need for part 4 which reintegrates > Preferences that is needed for pharo-dev) > I wouldn spare to much time in Dev 1.1 images. That's why we remove them from the website. They are very unstable because , of course, the tools are now working yet on it. > > And then the debugger can't be opened, because of similar DNUs. > > > thanks for reporting, I will check. > Cheers > Alain > > > Maybe this isn't supposed to work, that the update stream is only to > > update core images, not dev? > > > > If so, I could use the instructions on how to make a 1.1 dev image from > > a core. I think the Metacello process for this is still 1.0 only? > > > > Regards, > > > > -Martin > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 10, 2010

Re: [Pharo-project] Finalization quirk

by John M McIntosh

Yes, usually the finalization logic is a separate high priority process. I think in VisualAge you can also manually call a primitive to get more finalized objects as a way of hurrying finalization along. I have seen a case at a client where their "higher* priority task stalled finalization, but this was a mistake on their part by a novice, lowering the priority under memory management tasks fixed the problem. On 2010-01-10, at 2:45 AM, Philippe Marschall wrote: > On 06.01.2010 21:27, John M McIntosh wrote: >> Bill, I always tell people >> >> (a) finalization will occur later, not when you think it should >> (b) finalization will occur slower/faster than you think. >> (c) both (a) & (b) will vary > > (d) finalization will occur in a different process, right? > > Cheers > Philippe > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Jan. 10, 2010