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

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by StÃ©phane Ducasse

> Ok, I had spend a couple of hours with Michael Rueger on the mac menu bug. But I'm not sure if he > got around to sending out any changes before he took some time off. > > If someone can test this I can offer up some change sets for review. I've never been able to recreate this > here so someone else has to try. please send. We removed the mac menu for 1.0 but we would like to have it in 1.1 Stef

Jan. 25, 2010

Re: [Pharo-project] about imageSegments

by Mariano Martinez Peck

On Mon, Jan 25, 2010 at 9:02 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Hi Stef > > We can move the few classes related to image segments into a separate > package in SqueakSource. The system (ideally) does not depend on them so it > should not be too hard to package them separately. > > There are several things I would like to say: - The ImageSegment code really suc.. and it is very difficult to understand, maintain and test. It is full of etoys, morphic, project and other stuff. - There are a lot of methods that do a lot of black magic - The code is VERY fragile and may be broke any time (if it is not already broken) However, - Some people use it - It is fast If you ask if we should remove it form core, I would say: - It won't very VERY easy to completely remove them. There are some places where ImageSegment are inside the code and won't be easy to remove. Or at least, leave the code with Smalltalk at: #ImageSegment ifPresent: [blah..] Look for example, Behavior >> allInstancesEverywhereDo: ClassDescription >> updateInstancesFrom: All those doGently and isInMemory So...remove then would be easy, but put them in a separate package, still working and without Smalltalk at: ifPresent I think it would be difficult. I have already clean, fix and test it as much as possible. I will let them in Pharo and as Martin said, getting it better when someone has time and is willing to do it. Another problem is that if we remove ImageSegment to an external package, will be soon outdated and nobody will maintain it. Cheers Mariano Adrian > > On Jan 22, 2010, at 21:35 , StÃ©phane Ducasse wrote: > > > hi guys > > > > the more I read about imageSegments the more I would like to remove them > (or to package them > > carefully - not sure that this is possible) and may be add a new class > to > > just have one simple way of invoking the save (but not swapping back in) > > > > I think that mariano diving into them is a great phd exercise but on the > long run > > I see it as a brittle mechanism. > > > > what do you think? > > > > Stef > > _______________________________________________ > > 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. 25, 2010

Re: [Pharo-project] [update] #10507

by Mariano Martinez Peck

On Sun, Jan 24, 2010 at 10:43 PM, Stefan Marr <pharo(a)stefan-marr.de> wrote: > > So to explain: waiting two days until making the link on the download > page: ok. We did that. Not announcing it yet. Ok, > > we will announce when it's clear it's stable. But having people download > an old image without the bug-fixes by default? > > No. > > > > We are already in Beta. Clearly marked. There is no need for a private, > more secret special beta. > What is a Release Candidate meant for? > > Well, I think, it is meant to be downloaded and tested. > After all, it is a RC, if it blows up in your face, then it is something > you will report. > > At least that is the way it is done in the world of PHP. > > Several iterations, going from beta (for early adopters only, people living > on the edge), to RCs with several iterations, where basically every one out > there with a large code base is asked to test it extensively to get to a > point where only minor issues remain. The last RC where no critical issues > have been found will then be labeled as final x.y.0 release. > > And that only works, if RCs are actually tested by a large group of people. > > Ok...you convinced me. Ok...I am agree :) Thanks Stefan > Best > Stefan > > > > > > > > Marcus > > > > > > -- > > Marcus Denker -- http://www.marcusdenker.de > > INRIA Lille -- Nord Europe. Team RMoD. > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr <http://soft.vub.ac.be/%7Esmarr> > Phone: +32 2 629 3956 > Fax: +32 2 629 3525 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 25, 2010

