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

Re: [Pharo-project] Bug in OCompletion

by Mariano Martinez Peck

This bug has been closed but I can still reproduce it in 10479. Can someone please test it and tell me if I am not the only one. Thanks mariano On Wed, Sep 23, 2009 at 4:29 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > > Begin forwarded message: > > *From: *Mariano Martinez Peck <marianopeck(a)gmail.com> > *Date: *September 23, 2009 8:20:40 PM CEDT > *To: *Pharo Development <pharo-project(a)lists.gforge.inria.fr> > *Subject: **[Pharo-project] Bug in OCompletion* > *Reply-To: *Pharo-project(a)lists.gforge.inria.fr > > http://code.google.com/p/pharo/issues/detail?id=1236 > > Tested with OBSystemBrowserAdaptor in pharo1.0-10451-BETAdev09.09.3 on > Windows. > > To reproduce: > > 1) Open a System Browser > 2) Create a new class. When you do this, when you are changing > "#NameOfSubclass" to "#YourClass", after doing this press the down arrow > key > 3) An empty pop up will be brought and the keyboard won't respond. To fix > this, you must press "Esc" key. > > > Best, > > Mariano > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > >

Oct. 18, 2009

Re: [Pharo-project] Input problems

by StÃ©phane Ducasse

did you executed InputEventSensor default initialize Stef On Oct 18, 2009, at 8:15 PM, Schwab,Wilhelm K wrote: > This time I copied the entire directory, filed in the change set and > saved/quit/re-opened. It really does not make any difference that I > can detect. Please keep at it. I will gladly try anything you > think improves the situation. > > Bill > > > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo- > project-bounces(a)lists.gforge.inria.fr] On Behalf Of Michael Rueger > Sent: Sunday, October 18, 2009 10:19 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Input problems > > Damien Cassou wrote: >> 2009/10/17 Michael Rueger <m.rueger(a)acm.org>: > >>> Please let me know if after filing in the change set the issues are >>> fixed, less often or unchanged. >> >> http://code.google.com/p/pharo/issues/detail?id=1323 > > OK, turns out the change set didn't actually do anything, so for > Lukas the placebo effect worked ;-) Just shows how ephemeral the > problem can be. > Attached an updated change set, that actually switches to > SharedQueue2. > > If there is someone who can reasonably reliably reproduce the > missing character problem, please contact me so I can work with you > directly on instrumenting a test image. > > Thanks > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 18, 2009

Re: [Pharo-project] Input problems

by Schwab,Wilhelm K

This time I copied the entire directory, filed in the change set and saved/quit/re-opened. It really does not make any difference that I can detect. Please keep at it. I will gladly try anything you think improves the situation. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Michael Rueger Sent: Sunday, October 18, 2009 10:19 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Input problems Damien Cassou wrote: > 2009/10/17 Michael Rueger <m.rueger(a)acm.org>: >> Please let me know if after filing in the change set the issues are >> fixed, less often or unchanged. > > http://code.google.com/p/pharo/issues/detail?id=1323 OK, turns out the change set didn't actually do anything, so for Lukas the placebo effect worked ;-) Just shows how ephemeral the problem can be. Attached an updated change set, that actually switches to SharedQueue2. If there is someone who can reasonably reliably reproduce the missing character problem, please contact me so I can work with you directly on instrumenting a test image. Thanks Michael

Oct. 18, 2009

[Pharo-project] [update] 10481

by Adrian Lienhard

10481 ----- - Issue 1327: TestRunner should set dummy author when running tests - Issue 1310: Make all tests green (work in progress) ___________________ http://www.adrian-lienhard.ch/

Oct. 18, 2009

Re: [Pharo-project] Input problems

by Damien Cassou

2009/10/18 Michael Rueger <m.rueger(a)acm.org>: >> http://code.google.com/p/pharo/issues/detail?id=1323 > > OK, turns out the change set didn't actually do anything, so for Lukas the > placebo effect worked ;-) > Just shows how ephemeral the problem can be. > Attached an updated change set, that actually switches to SharedQueue2. > > If there is someone who can reasonably reliably reproduce the missing > character problem, please contact me so I can work with you directly on > instrumenting a test image. I've updated the tracker. Could you please continue the discussion there so that things don't get lost? -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Oct. 18, 2009

Re: [Pharo-project] Input problems

by Lukas Renggli

>>> Please let me know if after filing in the change set the issues are >>> fixed, >>> less often or unchanged. >> >> http://code.google.com/p/pharo/issues/detail?id=1323 > > OK, turns out the change set didn't actually do anything, so for Lukas the > placebo effect worked ;-) > Just shows how ephemeral the problem can be. Of course I evaluated "InputEventSensor default initialize" manually. I haven't seen the problem again afterwards. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Oct. 18, 2009

[Pharo-project] [update] 10478

by Adrian Lienhard

!! We backtracked and removed the 1.1alpha branch again (we implement a more clever infrastructure for the update mechanism). Please take an image <=10477 and update. Delete existing images with version 10478. !! Issue 1310: Make all tests green (work in progress) Issue 818: MethodContext tempNames wrong implementation or usage for Closure Issue 1270: ClassBuilder wrong class format validation Issue 1317: Add MethodHighlightingTests back Tests for ImageSegment (including support for analyzing a segment) Adrian ___________________ http://www.adrian-lienhard.ch/

Oct. 18, 2009

Re: [Pharo-project] Input problems

by Michael Rueger

Damien Cassou wrote: > 2009/10/17 Michael Rueger <m.rueger(a)acm.org>: >> Please let me know if after filing in the change set the issues are fixed, >> less often or unchanged. > > http://code.google.com/p/pharo/issues/detail?id=1323 OK, turns out the change set didn't actually do anything, so for Lukas the placebo effect worked ;-) Just shows how ephemeral the problem can be. Attached an updated change set, that actually switches to SharedQueue2. If there is someone who can reasonably reliably reproduce the missing character problem, please contact me so I can work with you directly on instrumenting a test image. Thanks Michael

Oct. 18, 2009

[Pharo-project] New Pharo based on core 10477

by Damien Cassou

http://pharo-project.org/pharo-download -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Oct. 18, 2009

[Pharo-project] [update] 10478: advance to 1.1 or stay at 1.0

by Marcus Denker

Hi, There is now an update that asks to advance to 1.1 or stay at 1.0 If you stay at 1.0, you will get the following changes up to the release of 1.0 If yu advance to 1.1, you get all 1.1 unstable changes (which of course will include all the 1.0 ones, too). Marcus -- Marcus Denker -- marcus(a)2denker.de http://www.2denker.de 2denker UG (haftungsbeschrÃ¤nkt) Sitz KÃ¶ln Amtsgericht - Registergericht - KÃ¶ln, HRB 65065 GeschÃ¤ftsfÃ¼hrer: Christian Denker und Dr. Marcus Denker

Oct. 18, 2009