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

Re: [Pharo-project] windows xp theme

by Steve Wirts

Stephen, My company has standardized on xp, so if I'm going to use squeak/pharo, I guess I'll need to build it. I'm going to start with the vistary ui and see if I can't come up with something. Thanks for your help!! s On Fri, Apr 17, 2009 at 4:59 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > hi steve > > did you check the vistary one? > Else did you check (should probably not work) the work on skins > by Stephan B. Wessels > http://www.preeminent.org/squeak/ > > There was also a zurgle look which had a good windows look > But I cannot find it. > > Stef > > On Apr 17, 2009, at 9:02 PM, Steve Wirts wrote: > > > Is there any chance a windows xp theme might eventually be included > > in pharo? _______________________________________________ > > 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 >

April 20, 2009

Re: [Pharo-project] Lots of characters lost while typing in Unix

by Nicolas Cellier

2009/4/20 Igor Stasenko <siguctua(a)gmail.com>: > 2009/4/20 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> Would a platform specific code or infrastructure help there? >> > > There should be some kind of detection algorythm , which can switch > between polling and waiting on input semaphore. > My proposal is to change the primitive (primInterruptSemaphore: > aSemaphore ) to return boolean value, showing that input semaphore > signaling is available. > Then the code can use polling or waiting depending on returned result > (the primitive in older VM's don't return informal value - it just > returns a receiver). > Andreas disagree with this approach, saying that same could be > achieved w/o changes in VM by checking if input semaphore ever > signaled, and if so, then switch from polling (which should be > installed by default) to waiting. > Both ways is doable, and should work well, it just shows our different approach. > Andreas is right on this point, though your proposition makes thing simpler. But if he didn't introduce support for event-driven loop in windows VM, he is wrong: feeding a polling loop with an event-loop is easy, the reverse is not. I bet he spent more time arguing in the thread, than necessary for introducing requested change in the VM :) ... unless... I tried this in windows: (SmalltalkImage current vmVersion. -> 'Squeak3.10.2 of ''5 June 2008'' [latest update: #7179]') InputEventFetcher deinstall; install. InputEventFetcher default. -> an InputEventFetcher It seems to work like a charm, doesn't that mean that VM IS SIGNALLING the inputSemaphore? Nicolas

April 20, 2009

[Pharo-project] Kernel Branch Name (was: Delays Semaphores and Processes)

by Lukas Renggli

> does it make sense if I load kernel-nice.renggli.300 I am enjoying to see these nice.renggli branch names everywhere, but maybe sometime this tag should be removed ;-) Lukas -- Lukas Renggli http://www.lukas-renggli.ch

April 20, 2009

Re: [Pharo-project] Delays Semaphores and Processes

by StÃ©phane Ducasse

nicolas here is what I'm planning to do: 1- Delay startTimerEventLoop. 2- Merge your pakcage 300 3- publish a new script and package with Delay startTimerEventLoop. Do you think that this will work? Stf

April 20, 2009

Re: [Pharo-project] Lots of characters lost while typing in Unix

by Damien Cassou

On Mon, Apr 20, 2009 at 6:39 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Well, its all about backward compatibility. > Sure, if Pharo ships with only newest VM, then there no need in having > these workarounds. Pharo won't work on old VMs because of closures. -- Damien Cassou http://damiencassou.seasidehosting.st

April 20, 2009

Re: [Pharo-project] Delays Semaphores and Processes

by StÃ©phane Ducasse

