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

[Pharo-project] Pharo sprint @ Brussels

by Stephan Eggermont

I'll be there on Saturday. Stephan Eggermont

June 6, 2010

Re: [Pharo-project] issue 2512 - PNG Tests failure

by Henrik Sperre Johansen

On 06.06.2010 03:18, Henrik Sperre Johansen wrote: > On 05.06.2010 20:10, Oscar Nierstrasz wrote: >> No, we have other tests that fail only when running all tests -- >> those that test finalization. >> >> The PNG tests fail reliably in 1.1. Unfortunately we were unable to >> narrow down the cause. >> >> There appears to be an off by one error somewhere in encoding (or >> decoding) the Color black. >> >> - on > Related to: > http://code.google.com/p/pharo/issues/detail?id=2486 > perhaps? > Essentially, 32 bit transparent black used to be 0(r) 0(g) (1)b (0)a > instead of 0(r) 0(g) 0(b) 0(a). > Which, was wrong. (And caused trouble when using transparent black as > one of the colors in a bitblt operation) > > Cheers, > Henry or (1)a 0(r) 0(g) (0)b instead of 0(a) 0(r) 0(g) 0(b) / (0)a 0(r) 0(g) (1)b instead of 0(a) 0(r) 0(g) 0(b) Can't exactly remember the byte order. The important point is there used to be a special case where transparent black was given a 32bit pixel-value of 1 rather than 0. Cheers, Henry

June 6, 2010

Re: [Pharo-project] issue 2512 - PNG Tests failure

by Henrik Sperre Johansen

On 05.06.2010 20:10, Oscar Nierstrasz wrote: > No, we have other tests that fail only when running all tests -- those that test finalization. > > The PNG tests fail reliably in 1.1. Unfortunately we were unable to narrow down the cause. > > There appears to be an off by one error somewhere in encoding (or decoding) the Color black. > > - on Related to: http://code.google.com/p/pharo/issues/detail?id=2486 perhaps? Essentially, 32 bit transparent black used to be 0(r) 0(g) (1)b (0)a instead of 0(r) 0(g) 0(b) 0(a). Which, was wrong. (And caused trouble when using transparent black as one of the colors in a bitblt operation) Cheers, Henry

June 6, 2010

Re: [Pharo-project] GUI Layouts doc, request for comments

by Sean P. DeNigris

laurent laffont wrote: > > here's a documentation on Layout with Morphic GUI. Comments are welcome, > and > thanks to all native english people who can check the text :) > Great document! It was clear and the english was very good. I made some small grammatical/clarity enhancements. Also: * should we include info on LayoutPolicies? * there are some good examples at http://wiki.squeak.org/squeak/2141. Maybe add a link? Sean -- View this message in context: http://forum.world.st/GUI-Layouts-doc-request-for-comments-tp2244374p224450… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 5, 2010

Re: [Pharo-project] About TDD and Pharo

by Sean P. DeNigris

StÃ©phane Ducasse wrote: > > I know that keith integrated SSpec and SUnit so probably there are > enhancements there. > Thanks Steph, I had checked the Testing project before and its latest timestamp for SSpec is a few years earlier, so I think the SSpec repo has the best version. But it seems that project was in line with what I was suggesting - to have BDD tools together with the TDD tools. Sean -- View this message in context: http://forum.world.st/About-TDD-and-Pharo-tp2240686p2244477.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 5, 2010

Re: [Pharo-project] pharo and stand along GUI projects

by Douglas Brebner

On 05/06/2010 17:42, Richard Durr wrote: > Since single-fullwindow apps like garageband, finalcut, aperture et > al. are all very well accepted, a single-fullwindow app based on pharo > sounds possible. > > By accessibility (a11y) I meant support for disabled use, such as screenreaders and voice operation. Also useful for hands or eyes free operation such as while driving or other physical tasks :) > On Sat, Jun 5, 2010 at 6:28 PM, Douglas Brebner > <squeaklists(a)fang.demon.co.uk> wrote: > >> On 05/06/2010 14:39, Schwab,Wilhelm K wrote: >> >>> Native widgets are over-rated IMHO. That is not to say they have no >>> value, and it would be nice to see us make them easy to use. I am split on >>> whether I would like to see the IDE tools appear as host widgets on Linux; >>> it would probably be best to set (sorry) a preference for the image to run >>> over multiple windows or to default to what we have now which can be very >>> useful if I need to work on two or more images at one time. That is rare, >>> and most of the time I would like to see the OS' task bar include my >>> Smalltalk tools. >>> >>> >>> >> The only real advantage I see for native widgets currently is that they >> support things like accessibility, though Juan mentioned he's thought about >> that for Morphic 3 which gives me hope :) >> >

June 5, 2010

Re: [Pharo-project] pharo and stand along GUI projects

by Schwab,Wilhelm K

