- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Opening World Tools via Shortcuts

by Camille Teruel

On OSX you have (on Windows and Linux you might change Cmd to Ctrl or Alt I never remember): - Monticello: Cmd+O,P - Workspace: Cmd+O,W - Browser: Cmd+O,B - Transcript: Cmd+O,T - Settings: Cmd+O,S - Test Runner: Cmd+O,U AFAIK there is no shortcut for the Finder, we can assign it Cmd+O,F. On 25 juil. 2014, at 19:45, kilon alios <kilon.alios(a)gmail.com> wrote: > Is it possible to open the tools in world menu using shortcuts ? > > I am interested especially for Workspace , Browser (without selecting a message) , Finder , Monticello and of course all the others. > > you can answer the questions also here -> http://stackoverflow.com/questions/24943081/bypassing-world-menu-with-short…

July 25, 2014

Re: [Pharo-dev] Returning the source of a class as a string

by Thierry Goubier

Le 25/07/2014 19:47, kilon alios a Ã©crit : > > I want to find the source of a Class and its methods (including all > variables too, local , instance, class , class instance etc) and > return them as a string or a collection of strings. > For the class, use aClass definition. For a method use CompiledMethod>>sourceCode; you can also ask the class for a selector as in: (aClass compiledMethodAt: self selector) sourceCode (works also if aClass is the meta side) > > I have found MethodNode>>sourceText and CompiledMethod>>sourceCode but > I have no clue how to send these messages or if they are the messages > I am looking for. > > Also any pointers as to how to navigate the Pharo syntax by code using > something like AST would be greatly appreciated :) > > http://stackoverflow.com/questions/24961556/how-to-ask-an-object-to-return-… > ast := RBParser parseMethod: aTarget text asString onError: [ :msg :pos | ^ self ]. ast doSemanticAnalysisIn: self sourceClass. (you need the semantic analysis to have the variable bindings) To navigate the parse tree you either write a visitor or use existing search structures and extend nodes, as is done in SmartSuggestions. SmartSuggestions is probably an interesting place to look for that. The code above is from an ancestor to smart suggestion. Then I have some code which does a visit + rewrite over an AST tree (a code tracing tool). Refactoring also does that (all things RB). > > Would it make more sense to use something like PettitParser ? > Maybe. But probably not, RBParser is good enough. Thierry

July 25, 2014

Re: [Pharo-dev] Metarepo Pharo 4.0 access

by Maximiliano Taborda

Hi. I need access too. Could you give it to me? My username is: maxi. Thanks. Regards. Maxi 2014-07-25 12:30 GMT-03:00 Marcus Denker <marcus.denker(a)inria.fr>: > > On 25 Jul 2014, at 17:06, Serge Stinckwich <serge.stinckwich(a)gmail.com> > wrote: > > > Can someone give me access to the metarepo for Pharo 4.0 ? > > done > > >

July 25, 2014

Returning the source of a class as a string

by kilon alios

I want to find the source of a Class and its methods (including all variables too, local , instance, class , class instance etc) and return them as a string or a collection of strings. I have found MethodNode>>sourceText and CompiledMethod>>sourceCode but I have no clue how to send these messages or if they are the messages I am looking for. Also any pointers as to how to navigate the Pharo syntax by code using something like AST would be greatly appreciated :) http://stackoverflow.com/questions/24961556/how-to-ask-an-object-to-return-… Would it make more sense to use something like PettitParser ?

July 25, 2014

Opening World Tools via Shortcuts

by kilon alios

Is it possible to open the tools in world menu using shortcuts ? I am interested especially for Workspace , Browser (without selecting a message) , Finder , Monticello and of course all the others. you can answer the questions also here -> http://stackoverflow.com/questions/24943081/bypassing-world-menu-with-short…

July 25, 2014

Re: [Pharo-dev] [Vm-dev] Delay machinery (was Re: Suspending a Process)

by Eliot Miranda