Re: [Pharo-project] TestIndenting fails with Exupery (was: [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2)

by Mariano Martinez Peck

2010/1/25 laurent laffont <laurent.laffont(a)gmail.com> > Hi, > > Now I know how to build my own squeak vm with FT2Plugin (yeepeee !!). So: > > Linux + FT2Plugin + Squeak vm = success > Linux + FT2Plugin + Exupery vm = fails > > I put the built vm here: > http://lolgzs.free.fr/pharo/Squeak-3.11.3.2135-src-with-FT2Plugin.tar.gz > > The squeak binary is build/squeak. > > Thanks Laurent! > I will have less time from today as I'm starting a new job. > > Good luck! In smalltalk ? > Cheers, > > Laurent > > > > On Sun, Jan 24, 2010 at 10:01 PM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > >> 2010/1/24 Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> >> >> On 24.01.2010 21:36, laurent laffont wrote: >>> >>> It's the opposite for me :) >>> >>> TestIndenting>>testCR2 and >>> TestIndenting>>testNewLineLeaveSpacesOnOldLine fails because FTPlugin is >>> here (in exupery). If I delete FTPlugin directory, these tests succeed. >>> >>> Laurent >>> >>> Technically, the tests don't fail because the Plugin no longer exists >>> (ie, these tests failing does not indicate there's anything wrong with the >>> plugin), but because a font which satisfies the hardcoded assumptions about >>> width is used when no FreeType-fonts are availiable. ;) >>> >> >> >> You're right. The test results depends on the font that is choosed as >> default font. May be the tests should change the Form object font ? >> >> Laurent >> >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 25, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Mariano Martinez Peck

On Mon, Jan 25, 2010 at 2:38 AM, John M McIntosh < johnmci(a)smalltalkconsulting.com> wrote: > Ok, I had spend a couple of hours with Michael Rueger on the mac menu bug. > But I'm not sure if he > got around to sending out any changes before he took some time off. > > If someone can test this I can offer up some change sets for review. I've > never been able to recreate this > here so someone else has to try. > Cool. If you send me changesets I can test it. > > > On 2010-01-24, at 12:05 PM, StÃ©phane Ducasse wrote: > > > Michael > > > > We have 1.0 (on final release cycle) and 1.1-unstable and for both we > have core and dev images. > > > > 1.0 is on release period for too long now mainly because of a vicious bug > due to mac menu > > that duplicated events. > > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: > squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 25, 2010

Re: [Pharo-project] RBSpelling errors when class has Pool Dictionary - Re: [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Mariano Martinez Peck

On Sun, Jan 24, 2010 at 11:43 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > > Wiiiii :) Only one expected failire! > > Yeah, I don't know how to fix that one. And it probably won't be in > the near future. Maybe at some point somebody understands why it is > broken. > > > Thanks Lukas!! Next Pharo image will use RB 1.2. > > RB 1.2 ? > > hahahahha sorry. I meant the 1.2 version of the ConfigurationOfRefactoringBrowser :) > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 25, 2010

Re: [Pharo-project] about imageSegments

by Adrian Lienhard

Hi Stef We can move the few classes related to image segments into a separate package in SqueakSource. The system (ideally) does not depend on them so it should not be too hard to package them separately. Adrian On Jan 22, 2010, at 21:35 , StÃ©phane Ducasse wrote: > hi guys > > the more I read about imageSegments the more I would like to remove them (or to package them > carefully - not sure that this is possible) and may be add a new class to > just have one simple way of invoking the save (but not swapping back in) > > I think that mariano diving into them is a great phd exercise but on the long run > I see it as a brittle mechanism. > > what do you think? > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 25, 2010