I largely agree, though the example of having the various SystemWindow instances able to float around the desktop can be seen as an advantage too. There are times when I would want that, and times when I would prefer a single main window and the tools confined within it. Otherwise, I agree that the commonly held idea that native==fast is more myth than fact. An app using native decoration would take on the host appearance without the need for us to maintain emulation code. Another potential advantage to multiple system windows is that it would force us to "play by the rules" with respect to input focus. With many thanks to Pinesoft, that is far less of a concern in Pharo now than it was in Squeak. Overall, emulate as much as you want. That said, I look forward to a day when we will have a choice to do otherwise. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Douglas Brebner [squeaklists(a)fang.demon.co.uk] Sent: Saturday, June 05, 2010 12:28 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] pharo and stand along GUI projects On 05/06/2010 14:39, Schwab,Wilhelm K wrote: > Native widgets are over-rated IMHO. That is not to say they have no value, and it would be nice to see us make them easy to use. I am split on whether I would like to see the IDE tools appear as host widgets on Linux; it would probably be best to set (sorry) a preference for the image to run over multiple windows or to default to what we have now which can be very useful if I need to work on two or more images at one time. That is rare, and most of the time I would like to see the OS' task bar include my Smalltalk tools. > > The only real advantage I see for native widgets currently is that they support things like accessibility, though Juan mentioned he's thought about that for Morphic 3 which gives me hope :) _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 5, 2010

Re: [Pharo-project] issue 2512 - PNG Tests failure

by Oscar Nierstrasz

No, we have other tests that fail only when running all tests -- those that test finalization. The PNG tests fail reliably in 1.1. Unfortunately we were unable to narrow down the cause. There appears to be an off by one error somewhere in encoding (or decoding) the Color black. - on On Jun 5, 2010, at 18:39, Peter Hugosson-Miller wrote: > Hmmm, weren't these the tests that failed in 1.0 if you ran all the tests in one go? I know they were in the neighbourhood anyway, since I spent some time trying to chase them down, and recognise those method names from then. > > Maybe Torsten knows a bit more about them, since he was the one that put me on the trail... > > -- > Cheers, > Peter > > 2010/6/5 Fabrizio Perin <fabrizio.perin(a)gmail.com> > http://code.google.com/p/pharo/issues/detail?id=2512 > > the following tests fail: > > > PNGReadWriterTest>>testPngEncodingColors32 > PNGReadWriterTest>>testPngDecodingColors32 > > They were both green in Pharo 1.0. Also the current implementation of PNGReadWriterTest class has been file in into the last Squeak trunk image and they are green. So the last modifications on the the PNG package cause those methods fail. > > Cheers, > > Fabrizio > > _______________________________________________ > 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

June 5, 2010

Re: [Pharo-project] pharo and stand along GUI projects

by Schwab,Wilhelm K

Of course it is possible, and at times it would even be the correct thing to do. The point is that we are currently limited to it, and that is always a sign that work remains to be done. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Richard Durr [richard.durr(a)googlemail.com] Sent: Saturday, June 05, 2010 12:42 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] pharo and stand along GUI projects Since single-fullwindow apps like garageband, finalcut, aperture et al. are all very well accepted, a single-fullwindow app based on pharo sounds possible. On Sat, Jun 5, 2010 at 6:28 PM, Douglas Brebner <squeaklists(a)fang.demon.co.uk> wrote: > On 05/06/2010 14:39, Schwab,Wilhelm K wrote: >> >> Native widgets are over-rated IMHO. That is not to say they have no >> value, and it would be nice to see us make them easy to use. I am split on >> whether I would like to see the IDE tools appear as host widgets on Linux; >> it would probably be best to set (sorry) a preference for the image to run >> over multiple windows or to default to what we have now which can be very >> useful if I need to work on two or more images at one time. That is rare, >> and most of the time I would like to see the OS' task bar include my >> Smalltalk tools. >> >> > > The only real advantage I see for native widgets currently is that they > support things like accessibility, though Juan mentioned he's thought about > that for Morphic 3 which gives me hope :) > > _______________________________________________ > 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

June 5, 2010

Re: [Pharo-project] Issue 2507: Oversized allocation does not fail correctly

by Adrian Lienhard

I updated the link. Thanks for reminding... Cheers, Adrian On Jun 5, 2010, at 19:21 , Mariano Martinez Peck wrote: > I suggested a couple of times to update the download link of the Mac vm of > the website to 4.2.4. > > Adrian, can we do this? > > Cheers > > Mariano > > On Sat, Jun 5, 2010 at 12:39 PM, Oscar Nierstrasz <oscar(a)iam.unibe.ch>wrote: > >> >> Fixed in 4.2.4 VM. >> >> - on >> >> On 5 Jun 2010, at 11:39, Oscar Nierstrasz wrote: >> >>> >>> http://code.google.com/p/pharo/issues/detail?id=2507 >>> >>> The following test in KernelTests-Exception fails in PharoCore1.1 >>> >>> AllocationTest>>testOneGigAllocation >>> >>> This test tries to allocate one gig of memory and verify that it either >> succeeds with the right size of array, or >>> allocation should fail. Instead we get an array of size 0. >>> >>> Curiously: >>> >>> (Array new: 1024*1024*1023) size. -> "Warning! Pharo is almost out of >> memory!" >>> (Array new: 1024*1024*1024) size. -> 0 >>> (Array new: 1024*1024*1025) size. -> 1048576 >>> >>> Array>>new: runs primitive 71, so this appears to be a VM bug. >>> >>> Oscar Nierstrasz >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 5, 2010