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

Re: [Pharo-project] Pharo windows hanging ...

by StÃ©phane Ducasse

You are not forced to use pharo and you can send code once you signed the license agreement. talking is easier than doing. Stef (a Doer). > Igor Stasenko wrote: > >> This is because all do-its executed in process, which responsible >> from >> handling UI events. >> To avoid 'hanging' you can just do like following: >> [ do what you need ] fork. > > Oh, yes! > > Then i commanded a Full GC. I had to clean some 16 MByte Smalltalk > stuff > on my Notebook. 15 Seconds I had to wait, till my keystrokes and mouse > events were accepted back again by Pharo GUI. > > Well, in the meantime, the seaside process was unresponsive. > > Ok, no real problem. Customers can wait and I have my coffee > breaks ;-) > > World Wide Wait with Seaside Servers on Pharo ... > > Sorry, no access to The Salty Spitoon .... (not yet) ;-) > > Have fun, Guido Stepken > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 23, 2009

Re: [Pharo-project] Going Alpha

by Serge Stinckwich

On Thu, Apr 23, 2009 at 1:30 AM, Marcus Denker <denker(a)acm.org> wrote: > > On 22.04.2009, at 05:17, Adrian Lienhard wrote: > >> >> On Apr 22, 2009, at 11:04 , StÃ©phane Ducasse wrote: >> >>> >>>> On Tue, Apr 21, 2009 at 11:20 PM, StÃ©phane Ducasse >>>> <stephane.ducasse(a)inria.fr> wrote: >>>>> Ok for me . >>>>> Let us now target beta. >>>> >>>> Ok. What's the plan to go MIT? >>> >>> this is still there but who will do it? >> >> You did a great job in the last weeks! >> > > indeed! > >> I'll try to find again a bit more time for Pharo. Marcus also said he >> will have more time again. > > Yes, I will definitely be more active again soon. It's interesting how > much cognitive bandwith is occupied by a move to another culture... I experience the same thing here but it's wonderfull in the end ! -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

April 23, 2009

Re: [Pharo-project] Going Alpha

by StÃ©phane Ducasse

do it We need more regression tools. Stef On Apr 23, 2009, at 1:27 AM, Michael Roberts wrote: > http://code.google.com/p/pharo/wiki/BaselineTestResults > > This is just a first version I have published. Comments welcome. > > I have some crude code to produce the wiki syntax from the image. Does > anyone mind if I add behaviour to TestRunner & TestResult to do this > or should I create a separate PharoWikiExporter class and integrate > it? Also it would be convenient for a TestCase to be sortable. Any > thoughts on that? I have not made TestCase understand <= yet but it > seems verbose not to do so. > > thanks, > > Mike > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 23, 2009

Re: [Pharo-project] Going Alpha

by StÃ©phane Ducasse

> > indeed! > >> I'll try to find again a bit more time for Pharo. Marcus also said he >> will have more time again. > > Yes, I will definitely be more active again soon. It's interesting how > much cognitive bandwith is occupied by a move to another culture... oh yes! excellent experience :) Stef

April 23, 2009

Re: [Pharo-project] Going Alpha

by StÃ©phane Ducasse

I agree. But we took the decision to harvest the fix of events because they could rot dramatically. Then removing bad code is also important for the relicensing. The less etoy bookmoprh the less relicensing we have. > I have been running the sunits recently for each update or published > build. It would be great if more people could do this so that we can > seriously get the error list down. Also we should try not to push out > updates if they increase the error number. To make comparison easier I > was going to publish the baseline results on the wiki to make it easy > to see progress. I got stuck when recently the tests did not complete > :-) but I think this is a good example of why we should focus in this > area. > Thanks mike

April 23, 2009

Re: [Pharo-project] Input Sensor fix

by Michael Rueger

On Thu, Apr 23, 2009 at 10:12 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > mickael I loaded the kernel 304 but copy and paste does not work > Am I missing an initialize? > After loading the package you need to execute > InputEventSensor installPollingEventSensorFramework Michael

April 23, 2009

