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

Re: [Pharo-project] About the collaborative pier

by Michael Roberts

Stef, Doru i have got confused as well with where pages get added. It makes sense once you understand what Pier is doing, but i have put too many pages in the wrong place. Anyway i have created a help chapter, with some tips. Please feel free to correct or add more. cheers, Mike

April 18, 2010

[Pharo-project] Help on collaborator Active book

by laurent laffont

Hi, how to: - upload / display pictures ? - correctly highlight linux commands ? I use == but here http://book.pharo-project.org/book/Virtual-Machine/Building/BuildVMOnLinux it seems that / is a special character so the lines are red. Cheers, Laurent Laffont

April 18, 2010

[Pharo-project] Fwd: Issue 1938 in pharo: related to 1910 Readonly....

by StÃ©phane Ducasse

thanks sean. I may have some time today but this is really sunny :) If people want to have a look.... http://code.google.com/p/pharo/issues/detail?id=1938 Stef Begin forwarded message: > From: pharo(a)googlecode.com > Date: April 17, 2010 11:43:52 PM GMT+02:00 > To: stephane.ducasse(a)gmail.com > Subject: Re: Issue 1938 in pharo: related to 1910 Readonly.... > > > Comment #1 on issue 1938 by sean.p.denigris: related to 1910 Readonly.... > http://code.google.com/p/pharo/issues/detail?id=1938 > > Fix is PharoInbox. Slice-Fix1938. > > All suggestions implemented. And, for DigitalSignatureAlgorithm class, it looked like maybe > writeExamplesToDisk, testKeySet, and/or example should be moved also. > > > -- > You received this message because you are listed in the owner > or CC fields of this issue, or because you starred this issue. > You may adjust your issue notification preferences at: > http://code.google.com/hosting/settings

April 18, 2010

Re: [Pharo-project] Canvas transform bug when rendering text?

by StÃ©phane Ducasse

we should release 1.1 much faster :) like that people will be able to get all the fixes.... Stef On Apr 18, 2010, at 2:42 AM, Henrik Sperre Johansen wrote: > Sorry for responding so late. but... > On 09.04.2010 11:14, Lukas Renggli wrote: >> Pay attention there is a #haltOnce in the code. Also there is >> something wrong with the line endings in the change-set. >> > :( Didn't have time to review it before submission at the time, so some debug code was left in. >> However it also breaks some window refreshing, see attached screenshot. >> >> Lukas > > Yes, for some reason, 1.0 does not contain > TransformMorph >> areasRemainingTofFill: aRectangle > > ^Array with: aRectangle > > Which is needed for a proper refresh. > As you noticed, at least it's quite visible when not present, so one is forced to determine what the proper return value should be, > Basically, areasRemaining...: should denote the non-opaque areas of the morph. > This is mostly used in the drawing algorithm, to determine coverage of a morph, and thus which areas remain to be drawn below it. > In the case of TransformMorph, the calculation for returning a decent estimate is probably more work than just telling it to draw everything below (ie. return the rectangle as the area that remains to be drawn), so that's what we do. If you have a better default, please suggest it! :D > > Cheers, > Henry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 18, 2010

Re: [Pharo-project] Fix 1938 - various changes

by StÃ©phane Ducasse

Laurent will be happy :) Because this was really the purpose of the screencast. Stef On Apr 17, 2010, at 11:49 PM, Sean P. DeNigris wrote: > > In inbox. http://code.google.com/p/pharo/issues/detail?id=1938 > > Sean DeNigris > > p.s. following the screencast > (http://pharocasts.blogspot.com/2010/03/how-to-contribute-to-pharo.html) > made it much easier to submit the code. > -- > View this message in context: http://n4.nabble.com/Fix-1938-various-changes-tp2014441p2014441.html > 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

April 18, 2010

Re: [Pharo-project] Really Important message (tm)

by StÃ©phane Ducasse

Thanks a lot!!! On Apr 17, 2010, at 11:46 PM, Sean P. DeNigris wrote: > > > StÃ©phane Ducasse wrote: >> >> - We need you! >> > > I'm in! Just submitted my first bug fix :) > > Sean > -- > View this message in context: http://n4.nabble.com/Really-Important-message-tm-tp1860396p2014439.html > 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

April 18, 2010

[Pharo-project] Fwd: [Vm-dev] InputSemaphore on Windows

by StÃ©phane Ducasse

Begin forwarded message: > From: Igor Stasenko <siguctua(a)gmail.com> > Date: April 18, 2010 3:00:02 AM GMT+02:00 > To: Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org> > Subject: Re: [Vm-dev] InputSemaphore on Windows > Reply-To: Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org> > > > On 16 April 2010 02:07, Andreas Raab <andreas.raab(a)gmx.de> wrote: >> >> On 4/15/2010 3:18 PM, Henrik Sperre Johansen wrote: >>> >>> Is there a reason why this isn't signalled when inputSemaphoreIndex > 0? >> >> None. It just doesn't bite me. If it did I would've fixed it already. Got >> patch? >> >>> In sqWin32Window.c, the comment for synchronizedSignalSemaphoreWithIndex >>> looks somewhat scary... >>> But looking at the svn logs, it seems it never was used in the >>> record...Event() functions at all, so I wondered if a problem was >>> encountered before svn was in use that lead to its removal, or if it's >>> just not done by default? >> >> The short answer is that there are so many potential issues with handling >> semaphore signals properly that at some point I just gave up. At this point, >> there is no reliable way to deliver semaphore signals, they can and they >> *do* get dropped (we've proven that). >> > Wait.. lets us separate the issues. > 1) synchronizedSignalSemaphoreWithIndex() & friends, for signaling an > arbitrary semaphore > 2) an input semaphore, which should be signaled if there are any > events pending for delivery into language side. > > For (2) , i remember you promised to fix that in no time (a fix is > quite trivial) , so then newer images could finally > stop using polling and use an input semaphore instead. > Usually, it is not a big problem with dropping an input semaphore > signals ( if that's ever possible), > because events tend to come at a regular basis, so even if image-side > missed a signal, it can catch up later, > when next event will come by. > >> Cheers, >> - Andreas >> > > -- > Best regards, > Igor Stasenko AKA sig.