nicolas does it make sense if I load kernel-nice.renggli.300 then generate a new package that will be loaded using a similar script than yours? The problem is that I should merge with the changes done by mike. Stef On Apr 20, 2009, at 10:37 AM, Nicolas Cellier wrote: > I consider it is ready, see my last mail for instructions > > Nicolas > > 2009/4/20 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> Ok let me know when this is ready and I can integrate it. >> >> Stef >> >> On Apr 19, 2009, at 9:11 PM, Nicolas Cellier wrote: >> >>> OK, I checked that mantis 6576 is superseded by 7321. >>> >>> To install DelayCleanup.1.cs it is necessary to write a ScriptLoader >>> script like: >>> script363 >>> Delay startTimerEventLoop. >>> (self buildConfigurationMapFor: >>> #('Kernel-nice.renggli.300.mcz')) load >>> >>> Now, last thing to fix is remove SmallInteger maxVal//2 protection >>> and test. >>> >>> 2009/4/19 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >>>> Andreas answered that the SmallInteger limit is obsolete since >>>> http://bugs.squeak.org/view.php?id=6576 which was included in 3.10 >>>> >>>> So I will check that mantis 6576+7321, and change the >>>> DelayTests>>#testBounds >>>> >>>> Then only the PREAMBLE problem will remain. >>>> But I see this preamble can simply go in a ScriptLoader script. >>>> >>>> 2009/4/19 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >>>>> I took a look at http://bugs.squeak.org/view.php?id=7321 and >>>>> http://code.google.com/p/pharo/issues/detail?id=688 >>>>> >>>>> I started publishing PharoInbox/SLICE-DelayFixFromMantis7321-nice >>>>> to >>>>> integrate Andreas' changes. >>>>> >>>>> Now I did integrate all but DelayCleanup.1.cs >>>>> This change set does cure the failing testSemaphore in Pharo, but >>>>> has >>>>> two problems: >>>>> 1) It requires a preamble, and I don't know how they are handled >>>>> in Monticello >>>>> 2) It probably does not include change about LargeInteger delays >>>>> included in 3.9 >>>>> (Dave kindly pointed me to http://bugs.squeak.org/view.php? >>>>> id=854) >>>>> 3) it makes DelayTests>>#testBounds fail >>>>> >>>>> >>>>> I think that the limit of (SmallInteger maxVal//2) is not >>>>> necessary... >>>>> if LargeInteger delay fix is in the image. >>>>> I can try to fix 2) mixing Andreas and Tim fixes. >>>>> What about 1) ? >>>>> >>>> >>> >>> _______________________________________________ >>> 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 >

April 20, 2009

Re: [Pharo-project] Lots of characters lost while typing in Unix

by Igor Stasenko

2009/4/20 Michael Rueger <m.rueger(a)acm.org>: > On Mon, Apr 20, 2009 at 5:58 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> 2009/4/20 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>> Would a platform specific code or infrastructure help there? >>> >> >> There should be some kind of detection algorythm , which can switch >> between polling and waiting on input semaphore. >> My proposal is to change the primitive (primInterruptSemaphore: >> aSemaphore ) to return boolean value, showing that input semaphore >> signaling is available. > > I disagree, changing the VM and still not fixing it is not really an option. > If I understood Andreas correctly the signalling is not hard to > implement and then we could abandon polling altogether. > Well, its all about backward compatibility. Sure, if Pharo ships with only newest VM, then there no need in having these workarounds. > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

April 20, 2009

Re: [Pharo-project] Lots of characters lost while typing in Unix

by Michael Rueger

On Mon, Apr 20, 2009 at 5:58 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > 2009/4/20 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> Would a platform specific code or infrastructure help there? >> > > There should be some kind of detection algorythm , which can switch > between polling and waiting on input semaphore. > My proposal is to change the primitive (primInterruptSemaphore: > aSemaphore ) to return boolean value, showing that input semaphore > signaling is available. I disagree, changing the VM and still not fixing it is not really an option. If I understood Andreas correctly the signalling is not hard to implement and then we could abandon polling altogether. Michael

April 20, 2009

Re: [Pharo-project] Some bugs with the last version of pharo (10281) and pharo-dev (10284)

by Michael Rueger

On Mon, Apr 20, 2009 at 5:52 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > Strange. Cut&Paste works perfectly for me. I use Pharo0.1Core-10281cl > and Squeak 4.0.1beta1U it's broken by the new event sensor stuff in 284 Michael

April 20, 2009

[Pharo-project] [ANN] 10286 Fixing Events

by StÃ©phane Ducasse

Thanks mike. Now I will do the delay fixes and some others of mine. Stef

April 20, 2009