Re: [Pharo-project] TestIndenting fails with Exupery (was: [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2)

by laurent laffont

Hi, Now I know how to build my own squeak vm with FT2Plugin (yeepeee !!). So: Linux + FT2Plugin + Squeak vm = success Linux + FT2Plugin + Exupery vm = fails I put the built vm here: http://lolgzs.free.fr/pharo/Squeak-3.11.3.2135-src-with-FT2Plugin.tar.gz The squeak binary is build/squeak. I will have less time from today as I'm starting a new job. Cheers, Laurent On Sun, Jan 24, 2010 at 10:01 PM, laurent laffont <laurent.laffont(a)gmail.com > wrote: > 2010/1/24 Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> > > On 24.01.2010 21:36, laurent laffont wrote: >> >> It's the opposite for me :) >> >> TestIndenting>>testCR2 and >> TestIndenting>>testNewLineLeaveSpacesOnOldLine fails because FTPlugin is >> here (in exupery). If I delete FTPlugin directory, these tests succeed. >> >> Laurent >> >> Technically, the tests don't fail because the Plugin no longer exists (ie, >> these tests failing does not indicate there's anything wrong with the >> plugin), but because a font which satisfies the hardcoded assumptions about >> width is used when no FreeType-fonts are availiable. ;) >> > > > You're right. The test results depends on the font that is choosed as > default font. May be the tests should change the Form object font ? > > Laurent > >

Jan. 25, 2010

Re: [Pharo-project] Pharo dev image rc2 thoughts

by Miguel Enrique CobÃ¡ Martinez

El dom, 24-01-2010 a las 22:33 +0100, Mariano Martinez Peck escribiÃ³: > > > I am completely ignorant about the progress. Could you detect where is > exactly that the progress bar is initialized in that package ? Thanks Dale and Mariano. I found the place where the reset is made. The postDoit for ImageForDevelopers calls DEVImageCreator default install that calls self setTheme that calls: UIThemeStandardSqueak beCurrent. UIThemeWatery2 beCurrent. that is defined in: UITheme class. There calls self current: self newDefault where current is: "Set the current ui theme." Current := aUITheme. UITheme allThemeClasses do: [:c | c changed: #isCurrent]. SystemProgressMorph reset. "reset to use new fill styles" ScrollBar initializeImagesCache. "reset to use new arrows" aUITheme updateWorldDockingBars. World themeChanged and here is the problem! (finally :)) The SystemProgressMorph reset is the culprit of the initialization of the progress bar. and is called not one but two times, because the setThemes method first install the old squeak theme (I suppose that Watery theme doesn't cover all the UI elements) and then install the watery theme. So here we have a problem. I think that it is correct to reset the progress bar when you install the theme. But I also think that *is not* the responsibility of Metacello to track this specific scenario (unless that is really simple and non-invasive to do, in that case, well, Dale is your time and we'll for sure welcome and thank that fix) Also, this problem can be solved by extracting the theme change to the installScript.st that is, DEVImageCreator>>install should remove the setTheme call and the installScript.st should do, after creating the image: DEVImageCreator default setTheme. BTW, as we are here, install also should remove: self writeListOfPackages. self openWelcomeWorkspaces. also to the installScript.st as DEVImageCreator default setTheme; writeListOfPackages; openWelcomeWorkspaces. But I digress. Returning to the problem of the reset of the progress bar, maybe the best solution is to simply remove the setTheme call because: Pharo already uses the watery theme, this was used, I think, in the dev images based on squeak. But, as you are using the ImageForDevelopers-pharo, just delete it. Dale has nothing to do after that. (but if you can change the writeListOfPackages and openWelcomeWorkspaces to the installScript that would be cool ;)). Cheers to all. SystemProgressMorph reset. "reset to use new fill styles" -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Jan. 25, 2010

Re: [Pharo-project] [update] #10507

by Miguel Enrique CobÃ¡ Martinez

El dom, 24-01-2010 a las 18:31 -0600, Miguel Enrique CobÃ¡ Martinez escribiÃ³: > El dom, 24-01-2010 a las 21:58 +0100, Marcus Denker escribiÃ³: > > On Jan 24, 2010, at 9:52 PM, Marcus Denker wrote: > > > > > > > > On Jan 24, 2010, at 9:51 PM, Mariano Martinez Peck wrote: > > >> > > >> > > >> Adrian: shouldn't we update http://www.pharo-project.org/home because it says "Current status: 1.0 RC1" > > >> > > > yes, and we need to link it on the download page... there are quite some downloads per day. > > > > > > I will do that. > > > > > > Done: > > > > http://www.pharo-project.org/home > > It is necessary to put a sources file download link in the pharo > download page. The dev image zip already contains it. > > I think that it should be in the PharoCore section that it doesn't > contains it. I was wrong. Both the dev image zip and the PharoCore zip include the sources file. So maybe this link shouldn't appear on the download page, just in the inria gforge page. cheers > > Cheers > > http://www.pharo-project.org/pharo-download > > > > -- > > Marcus Denker -- http://www.marcusdenker.de > > INRIA Lille -- Nord Europe. Team RMoD. > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Jan. 25, 2010