Hi Ben, On Fri, Jul 25, 2014 at 7:56 AM, Ben Coman <btc(a)openinworld.com> wrote: > > Over the last few days I have been looking deeper into the image locking > when suspending a process. It is an interesting rabbit hole [1] that leads > to pondering the Delay machinery, that leads to some VM questions. > > When pressing the interrupt key it seems to always opens the debugger > with the following call stack. > Semaphore>>critical: 'self wait' > BlockClosure>>ensure: 'self valueNoContextSwitch' > Semaphore>>critical: 'ensure: [ caught ifTrue: [self signal]] > Delay>>schedule 'AccessProtect critical: [' > Delay>>wait 'self schedule' > WorldState>>interCyclePause: > > I notice... > Delay class >> initialize > TimingSemaphore := (Smalltalk specialObjectsArray at: 30). > and... > Delay class >> startTimerEventLoop > TimingSemaphore := Semaphore new. > which seems incongruous that TimingSemaphore is set in differently. So > while I presume this critical stuff all works fine, just in an exotic way, > my entropy-guarding-neuron would just like confirm this is so. > The TimingSemaphore gets installed in the specialObjectsArray via primSignal: aSemaphore atMilliseconds: aSmallInteger "Signal the semaphore when the millisecond clock reaches the value of the second argument. Fail if the first argument is neither a Semaphore nor nil. Essential. See Object documentation whatIsAPrimitive." <primitive: 136> ^self primitiveFailed and from that the VM sets the nextWakeupUsecs: primitiveSignalAtMilliseconds "Cause the time semaphore, if one has been registered, to be signalled when the microsecond clock is greater than or equal to the given tick value. A tick value of zero turns off timer interrupts." | msecsObj msecs deltaMsecs sema | <var: #msecs type: #usqInt> msecsObj := self stackTop. sema := self stackValue: 1. msecs := self positive32BitValueOf: msecsObj. self successful ifTrue: [(objectMemory isSemaphoreOop: sema) ifTrue: [*objectMemory splObj: TheTimerSemaphore put: sema*. deltaMsecs := msecs - (self ioMSecs bitAnd: MillisecondClockMask). deltaMsecs < 0 ifTrue: [deltaMsecs := deltaMsecs + MillisecondClockMask + 1]. *nextWakeupUsecs := self ioUTCMicroseconds + (deltaMsecs * 1000)*. ^self pop: 2]. sema = objectMemory nilObject ifTrue: [objectMemory storePointer: TheTimerSemaphore ofObject: objectMemory specialObjectsOop withValue: objectMemory nilObject. *nextWakeupUsecs := 0*. ^self pop: 2]]. self primitiveFailFor: PrimErrBadArgument > -------------- > > In Delay class >> handleTimerEvent the comment says... > "Handle a timer event.... > -a timer signal (not explicitly specified)" > ...is that event perhaps a 'tick' generated periodically by the VM via > that item from specialObjectArray ? Or is there some other mechanism ? > Every time the VM checks for interrupts, which, in the Cog.Stack VMs is controlled by the heartbeat frequency, which defaults to 2 milliseconds, the VM checks if the current time has progressed to or beyond nextWakeupUsecs and signals the timer semaphore if so. -------------- > > [1] http://www.urbandictionary.com/define.php?term=Rabbit+Hole > and the problem here is not in the VM. So climb out and breath some fresh air ;-) cheers -ben > > > P.S. I've left the following for some initial context as I change the > subject. btw Nicolai, I confirm that my proposed fixes only work on > Windows, not Mavericks (and I haven't checked Linux). > > Nicolai Hess wrote: > > > Hi ben, thank you for looking at this. > > 2014-07-22 20:17 GMT+02:00 <btc(a)openinworld.com>: > >> I thought this might be interesting to learn, so I've gave it a go. I >> had some success at the end, but I'll give a progressive report. >> >> First I thought I'd try moving the update of StringMorph outside the >> worker-process using a Morph's #step method as follows... >> >> Morph subclass: #BackgroundWorkDisplayMorph >> instanceVariableNames: 'interProcessString stringMorph' >> classVariableNames: '' >> category: 'BenPlay' >> "---------" >> >> BackgroundWorkDisplayMorph>>initializeMorph >> self color: Color red. >> stringMorph := StringMorph new. >> self addMorphBack: stringMorph. >> self extent:(300@50). >> "---------" >> >> BackgroundWorkDisplayMorph>>newWorkerProcess >> ^[ >> | work | >> work := 0. >> [ 20 milliSeconds asDelay wait. >> work := work + 1. >> interProcessString := work asString. >> ] repeat. >> ] newProcess. >> "---------" >> >> BackgroundWorkDisplayMorph>>step >> stringMorph contents: interProcessString. >> "---------" >> >> BackgroundWorkDisplayMorph>>stepTime >> ^50 >> "---------" >> >> BackgroundWorkDisplayMorph>>initialize >> | workerProcess running | >> super initialize. >> self initializeMorph. >> >> workerProcess := self newWorkerProcess. >> running := false. >> >> self on: #mouseUp send: #value to: >> [ (running := running not) >> ifTrue: [ workerProcess resume. self color: Color green. ] >> ifFalse: [ workerProcess suspend. self color: Color red. ] >> ] >> "---------" >> >> >> >> But evaluating "BackgroundWorkDisplayMorph new openInWorld" found this >> exhibited the same problematic behavior you reported... Clicking on the >> morph worked a few times and then froze the UI until Cmd-. pressed a few >> times. >> > >> However I found the following never locked the GUI. >> >> BackgroundWorkDisplayMorph>>initialize >> "BackgroundWorkDisplayMorph new openInWorld" >> | workerProcess running | >> super initialize. >> self initializeMorph. >> >> workerProcess := self newWorkerProcess. >> running := false. >> >> [ [ (running := running not) >> ifTrue: [ workerProcess resume. self color: Color green ] >> ifFalse: [ workerProcess suspend. self color: Color red ]. >> 10 milliSeconds asDelay wait. >> ] repeat ] fork. >> "---------" >> >> > This locks the UI as well. Not every timet hough. I did this 5 times, > every time in a freshly loaded image and it happens two times. > > > >> So the problem seemed to not be with #suspend/#resume or with the shared >> variable /interProcessString/. Indeed, since in the worker thread >> /interProcessString/ is atomically assigned a copy via #asString, and the >> String never updated, I think there is no need to surround use of it with a >> critical section. >> >> The solution then was to move the "#resume/#suspend" away from the "#on: >> #mouseUp send: #value to:" as follows... >> >> BackgroundWorkDisplayMorph>>initialize >> "BackgroundWorkDisplayMorph new openInWorld" >> | workerProcess running lastRunning | >> super initialize. >> self initializeMorph. >> >> workerProcess := self newWorkerProcess. >> lastRunning := running := false. >> >> [ [ lastRunning = running ifFalse: >> [ running >> ifTrue: [ workerProcess resume ] >> ifFalse: [ workerProcess suspend ]. >> lastRunning := running. >> ]. >> 10 milliSeconds asDelay wait. >> ] repeat ] fork. >> >> self on: #mouseUp send: #value to: >> [ (running := running not) >> ifTrue: [ self color: Color green. ] >> ifFalse: [ self color: Color red. ] >> ] >> "---------" >> > > And this too :( > > > >> >> And finally remove the busy loop. >> >> BackgroundWorkDisplayMorph>>initialize >> "BackgroundWorkDisplayMorph new openInWorld" >> | workerProcess running lastRunning semaphore | >> super initialize. >> self initializeMorph. >> >> workerProcess := self newWorkerProcess. >> lastRunning := running := false. >> semaphore := Semaphore new. >> >> [ [ semaphore wait. >> running >> ifTrue: [ workerProcess resume ] >> ifFalse: [ workerProcess suspend ]. >> ] repeat ] fork. >> >> self on: #mouseUp send: #value to: >> [ (running := running not) >> ifTrue: [ self color: Color green. ] >> ifFalse: [ self color: Color red. ]. >> semaphore signal. >> ] >> "---------" >> >> > > And this locks the UI too. (Loaded the code 20 times, every time after a > fresh image start up. Two times I got a locked > ui after the first two clicks). > And I don't understand this code :) > > > >> Now I can't say how close that is to how it "should" be done. Its the >> first time I used sempahores and just what I discovered hacking around. >> But hey! it works :) >> >> cheers -ben >> >> >> >> Nicolai Hess wrote: >> >> I am still struggling with it. >> >> Any ideas? >> >> >> 2014-07-09 11:19 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: >> >>> >>> >>> >>> 2014-07-09 2:07 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >>> >>> Hi Nicolai, >>>> >>>> >>>> On Tue, Jul 8, 2014 at 7:19 AM, Nicolai Hess <nicolaihess(a)web.de> >>>> wrote: >>>> >>>>> I want to create a process doing some work and call #changed on a >>>>> Morph. >>>>> I want to start/suspend/resume or stop this process. >>>>> But sometimes, suspending the process locks the UI-Process, >>>>> and I don't know why. Did I miss something or do I have to care when >>>>> to call suspend? >>>>> >>>>> Wrapping the "morph changed" call in >>>>> UIManager default defer:[ morph changed]. >>>>> Does not change anything. >>>>> >>>>> Here is an example to reproduce it. >>>>> Create the process, >>>>> call resume, call supsend. It works, most of the time, >>>>> but sometimes, calling suspend locks the ui. >>>>> >>>>> p:=[[true] whileTrue:[ Transcript crShow: (DateAndTime now asString). >>>>> 30 milliSeconds asDelay wait]] newProcess. >>>>> >>>> p resume. >>>>> p suspend. >>>>> >>>> >>>> If you simply suspend this process at random form a user-priority >>>> process you'll never be able to damage the Delay machinery you're using, >>>> but chances are you'll suspend the process inside the critical section that >>>> Transcript uses to make itself thread-safe, and that'll lock up the >>>> Transcript. >>>> >>> >>> Thank you Eliot >>> yes I guessed it locks up the critical section, but I hoped with would >>> not happen if I the use UIManager defer call. >>> >>> >>> >>>> >>>> ThreadSafeTranscript>>nextPutAll: value >>>> accessSemaphore >>>> critical: [stream nextPutAll: value]. >>>> ^value >>>> >>>> So instead you need to use a semaphore. e.g. >>>> >>>> | p s wait | >>>> s := Semaphore new. >>>> p:=[[true] whileTrue:[wait ifTrue: [s wait]. Transcript crShow: >>>> (DateAndTime now asString). 30 milliSeconds asDelay wait]] newProcess. >>>> wait := true. >>>> 30 milliSeconds asDelay wait. >>>> wait := false. >>>> s signal >>>> >>>> etc... >>>> >>> >>> Is this a common pattern I can find in pharos classes. Or I need some >>> help understanding this. The semaphore >>> wait/signal is used instead of process resume/suspend? >>> >>> What I want is a process doing repeatly some computation, >>> calls or triggers an update on a morph, and I want to suspend and resume >>> this process. >>> >>> I would stop this discussion if someone tells me, "No your are doing it >>> wrong, go this way ..", BUT what strikes me: >>> in this example, that reproduces my problem more closely: >>> >>> |p m s running| >>> running:=false. >>> m:=Morph new color:Color red. >>> s:= StringMorph new. >>> m addMorphBack:s. >>> p:=[[true]whileTrue:[20 milliSeconds asDelay wait. s >>> contents:(DateAndTime now asString). m changed]] newProcess. >>> m on:#mouseUp send:#value to:[ >>> running ifTrue:[p suspend. m color:Color red.] >>> ifFalse:[p resume.m color:Color green.]. >>> running := running not]. >>> m extent:(300@50). >>> m openInWorld >>> >>> >>> clicking on the morph will stop or resume the process, if it locks up >>> I can still press alt+dot -> >>> - a Debugger opens but the UI is still not responsive. I can click >>> with the mouse on the debuggers close icon. >>> - nothing happens, as the UI is still blocked. >>> - pressing alt+Dot again, the mouse click on the close icon is >>> processed and the first debugger window closes >>> - maybe other debuggers open. >>> >>> Repeating this steps, at some time the system is *fully* responsive >>> again! >>> And miraculously, it works after that without further blockages. >>> What's happening here? >>> >>> Nicolai >>> >>> HTH >>>> >>>> regards >>>>> Nicolai >>>>> >>>> >>>> -- >>>> best, >>>> Eliot >>>> >>> -- Aloha, Eliot

July 25, 2014

Re: [Pharo-dev] [Moose-dev] [ANN] Voronyj Diagram

by Natalia Tymchuk

Thank you. Yes, I will. Natalia On Jul 25, 2014, at 5:36 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Impressive!!!! > > Natalia, will you be at esug? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Jul 25, 2014, at 8:10 AM, Natalia Tymchuk <natalia.tymchuk(a)unikernel.net> wrote: > >> Hello. >> >> I implemented Voronyj diagrams for Roassal. You can read about it here: http://natalia.tymchuk.me/RTVoronyjDiagram/ . >> I will be on vacation from Monday till Thursday, but it will be really cool if you can write me your opinion about this project and all your remarks. >> >> Best regards, >> Natalia >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >

July 25, 2014

Re: [Pharo-dev] [ANN] Voronyj Diagram

by Natalia Tymchuk

No problem. I just wanted to explain. On Jul 25, 2014, at 5:00 PM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > Sorry no problem. > I didn't want to annoy you. > > Regards, > > On Fri, Jul 25, 2014 at 4:49 PM, Natalia Tymchuk > <natalia.tymchuk(a)unikernel.net> wrote: >> Hi. >> Thank you. I know about Voronoi, but Georgiy Voronyj was Ukrainian and actually he called Voronyj. >> Voronyj means the raven color in Ukrainian. Russians translate casual nouns in proper names. In this way they get Voronoi. >> It is like if you translate Villeneuve-d'Ascq to English as Novoselok-d'Ascq because villeneuve literally translates to novoselok in Russian, or it like calling George Bush as Yuriy Kust. >> Sorry, I know that everyone use Voronoi, but I belive that I should use real name. >> >> Best regards, >> Natalia >> >> >> On Jul 25, 2014, at 3:16 PM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >> >>> Great work, great website, Natalia ! >>> Might be interested to mix Voronoi diagrams with multi-agent and >>> epidemiology modeling in the future. >>> Thank you. >>> >>> BTW, this kind of diagram are called Voronoi diagrams in english: >>> https://en.wikipedia.org/wiki/Voronoi_diagram >>> >>> On Fri, Jul 25, 2014 at 2:10 PM, Natalia Tymchuk >>> <natalia.tymchuk(a)unikernel.net> wrote: >>>> Hello. >>>> >>>> I implemented Voronyj diagrams for Roassal. You can read about it here: http://natalia.tymchuk.me/RTVoronyjDiagram/ . >>>> I will be on vacation from Monday till Thursday, but it will be really cool if you can write me your opinion about this project and all your remarks. >>>> >>>> Best regards, >>>> Natalia >>> >>> >>> >>> -- >>> Serge Stinckwich >>> UCBN & UMI UMMISCO 209 (IRD/UPMC) >>> Every DSL ends up being Smalltalk >>> http://www.doesnotunderstand.org/ >>> >> > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/

July 25, 2014

Re: [Pharo-dev] Does anyone use menuMorph in dockingbar?

by Nicolas Cellier

2014-07-25 14:59 GMT+02:00 stepharo <stepharo(a)free.fr>: > If one day we need to menubar we will design a specific menuMorph that > avoids to be crippled of is....whatever. > In old code the power of dispatch was largely underestimated. > > Stef > > > Yeah, I did not look at implementation, otherwise my boost of productivity might have vanished... The feature by itself is not un-interesting.

July 25, 2014

Re: [Pharo-dev] Looks like smart suggestions implementors is broken

by Marcus Denker

On 25 Jul 2014, at 17:37, stepharo <stepharo(a)free.fr> wrote: > But can you do implementors of because this is the one that I cannot. > DNU because #browseAllImplementorsOf: is not understood (send to the wrong class?) Should not be hard to fixâ¦ a workaround would be to add it to AbstractTool (forwarding to the browsed environments navigation). A better solution would be to add the concept of systemNavigation to the SugsContext. There is a confusion that SugsMessageBrowerContext tools is systemNavigation, while on Nautilus it is the tool itself, we should clean that up. > On 25/7/14 15:32, Marcus Denker wrote: >> On 25 Jul 2014, at 15:20, stepharo <stepharo(a)free.fr> wrote: >> >>> hi >>> >>> can someone confirm? >>> >> >> I can do âsenders ofâ of a selector. >> >> Marcus >> >> >> > >

July 25, 2014