Re: [Pharo-project] Input Sensor fix

by StÃ©phane Ducasse

mickael I loaded the kernel 304 but copy and paste does not work Am I missing an initialize? On Apr 22, 2009, at 9:48 PM, Michael Rueger wrote: > Mariano Martinez Peck wrote: > >> I tried this and: >> >> - Select text with shift works ok. >> - Short cuts are with alt + x , alt + v instead of ctrl + x or ctrl >> + v >> - Swap mouse button doesn't work. > > Thanks for testing! > OK, so another round of digging through crap... > > This stuff HAS TO GO... It's piled crap on history on crap... > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 23, 2009

Re: [Pharo-project] Input Sensor fix

by StÃ©phane Ducasse

so I will integrate now. because this is important :) Stef On Apr 22, 2009, at 1:42 PM, Michael Rueger wrote: > Hi all, > > in the Pharo inbox there is now > Kernel-michael_rueger.renggli.304 > > integrated John's Mac menu fixes > fixed problems with shift cursor > fixed and cleaned up input sensor/fetcher installation > > After loading the package you need to execute > InputEventSensor installPollingEventSensorFramework > > > Hopefully this will fix all the recent issues around input events. > > Thanks to all contributors and testers! > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 23, 2009

Re: [Pharo-project] Closure simulation errors

by StÃ©phane Ducasse

Thanks I will do an integration later today. Now I have to work on more boring stuff. On Apr 22, 2009, at 9:17 PM, Nicolas Cellier wrote: > As a follow-up, I missed one important change in 'Closure Usage > Fixes.1.cs' > ContextPart>>#runSimulated:contextAtEachStep: > > Load PharoInbox/Kernel-nice.renggli.305 to repair that. > Small progress: the ClosureCompilerTest errors now turned into > failures... > Now, we have to find another mismatch somewhere... > I think it is in Encoder and related to > http://code.google.com/p/pharo/issues/detail?id=743 > > Nicolas > > 2009/4/21 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >> Since I'm not sure it's the same issue, you have two... >> >> http://code.google.com/p/pharo/issues/detail?id=761 >> http://code.google.com/p/pharo/issues/detail?id=762 >> >> 2009/4/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>> can you add an issue on the bugtracker? >>> >>> On Apr 21, 2009, at 1:09 AM, Nicolas Cellier wrote: >>> >>>> You certainly noticed a lot of Closure related tests fail. >>>> A few because of unavailable BlockContext API in BlockClosure... >>>> (most >>>> are fixed yet) >>>> But mainly because of tests messing with: >>>> >>>> MethodContext>>#runSimulated:contextAtEachStep: >>>> >>>> I think something is broken there... One missing or not up to date >>>> change from Eliot probably. >>>> >>>> Also there is a problem in the debugger: when halted in a Closure, >>>> executing restart then proceed won't restart correclty: >>>> Example: >>>> 1) Execute this : >>>> (ScriptLoader new buildConfigurationMapFor: #('foobar.blast')) >>>> load >>>> 2) Open the debugger (click debug) >>>> 3) select top but one context >>>> [] in ScriptLoader>>buildConfigurationMapFor: >>>> 4) click restart, then proceed >>>> >>>> You get Character doesNotUnderstand: #encodeForHttp >>>> a real mess, as if evaluating the code in wrong context... >>>> >>>> _______________________________________________ >>>> 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 23, 2009

Re: [Pharo-project] FFI and Pharo

by StÃ©phane Ducasse

can you add that to the wiki :) Stef On Apr 22, 2009, at 3:34 PM, Mariano Martinez Peck wrote: > Hi! > > Smalltalk listLoadedModules > SmalltalkImage current listLoadedModules > > To load FFI package: > > ScriptLoader loadFFI. > > Cheers, > > Mariano > > On Wed, Apr 22, 2009 at 6:42 AM, Alexandre Bergel <Alexandre.Bergel(a)inria.fr > > wrote: > Hi All, > > I was wondering whether the FFI is included in the Pharo VM. Is there > an easy way to check this? > > Regards, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > 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 23, 2009