- Pharo-dev - lists.pharo.org

Re: [Pharo-project] New sensor code

by Igor Stasenko

The problem with your .cs that it can't work on windoze VM because it never signals input semaphore :( eventLoop "Fetch pending raw events from the VM. This method is run at high priority." [true] whileTrue: [ | eventBuffer type | inputSemaphore wait. <<<<< will stall here forever. An old EventSensor periodically polls events manually at some predefined period. As temporary measure, i suggest to put "self waitForInput" instead of "inputSemaphore wait" to make it easy to switch between old/new versions without intruding into the rest of code. 2008/11/22 Michael Rueger <m.rueger(a)acm.org>: > >> The event fetcher fetches events from the even and currently still > > from the VM that is > > _______________________________________________ > 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.

Nov. 22, 2008

Re: [Pharo-project] New sensor code

by Michael Rueger

> The event fetcher fetches events from the even and currently still from the VM that is

Nov. 22, 2008

[Pharo-project] New sensor code

by Michael Rueger

Hi all, finally got it. Turned out to be related to the host window/menu work, the window index slot needed to be set to 1 if 0. Sigh... Attached is a change set that installs the new logic into a recent Pharo image. I'm not sure if and how we can get the install into a package load, but this version is for the adventurous types anyways :-) A few remarks about the new sensor architecture (need to put this into the class comments). First what's not changed, which is the morphic side. HandMorph still polls for nextEvent and also all old polling methods are still supported and heavily used in the image. Basically the input event handling has been split into two parts: one event fetcher and event handlers. The event fetcher fetches events from the even and currently still polls. Next step will be to get the input semaphore signaling working. The event fetcher then signals the event to all registered event handlers. In the current version there are two: the new morphic sensor and the user interrupt handler. Events currently are handled multiple times (rather their copies), we might need to change that later. There needs to be some work done on how the user interrupt handler works, I had some problems with launching the debugger, but that might have been a problem in my development image. It would be helpful though, if the VM would provide information about the interrupted process as it does (or should do?) for the low space watcher. So much for now, questions welcome and happy testing :-) Michael

Nov. 22, 2008

Re: [Pharo-project] Event rewrite

by Michael Rueger

gets weirder... mouse move events work (buttons react to mouse over) typing in the debugger works, but no mouse clicks... Michael

Nov. 21, 2008

Re: [Pharo-project] SUnit: history support and OB icons

by Simon Denier

On 21 nov. 08, at 13:24, Simon Denier wrote: > > On 21 nov. 08, at 10:17, StÃ©phane Ducasse wrote: > >> I have the not run green/red icons >> but not the green ones when the tests are run. >> Even if once it worked because I saw it. >> Stef > > What Stef is talking about is the ability to run tests in the > browser with the cmd-t shortcut. Indeed, test status is not updated > in this case. Test status are only updated when ran through the > *TestRunner*. But, it makes perfect sense that running tests through > the browser should update the status. I have a very simple small patch to run tests with history from the browser (one method send!). It works when running tests on a package, a class or category. The running behavior when a single test method runs is different, so there is a different patch, however I am not sure we want it: running only one method will erase the previous test result for the class, so you will have to run all tests again to see their result (well the same is true if you only run a protocol and there are tests in different protocols anyway, but this is a rarity) I will try to check why test classes ask for your name. > > > I can work out something. Any hint about how it works in OB? > > > PS: I have been bothered by the password box being asked twice too. > Worse, when I load both Polymorph and my slice, if I try to move the > cursor to type in my name, it produces a new box, see screenshot. Be > aware. > > <Picture 1.png> > >> >> >> On Nov 20, 2008, at 11:00 PM, David RÃ¶thlisberger wrote: >> >>> >>>> Now I do not understand since when I run the tests the icons do >>>> not change. >>> Strange. So you always get the not run icon (circle with green and >>> red)? >>> For me this is not the case, the icons do change. Can you check >>> whether it saved a history in the class variable of TestCase? >>> >>> david >>>> Stef >>>> >>>> On Nov 20, 2008, at 8:17 PM, David RÃ¶thlisberger wrote: >>>> >>>>> >>>>>> I loaded the fix of John for the menu >>>>>> and the changes for SUnit icons and my image freshes when I >>>>>> open the Package browser and run the tests >>>>>> in 10162 >>>>> >>>>> which tests? All tests? >>>>> >>>>> David >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > Simon > > > -- Simon