April 18, 2010

[Pharo-project] Fwd: [Vm-dev] InputSemaphore on Windows

by StÃ©phane Ducasse

Begin forwarded message: > From: Igor Stasenko <siguctua(a)gmail.com> > Date: April 18, 2010 2:51:55 AM GMT+02:00 > To: Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org> > Subject: Re: [Vm-dev] InputSemaphore on Windows > Reply-To: Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org> > > > On 16 April 2010 01:18, Henrik Sperre Johansen > <henrik.s.johansen(a)veloxit.no> wrote: >> >> Is there a reason why this isn't signalled when inputSemaphoreIndex > 0? >> >> In sqWin32Window.c, the comment for synchronizedSignalSemaphoreWithIndex >> looks somewhat scary... >> But looking at the svn logs, it seems it never was used in the >> record...Event() functions at all, so I wondered if a problem was >> encountered before svn was in use that lead to its removal, or if it's just >> not done by default? >> > This function is not called, because recordXXXEvent() is already synchronous > because VM calls handleEvents(), and during that, no interpreter > activity is possible, > so it is safe to modify an input semaphore state directly. > The synchronizedSignalSemaphoreWithIndex() is used only for cases, > when you need to signal a > semaphore from other thread, than interpreter runs in. > >> Cheers, >> Henry >> > > > > -- > Best regards, > Igor Stasenko AKA sig.

April 18, 2010

[Pharo-project] Fwd: [Vm-dev] InputSemaphore on Windows

by StÃ©phane Ducasse

Begin forwarded message: > From: Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> > Date: April 18, 2010 2:24:45 AM GMT+02:00 > To: Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org> > Subject: Re: [Vm-dev] InputSemaphore on Windows > Reply-To: Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org> > > On 16.04.2010 01:07, Andreas Raab wrote: >> >> On 4/15/2010 3:18 PM, Henrik Sperre Johansen wrote: >>> Is there a reason why this isn't signalled when inputSemaphoreIndex > 0? >> >> None. It just doesn't bite me. If it did I would've fixed it already. Got patch? > Not yet, thought I'd ask the question if there was any good reason not to do so first :) > The reason I'd like it to be so, is that Pharo already includes a an EventSensor (InputEventFetcher) which relies on this, and abolishes the polling of EventSensor, but it's not used by default since InputSemaphore is not signaled on all VM's. The code should be easily* portable to Squeak as well. >> >>> In sqWin32Window.c, the comment for synchronizedSignalSemaphoreWithIndex >>> looks somewhat scary... >>> But looking at the svn logs, it seems it never was used in the >>> record...Event() functions at all, so I wondered if a problem was >>> encountered before svn was in use that lead to its removal, or if it's >>> just not done by default? >> >> The short answer is that there are so many potential issues with handling semaphore signals properly that at some point I just gave up. At this point, there is no reliable way to deliver semaphore signals, they can and they *do* get dropped (we've proven that). > As far as I could read from the latest thread about it on the Squeak list http://n4.nabble.com/More-Delay-Semaphore-fun-td67556.html#a67556, this is an issue mostly when the the waiting/signaling process is terminated, which would (probably... ) not be the case for an event fetcher. > > If I get the time to make any progress** I'll send you the modified file for review. > > Cheers, > Henry > > *As in, I haven't done it, but the code should run on both platforms. > ** Something buildable, which works as expected when InputEventSensor is active on Pharo

April 18, 2010

Re: [Pharo-project] Canvas transform bug when rendering text?

by Henrik Sperre Johansen

Sorry for responding so late. but... On 09.04.2010 11:14, Lukas Renggli wrote: > Pay attention there is a #haltOnce in the code. Also there is > something wrong with the line endings in the change-set. > :( Didn't have time to review it before submission at the time, so some debug code was left in. > However it also breaks some window refreshing, see attached screenshot. > > Lukas Yes, for some reason, 1.0 does not contain TransformMorph >> areasRemainingTofFill: aRectangle ^Array with: aRectangle Which is needed for a proper refresh. As you noticed, at least it's quite visible when not present, so one is forced to determine what the proper return value should be, Basically, areasRemaining...: should denote the non-opaque areas of the morph. This is mostly used in the drawing algorithm, to determine coverage of a morph, and thus which areas remain to be drawn below it. In the case of TransformMorph, the calculation for returning a decent estimate is probably more work than just telling it to draw everything below (ie. return the rectangle as the area that remains to be drawn), so that's what we do. If you have a better default, please suggest it! :D Cheers, Henry

April 18, 2010