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

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

by Alain Plantec

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

Jan. 10, 2010

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

by Mariano Martinez Peck

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: > > > On Sun, Jan 10, 2010 at 3:38 PM, Michael Roberts > > <mike(a)mjr104.co.uk> wrote: > > > > 2010/1/10 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > [snipped] > > > > > >> and you can change the suffix as well, but personally i would > > >> not use the date in the image name. > > >> > > > For the date you refer to year, month and number of version > > > inside the month ? > > > > yes I think it is too complicated a version scheme. The dev tag is > > also synonymous with Pharo. > > so if your Pharo image is currently Pharo1.0-10505-rc1dev10.01.1 I > > would call it Pharo-1.0-10505-rc1. This is the same scheme that the > > core image uses, and Pharo 1.1 will have this behaviour already > > using #imageVersionString since it is in 1.1. > > > > > > That's cool. I evaluate: > > SystemVersion current version: 'Pharo-1.0-10505-rc1' > > And seems to be almost what I want. It would be cool (maybe not > > for 1.0, but for 1.1) if we can see not only the version of Pharo, > > but also opf the pharoCore...So, SystemVersion could understand: > > coreVersion: and version: > > Then in System -> About, if I am in a core image I would see: > > > > 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. Maybe we can just don't care about this case or disable the system update in dev as we are discussing in another thread. > -- > 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 7:59 PM, Martin McClure <martin(a)hand2mouse.com>wrote: > 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: > We are discussing exactly this in another thread. Would be cool to have your opinion there. > > And then the debugger can't be opened, because of similar DNUs. > > Maybe this isn't supposed to work, that the update stream is only to > update core images, not dev? > Not, it is not supposed to work always. And yes, is ONLY for core. > > 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? > > 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 ? Thanks mariano Regards, > > -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] Allow or disable System Update in PharoDev images ?

by csrabak＠bol.com.br

Can't it be left as user setting that can be selected ('decided') after downloading the image? -- Cesar Rabak Em 10/01/2010 13:45, Mariano Martinez Peck < marianopeck(a)gmail.com > escreveu: It is a simple question. Do we allow that or not.Â Miguel wrote the 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 We have to take a decision. Cheers Mariano

Jan. 10, 2010

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

by csrabak＠bol.com.br

Em 10/01/2010 13:04, Mariano Martinez Peck < marianopeck(a)gmail.com > escreveu: > On Sun, Jan 10, 2010 at 3:38 PM, Michael Roberts > <mike(a)mjr104.co.uk> wrote: > > 2010/1/10 Mariano Martinez Peck <marianopeck(a)gmail.com>: > [snipped] > > > >> and you can change the suffix as well, but personally i would > >> not use the date in the image name. > >> > > For the date you refer to year, month and number of version > > inside the month ? > > yes I think it is too complicated a version scheme. The dev tag is > also synonymous with Pharo. > so if your Pharo image is currently Pharo1.0-10505-rc1dev10.01.1 I > would call it Pharo-1.0-10505-rc1. This is the same scheme that the > core image uses, and Pharo 1.1 will have this behaviour already > using #imageVersionString since it is in 1.1. > > > That's cool. I evaluate: > SystemVersion current version: 'Pharo-1.0-10505-rc1' > And seems to be almost what I want. It would be cool (maybe not > for 1.0, but for 1.1) if we can see not only the version of Pharo, > but also opf the pharoCore...So, SystemVersion could understand: > coreVersion: and version: > Then in System -> About, if I am in a core image I would see: > > 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? -- Cesar Rabak

Jan. 10, 2010

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

by Mariano Martinez Peck

On Sun, Jan 10, 2010 at 5:58 PM, Tudor Girba <tudor.girba(a)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(a)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(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 5:02 PM, Lukas Renggli <renggli(a)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/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. > > Excellent. > > > > :) > > > > 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 10, 2010

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

by Martin McClure

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: And then the debugger can't be opened, because of similar DNUs. 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

Jan. 10, 2010

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

by Yanni Chiu

Lukas Renggli wrote: > Thank you for adding me to the repository. I will commit my changes to > the HudsonBuildTools there, if this is ok with you? > > I've made some significant changes: > > - added methods to run all tests of a package > - make the distinction between error and failure > - measure the time it took to run a test > - display the exception and stack trace of a failing test > - encode all XML values properly (I had some problems with the stacks) Wow this is great. You guys work so fast, I can't keep up. -- Yanni

Jan. 10, 2010

Re: [Pharo-project] Pharo Smalltalk â¥

by merlyn＠stonehenge.com

>>>>> "Guido" == Guido Stepken <gstepken(a)googlemail.com> writes: Guido> Pharo Smalltalk â¥ Guido> ifTrue: [developer honk] I'm not sure developer should understand how to honk. :) -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <merlyn(a)stonehenge.com> <URL:http://www.stonehenge.com/merlyn/> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion

Jan. 10, 2010