Nov. 21, 2008

Re: [Pharo-project] isTransparent

by Igor Stasenko

One more example to illustrate things: drawOn: aCanvas "Put the painting on the display" color isTransparent ifFalse: [ aCanvas fillRectangle: bounds color: color ]. paintingForm ifNotNil: [ aCanvas paintImage: paintingForm at: bounds origin]. could look like: drawOn: aCanvas "Put the painting on the display" color fillRectangle: bounds on: aCanvas paintingForm ifNotNil: [ aCanvas paintImage: paintingForm at: bounds origin]. See the difference? In latter case, a color could be any object, and the way how it fills the requested area could be anything. While in former case, it is assumed that color is instance of Color and have some notion about transparency. -- Best regards, Igor Stasenko AKA sig.

Nov. 21, 2008

Re: [Pharo-project] isTransparent

by Igor Stasenko

2008/11/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > If you want to have fun > > do > > Object new setHaltOnce > > redefine > > Object>>isTransparent > self haltOnce. > Beeper beep. > ^ false > > > I found a kind of fix by initializing correctly SimpleBorder (my fix is not > totally convincing yet since it crashed the image). > SimpleBorder is used in BorderedSubpaneDividerMorph > > Now what is amazing to me is the number of time isTransparent is invoked > on Object when just typing text, I think that there is bogus there. > > If one UI expert can have a look this would be great. > There are many senders of isTransparent . Much of uses showing a conceptually wrong usage of colors. Maybe its faster to write: fillStyle isTransparent ifTrue: [^ self ]. instead of: fillStyle fill: someArea. and then in #fill: it can check if no fill necessary. That's one of the moves which we discussed with Gary, that it is up to fill style to determine how to fill an area. It should play role a full object with own behavior , not just holder of static information like color & gradient. But currently, if you look at uses of colors and gradients - they used as value holders, and this is why all those #isTransparent #isTransulent, instead of simply dispatching into this object and let it decide how to fill / draw things and with what color. > Stef > > _______________________________________________ > 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.

Nov. 21, 2008

Re: [Pharo-project] Event rewrite

by Michael Rueger

Michael Rueger wrote: > Hi all, > > after wrapping the current implementation which I test and packaged in > the experimental polymorph image I tried to install it in the newest > Pharo image and it doesn't work (freezes). It actually doesn't freeze but seems to hang in a delay in WorldState... alt-. pops a debugger, but so input events are fetched from the VM, but Morphic doesn's seem to pick them up anymore... OK, more hunting... Michael

Nov. 21, 2008

Re: [Pharo-project] Event rewrite

by Igor Stasenko

2008/11/22 Michael Rueger <m.rueger(a)acm.org>: > Hi all, > > after wrapping the current implementation which I test and packaged in the > experimental polymorph image I tried to install it in the newest Pharo image > and it doesn't work (freezes). > > Anyone a suggestion what might have changed in the area of event handling or > process management? I started going through the different classes but maybe > somebody has a hint where to look? > There some problems reported recently with class defs/traits. Maybe you were unlucky with it :) > As reward there will be no more EventSensor and EventTicklerProcess :-) > Awaiting release! > Thanks > > 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.

Nov. 21, 2008

[Pharo-project] Event rewrite

by Michael Rueger

Hi all, after wrapping the current implementation which I test and packaged in the experimental polymorph image I tried to install it in the newest Pharo image and it doesn't work (freezes). Anyone a suggestion what might have changed in the area of event handling or process management? I started going through the different classes but maybe somebody has a hint where to look? As reward there will be no more EventSensor and EventTicklerProcess :-) Thanks Michael

Nov. 21, 2008