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

[Pharo-project] Pharo windows hanging ...
by stepken April 23, 2009

April 23, 2009

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

7 8

[Pharo-project] Fwd: [vwnc] Spelling Mistakes
by Torsten Bergmann April 23, 2009

April 23, 2009

Maybe the iSpell dictionaries can help here: http://ftp.osuosl.org/pub/openoffice/contrib/dictionaries/ Bye Torsten BTW: they were also used in the dynamic language shootout - were the winning entry was done in Smalltalk (http://www.sigs-datacom.de/sd/kongresse/oop_2008/index.php?cat=dls_competit…) -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss fÃ¼r nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a

3 2

[Pharo-project] Fwd: [vwnc] Spelling Mistakes
by StÃ©phane Ducasse April 23, 2009

April 23, 2009

Sounds quite cool Begin forwarded message: > From: Runar Jordahl <runar.jordahl(a)gmail.com> > Date: April 23, 2009 10:51:44 AM CEDT > To: VWNC List NC <vwnc(a)cs.uiuc.edu> > Subject: [vwnc] Spelling Mistakes > > I ran a quick test through bundle âBase VisualWorksâ (in 7.6) > extracting all words in the source code. Afterwards I remove all > American English words from the result. I end up with 2089 possible > misspelled words. > > Not all words in the resulting list are misspellings, but just quickly > considering the ones starting with âaâ I find these spelling mistakes: > > abillity > absoute > abstact > accellerator > acception > accesss > accomodate > accomodates > accross > acess > acheived > additons > adust > aegument > allready > allways > alorithms > alway > ambigious > ambigous > ammount > andreas > anonymus > anouncement > answser > anwer > anwser > appeance > appearence > approiate > appropiate > appropiated > approriate > aprpopriate > aribtrary > arithmetiv > arround > asnwers > aspected > assignement > assocation > assoicated > atend > attibutes > attributes > atttempting > > Cincom should run spell check on all code they produce. We do this in > our project by using unit tests. It picks up a lot of mistakes, and > requires little effort. When a test fails, you either need to add a > new word to the project-specific word-list, or correct a spelling > mistake. I will try to provide some details on our approach later on. > > Attached is the full list of words found in bundle âBase VisualWorksâ > excluding known American English words. Just copy the list into Word, > turn on spell checking, and browse for words marked with red > underline. > > Kind regards > Runar Jordahl > _______________________________________________ > vwnc mailing list > vwnc(a)cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

1 0

[Pharo-project] FFI and Pharo
by Alexandre Bergel April 23, 2009

April 23, 2009

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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

4 6

[Pharo-project] Closure simulation errors
by Nicolas Cellier April 23, 2009

April 23, 2009

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...

2 4

[Pharo-project] Hack to make mac menus work in post pharo0.1-10284dev09.04.4
by John M McIntosh April 23, 2009

April 23, 2009

Ok Michael asked er, where is it broken this morning. So as he is making the official fix I'll supply a hack so that people don't loose their minds over the issue. The offical fix will override all this, but it will get mac users back on track this morning. First of all you need to do InputEventSensor startup so the class variables get initialized, the usual case of "sure my startup class method runs, doesn't it?" Add this method InputEventSensor>>processMenuEvent: evt | handler localCopyOfEvt | localCopyOfEvt := evt clone. handler := (HostSystemMenus defaultMenuBarForWindowIndex: (localCopyOfEvt at: 8)) getHandlerForMenu: (localCopyOfEvt at: 3) item: (localCopyOfEvt at: 4). [[handler handler value: localCopyOfEvt] ifError: [:err :rcvr | ]] forkAt: Processor activePriority. Then alter processMouseEvent: so that it checks for EventTypeMenu types InputEventSensor>>processMouseEvent: evt "process a mouse event, updating InputSensor state" (evt at: 1) = EventTypeMenu ifTrue: [self processMenuEvent: evt. nil]. "Check if it is a mouse event" (evt at: 1) = EventTypeMouse ifFalse: [^evt]. "Update state for polling calls" mousePosition := (evt at: 3) @ (evt at: 4). modifiers := evt at: 6. "Map button state depending on meta keys pressed" mouseButtons := evt at: 5. "Return the event so we can use this method inline in peek and next" ^evt -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

6 15

[Pharo-project] Call Graph Optimization in PHARO?
by stepken April 23, 2009

April 23, 2009

Hi! Before that refactoring and traits implementation stuff did you do any Call Graph Optimization? I mean, in Smalltalk, especially Squeak as being a 'reflective' language this should be done first to minimize cross side incompatiblity effects with older squeak packages, which happen to appear all the time. regards, Guido Stepken

1 0

Re: [Pharo-project] Pharo windows hanging ...
by stepken April 23, 2009

April 23, 2009

Hi, Igor! I've got a *brand new* design idea for PHARO ;-) All events (keyboard, mouse, network etc.) should be read by a separate process, which i call ... hmmmm ... "event dispatcher". Brilliant name, isn't it? That one reads the event from the operating system, puts it into a per-windowgroup "event-queue", and notifies the "view process" or "network process" about the arrival of the event. That one sits on a semaphore, waiting for the arrival. regards, Guido Stepken

2 1

[Pharo-project] Swapping mouse buttons on 10289
by Janko MivÅ¡ek April 22, 2009

April 22, 2009

Hi guys, I just loaded the newest pharo-dev, together with Exupery VM from link on pharo website but I cannot swap the mouse button on preferences at all. If I click swapMouseButtons enabled and save, right mouse still doesn't work. What can be the problem? I'm on openSuse 11.1, KDE and so far swapping the mouse works both on the squeak and previous Pharo images. Is there some problem with new VM? Best regards Janko -- Janko MivÅ¡ek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si

3 3

[Pharo-project] Pharo windows unresponsive while busy?
by stepken April 22, 2009

April 22, 2009

Hi! When i paste that stuff into workspace, let it run, all other open windows tasks freeze. (Windows XP, newest VM, newest Pharo patches) That makes Pharo pretty unusable for programming, testing, debugging ... I think, there are still some serious problems hidden (design problem?) downunder, which have to be solved ... regards, Guido Stepken packages := PackageOrganizer default packages select: [ :each | #('Collections' 'Kernel') includes: each packageName ]. browserEnvironment := SelectorEnvironment new label: 'Seaside Methods'. packages do: [ :package | package methods do: [ :method | browserEnvironment addClass: method actualClass selector: method methodSymbol ] ]. browserEnvironment open

2 1