October 2016 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

by phil＠highoctane.be

A good trick is to use raw Display output. Display getCanvas drawString: 'hello' from: 1 to: 5 autoBoundAt: 0 @ 0 font: nil color: Color black. On Mon, Oct 3, 2016 at 12:25 PM, Ben Coman <btc(a)openinworld.com> wrote: > On Mon, Oct 3, 2016 at 6:08 PM, Ben Coman <btc(a)openinworld.com> wrote: > > On Mon, Oct 3, 2016 at 3:49 PM, CodeDmitry <dimamakhnin(a)gmail.com> > wrote: > >> a JavaScript timeout is a function that takes a block and a period of > time, > >> and after this period of time, puts the block at the end of the event > >> queue, to be executed as soon as the runtime is done performing the > tasks in > >> front of it. > >> > >> I am not sure if Pharo has an event queue, so it's a bit harder to do > >> it(since without one you can't ensure only one thing happens at a time, > and > >> strange things can happen). > >> > >> That said, in simplest terms, imagine writing a clock app for Pharo, > which > >> updates time every second, in JS this would be done by setting an > interval > >> that ticks every 1000ms, and each time places the callback > function(block) > >> at the end of the event queue. > >> > >> Related: https://www.youtube.com/watch?time_continue=1&v=8aGhZQkoFbQ > > > > Pharo has a single threaded VM, but multiple green threads can run > concurrently. > > The closest to the event loop you are thinking of most likely the > > Morphic UI Process > > which you can see using World > Tools > Process Browser. When you > execute code > > from Playground it runs in that Process (note what Smalltalk > > historically (circa 1970s?) has > > called a Process is today more commonly know as a Green Thread) > > > > If you select Morphic UI Process you will see its call stack on the > > right, where an interesting method is WorldState>>doOneCycleFor: > > You can gain some insight by turning on auto-update in the Process > > Browser, then open a Browser on WorldState>>doOneCycleFor: > > and put "self haltOnce" at the top, then enable it via... > > Pharo 5: World > System > Enable halt/inspect once. > > Pharo 6: World > Debugging > Enable all break/inspect once. > > > > You will see in the Process Browser that a new Morphic UI Process is > > spawned, and the original Morphic UI Process call stack now has > > #debugProcess at the top > > and a debug window appears that you can step through. Note, since two > > UI loops are executing here, the image may lock up, but usually its > > fine so hey! live on the edge! > > > I meant to ask the list about a bug I hit doing this.... > > Putting a "self haltOnce" here... > > WorldState>>doOneCycleNowFor: aWorld > DisplayScreen checkForNewScreenSize. > self haltOnce. > "process user input events" > LastCycleTime := Time millisecondClockValue. > self handsDo: [:h | > self activeHand: h. > h processEvents. > self activeHand: nil. > ]. > self activeHand: self hands first. > aWorld runStepMethods. "there are currently some variations here" > self displayWorldSafely: aWorld. > > > When stepping over "self activeHand: nil." > another debugger appears MNU: receiver of "releaseKeyboardFocus:" is nil > in GLMPagerPanePreviewMorph(Morph)>>delete > > self activeHand > releaseKeyboardFocus: self; > releaseMouseFocus: self. > > > This can obviously be fixed by wrapping "self activeHand" with an #ifNil: > but alternatively I wonder if the "self activeHand: nil" is really needed? > It seems redundant since activeHand is set at the top of the loop and > immediately after exiting the loop. > Eliminating it would reduce the propagation of #ifNil: anti-pattern. > > https://pharo.fogbugz.com/default.asp?19169 > > cheers -ben > > > > > In #runStepMethodsIn: you'll see "queue := self class > > deferredUIMessages" for which you enqueue items like this... > > http://forum.world.st/Issue-3562-in-pharo-Deferred-UI- > messages-executed-slowly-td3228060.html > > > > After processing the deferred UI messages, each Morph's #step method > > is processed by #runLocalStepMethodsIn: > > refer... http://wiki.squeak.org/squeak/2096 > > > > The display is then rendered by #displayWorldSafely: calling... > > --> #displayWorld > > --> #displayWorld:submorphs: > > which then is a lot to trace through, but depending on the graphics > > back end eventually ends up calling... > > Canvas>>fullDrawMorph: which ultimately invokes one of many #drawOn: > > or... > > AthensCanvas>>fullDrawMorph: which ultimately invokes one of many > > #drawOnAthensCanvas: > > > > > > So, for a regular timed UI animation, you would define your custom > > morph's #step and #stepTime methods, > > and for lower level stuff you would fork like Dennis suggests. > > > > cheers -ben > > >

Oct. 3, 2016

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

by phil＠highoctane.be

There has been some serious refactoring occuring in these specific bowels of the beast. Phil On Mon, Oct 3, 2016 at 1:08 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi Ben. > > 2016-10-03 12:37 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > >> A further curiousity occurs to me. With this being executed 20 times >> a second or more, how can the active hand ever be anything other than >> the primary hand? >> Why isn't the active hand stored, all hands cycled through processing >> events, then the active hand restored?? >> > > Previous version of method was also with nil at the end: > > self handsDo: [:h | > ActiveHand := h. > h processEvents. > ActiveHand := nil > ]. > > Could you try your test on previous version of Pharo? > >

Oct. 3, 2016

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

by phil＠highoctane.be

UIManager>>#defer: aBlock can be useful too. defer: aBlock " Evaluate the given Block in the UI thread as soon as there is nothing scheduled. Evaluate immediately when there is no UI" aBlock value For some fun, check also GrowlMorph 10 timesRepeat: [ (GrowlMorph openWithLabel: 'The time' contents: DateAndTime now) " vanishDelay: 1000; resetVanishTimer". World doOneCycle ]. inspect how vanishDelay: works, so that you can get the same kind of thing as a JS setTimeout(function(){ alert("Hello"); }, 3000); Phil On Mon, Oct 3, 2016 at 12:08 PM, Ben Coman <btc(a)openinworld.com> wrote: > > On Mon, Oct 3, 2016 at 3:49 PM, CodeDmitry <dimamakhnin(a)gmail.com> wrote: > > a JavaScript timeout is a function that takes a block and a period of time, > > and after this period of time, puts the block at the end of the event > > queue, to be executed as soon as the runtime is done performing the tasks in > > front of it. > > > > I am not sure if Pharo has an event queue, so it's a bit harder to do > > it(since without one you can't ensure only one thing happens at a time, and > > strange things can happen). > > > > That said, in simplest terms, imagine writing a clock app for Pharo, which > > updates time every second, in JS this would be done by setting an interval > > that ticks every 1000ms, and each time places the callback function(block) > > at the end of the event queue. > > > > Related: https://www.youtube.com/watch?time_continue=1&v=8aGhZQkoFbQ > > Pharo has a single threaded VM, but multiple green threads can run concurrently. > The closest to the event loop you are thinking of most likely the > Morphic UI Process > which you can see using World > Tools > Process Browser. When you execute code > from Playground it runs in that Process (note what Smalltalk > historically (circa 1970s?) has > called a Process is today more commonly know as a Green Thread) > > If you select Morphic UI Process you will see its call stack on the > right, where an interesting method is WorldState>>doOneCycleFor: > You can gain some insight by turning on auto-update in the Process > Browser, then open a Browser on WorldState>>doOneCycleFor: > and put "self haltOnce" at the top, then enable it via... > Pharo 5: World > System > Enable halt/inspect once. > Pharo 6: World > Debugging > Enable all break/inspect once. > > You will see in the Process Browser that a new Morphic UI Process is > spawned, and the original Morphic UI Process call stack now has > #debugProcess at the top > and a debug window appears that you can step through. Note, since two > UI loops are executing here, the image may lock up, but usually its > fine so hey! live on the edge! > > In #runStepMethodsIn: you'll see "queue := self class > deferredUIMessages" for which you enqueue items like this... > http://forum.world.st/Issue-3562-in-pharo-Deferred-UI-messages-executed-slo… > > After processing the deferred UI messages, each Morph's #step method > is processed by #runLocalStepMethodsIn: > refer... http://wiki.squeak.org/squeak/2096 > > The display is then rendered by #displayWorldSafely: calling... > --> #displayWorld > --> #displayWorld:submorphs: > which then is a lot to trace through, but depending on the graphics > back end eventually ends up calling... > Canvas>>fullDrawMorph: which ultimately invokes one of many #drawOn: > or... > AthensCanvas>>fullDrawMorph: which ultimately invokes one of many > #drawOnAthensCanvas: > > > So, for a regular timed UI animation, you would define your custom > morph's #step and #stepTime methods, > and for lower level stuff you would fork like Dennis suggests. > > cheers -ben > >

Oct. 3, 2016

Re: [Pharo-users] Pharo on my Ubuntu laptop :3

by phil＠highoctane.be

SystemWindow can be a good start. On Mon, Oct 3, 2016 at 10:57 AM, CodeDmitry <dimamakhnin(a)gmail.com> wrote: > Sounds exciting, I've been trying to tweak the window buttons but couldn't > figure out where to look. > > > > -- > View this message in context: http://forum.world.st/Pharo- > on-my-Ubuntu-laptop-3-tp4917833p4917846.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > >

Oct. 3, 2016

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

by Denis Kudriashov

Hi Ben. 2016-10-03 12:37 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > A further curiousity occurs to me. With this being executed 20 times > a second or more, how can the active hand ever be anything other than > the primary hand? > Why isn't the active hand stored, all hands cycled through processing > events, then the active hand restored?? > Previous version of method was also with nil at the end: self handsDo: [:h | ActiveHand := h. h processEvents. ActiveHand := nil ]. Could you try your test on previous version of Pharo?

Oct. 3, 2016

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

by Ben Coman

On Mon, Oct 3, 2016 at 6:25 PM, Ben Coman <btc(a)openinworld.com> wrote: > On Mon, Oct 3, 2016 at 6:08 PM, Ben Coman <btc(a)openinworld.com> wrote: >> On Mon, Oct 3, 2016 at 3:49 PM, CodeDmitry <dimamakhnin(a)gmail.com> wrote: >>> a JavaScript timeout is a function that takes a block and a period of time, >>> and after this period of time, puts the block at the end of the event >>> queue, to be executed as soon as the runtime is done performing the tasks in >>> front of it. >>> >>> I am not sure if Pharo has an event queue, so it's a bit harder to do >>> it(since without one you can't ensure only one thing happens at a time, and >>> strange things can happen). >>> >>> That said, in simplest terms, imagine writing a clock app for Pharo, which >>> updates time every second, in JS this would be done by setting an interval >>> that ticks every 1000ms, and each time places the callback function(block) >>> at the end of the event queue. >>> >>> Related: https://www.youtube.com/watch?time_continue=1&v=8aGhZQkoFbQ >> >> Pharo has a single threaded VM, but multiple green threads can run concurrently. >> The closest to the event loop you are thinking of most likely the >> Morphic UI Process >> which you can see using World > Tools > Process Browser. When you execute code >> from Playground it runs in that Process (note what Smalltalk >> historically (circa 1970s?) has >> called a Process is today more commonly know as a Green Thread) >> >> If you select Morphic UI Process you will see its call stack on the >> right, where an interesting method is WorldState>>doOneCycleFor: >> You can gain some insight by turning on auto-update in the Process >> Browser, then open a Browser on WorldState>>doOneCycleFor: >> and put "self haltOnce" at the top, then enable it via... >> Pharo 5: World > System > Enable halt/inspect once. >> Pharo 6: World > Debugging > Enable all break/inspect once. >> >> You will see in the Process Browser that a new Morphic UI Process is >> spawned, and the original Morphic UI Process call stack now has >> #debugProcess at the top >> and a debug window appears that you can step through. Note, since two >> UI loops are executing here, the image may lock up, but usually its >> fine so hey! live on the edge! > > > I meant to ask the list about a bug I hit doing this.... > > Putting a "self haltOnce" here... > > WorldState>>doOneCycleNowFor: aWorld > DisplayScreen checkForNewScreenSize. > self haltOnce. > "process user input events" > LastCycleTime := Time millisecondClockValue. > self handsDo: [:h | > self activeHand: h. > h processEvents. > self activeHand: nil. > ]. > self activeHand: self hands first. A further curiousity occurs to me. With this being executed 20 times a second or more, how can the active hand ever be anything other than the primary hand? Why isn't the active hand stored, all hands cycled through processing events, then the active hand restored?? cheers -ben > aWorld runStepMethods. "there are currently some variations here" > self displayWorldSafely: aWorld. > > > When stepping over "self activeHand: nil." > another debugger appears MNU: receiver of "releaseKeyboardFocus:" is nil > in GLMPagerPanePreviewMorph(Morph)>>delete > > self activeHand > releaseKeyboardFocus: self; > releaseMouseFocus: self. > > > This can obviously be fixed by wrapping "self activeHand" with an #ifNil: > but alternatively I wonder if the "self activeHand: nil" is really needed? > It seems redundant since activeHand is set at the top of the loop and > immediately after exiting the loop. > Eliminating it would reduce the propagation of #ifNil: anti-pattern. > > https://pharo.fogbugz.com/default.asp?19169 > > cheers -ben > >> >> In #runStepMethodsIn: you'll see "queue := self class >> deferredUIMessages" for which you enqueue items like this... >> http://forum.world.st/Issue-3562-in-pharo-Deferred-UI-messages-executed-slo… >> >> After processing the deferred UI messages, each Morph's #step method >> is processed by #runLocalStepMethodsIn: >> refer... http://wiki.squeak.org/squeak/2096 >> >> The display is then rendered by #displayWorldSafely: calling... >> --> #displayWorld >> --> #displayWorld:submorphs: >> which then is a lot to trace through, but depending on the graphics >> back end eventually ends up calling... >> Canvas>>fullDrawMorph: which ultimately invokes one of many #drawOn: >> or... >> AthensCanvas>>fullDrawMorph: which ultimately invokes one of many >> #drawOnAthensCanvas: >> >> >> So, for a regular timed UI animation, you would define your custom >> morph's #step and #stepTime methods, >> and for lower level stuff you would fork like Dennis suggests. >> >> cheers -ben

Oct. 3, 2016

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

by Ben Coman

On Mon, Oct 3, 2016 at 6:08 PM, Ben Coman <btc(a)openinworld.com> wrote: > On Mon, Oct 3, 2016 at 3:49 PM, CodeDmitry <dimamakhnin(a)gmail.com> wrote: >> a JavaScript timeout is a function that takes a block and a period of time, >> and after this period of time, puts the block at the end of the event >> queue, to be executed as soon as the runtime is done performing the tasks in >> front of it. >> >> I am not sure if Pharo has an event queue, so it's a bit harder to do >> it(since without one you can't ensure only one thing happens at a time, and >> strange things can happen). >> >> That said, in simplest terms, imagine writing a clock app for Pharo, which >> updates time every second, in JS this would be done by setting an interval >> that ticks every 1000ms, and each time places the callback function(block) >> at the end of the event queue. >> >> Related: https://www.youtube.com/watch?time_continue=1&v=8aGhZQkoFbQ > > Pharo has a single threaded VM, but multiple green threads can run concurrently. > The closest to the event loop you are thinking of most likely the > Morphic UI Process > which you can see using World > Tools > Process Browser. When you execute code > from Playground it runs in that Process (note what Smalltalk > historically (circa 1970s?) has > called a Process is today more commonly know as a Green Thread) > > If you select Morphic UI Process you will see its call stack on the > right, where an interesting method is WorldState>>doOneCycleFor: > You can gain some insight by turning on auto-update in the Process > Browser, then open a Browser on WorldState>>doOneCycleFor: > and put "self haltOnce" at the top, then enable it via... > Pharo 5: World > System > Enable halt/inspect once. > Pharo 6: World > Debugging > Enable all break/inspect once. > > You will see in the Process Browser that a new Morphic UI Process is > spawned, and the original Morphic UI Process call stack now has > #debugProcess at the top > and a debug window appears that you can step through. Note, since two > UI loops are executing here, the image may lock up, but usually its > fine so hey! live on the edge! I meant to ask the list about a bug I hit doing this.... Putting a "self haltOnce" here... WorldState>>doOneCycleNowFor: aWorld DisplayScreen checkForNewScreenSize. self haltOnce. "process user input events" LastCycleTime := Time millisecondClockValue. self handsDo: [:h | self activeHand: h. h processEvents. self activeHand: nil. ]. self activeHand: self hands first. aWorld runStepMethods. "there are currently some variations here" self displayWorldSafely: aWorld. When stepping over "self activeHand: nil." another debugger appears MNU: receiver of "releaseKeyboardFocus:" is nil in GLMPagerPanePreviewMorph(Morph)>>delete self activeHand releaseKeyboardFocus: self; releaseMouseFocus: self. This can obviously be fixed by wrapping "self activeHand" with an #ifNil: but alternatively I wonder if the "self activeHand: nil" is really needed? It seems redundant since activeHand is set at the top of the loop and immediately after exiting the loop. Eliminating it would reduce the propagation of #ifNil: anti-pattern. https://pharo.fogbugz.com/default.asp?19169 cheers -ben > > In #runStepMethodsIn: you'll see "queue := self class > deferredUIMessages" for which you enqueue items like this... > http://forum.world.st/Issue-3562-in-pharo-Deferred-UI-messages-executed-slo… > > After processing the deferred UI messages, each Morph's #step method > is processed by #runLocalStepMethodsIn: > refer... http://wiki.squeak.org/squeak/2096 > > The display is then rendered by #displayWorldSafely: calling... > --> #displayWorld > --> #displayWorld:submorphs: > which then is a lot to trace through, but depending on the graphics > back end eventually ends up calling... > Canvas>>fullDrawMorph: which ultimately invokes one of many #drawOn: > or... > AthensCanvas>>fullDrawMorph: which ultimately invokes one of many > #drawOnAthensCanvas: > > > So, for a regular timed UI animation, you would define your custom > morph's #step and #stepTime methods, > and for lower level stuff you would fork like Dennis suggests. > > cheers -ben

Oct. 3, 2016

Re: [Pharo-users] Intro to Microsoft COM for Smalltalkers

by Ben Coman

On Mon, Oct 3, 2016 at 3:49 PM, CodeDmitry <dimamakhnin(a)gmail.com> wrote: > a JavaScript timeout is a function that takes a block and a period of time, > and after this period of time, puts the block at the end of the event > queue, to be executed as soon as the runtime is done performing the tasks in > front of it. > > I am not sure if Pharo has an event queue, so it's a bit harder to do > it(since without one you can't ensure only one thing happens at a time, and > strange things can happen). > > That said, in simplest terms, imagine writing a clock app for Pharo, which > updates time every second, in JS this would be done by setting an interval > that ticks every 1000ms, and each time places the callback function(block) > at the end of the event queue. > > Related: https://www.youtube.com/watch?time_continue=1&v=8aGhZQkoFbQ Pharo has a single threaded VM, but multiple green threads can run concurrently. The closest to the event loop you are thinking of most likely the Morphic UI Process which you can see using World > Tools > Process Browser. When you execute code from Playground it runs in that Process (note what Smalltalk historically (circa 1970s?) has called a Process is today more commonly know as a Green Thread) If you select Morphic UI Process you will see its call stack on the right, where an interesting method is WorldState>>doOneCycleFor: You can gain some insight by turning on auto-update in the Process Browser, then open a Browser on WorldState>>doOneCycleFor: and put "self haltOnce" at the top, then enable it via... Pharo 5: World > System > Enable halt/inspect once. Pharo 6: World > Debugging > Enable all break/inspect once. You will see in the Process Browser that a new Morphic UI Process is spawned, and the original Morphic UI Process call stack now has #debugProcess at the top and a debug window appears that you can step through. Note, since two UI loops are executing here, the image may lock up, but usually its fine so hey! live on the edge! In #runStepMethodsIn: you'll see "queue := self class deferredUIMessages" for which you enqueue items like this... http://forum.world.st/Issue-3562-in-pharo-Deferred-UI-messages-executed-slo… After processing the deferred UI messages, each Morph's #step method is processed by #runLocalStepMethodsIn: refer... http://wiki.squeak.org/squeak/2096 The display is then rendered by #displayWorldSafely: calling... --> #displayWorld --> #displayWorld:submorphs: which then is a lot to trace through, but depending on the graphics back end eventually ends up calling... Canvas>>fullDrawMorph: which ultimately invokes one of many #drawOn: or... AthensCanvas>>fullDrawMorph: which ultimately invokes one of many #drawOnAthensCanvas: So, for a regular timed UI animation, you would define your custom morph's #step and #stepTime methods, and for lower level stuff you would fork like Dennis suggests. cheers -ben

Oct. 3, 2016

Re: [Pharo-users] Pharo on my Ubuntu laptop :3

by CodeDmitry

Sounds exciting, I've been trying to tweak the window buttons but couldn't figure out where to look. -- View this message in context: http://forum.world.st/Pharo-on-my-Ubuntu-laptop-3-tp4917833p4917846.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Oct. 3, 2016

Re: [Pharo-users] bytes to utf8 string / byte stream parsing

by Fabrice Leal

hey! yeah, i checked it, it seems to solve my issue but i havent test it yet. i have a custom binary format that i want to parse, and was looking for a way for reading a utf8 string as encoded by c# (where i generate files with this format). gotta check that Xtreams thing On Mon, Oct 3, 2016 at 6:39 AM, stepharo <stepharo(a)free.fr> wrote: > Hello Fabrice > > Did you read the excellent book chapter written by sven on stream > encodings? > > Check Enterprise Pharo book http://books.pharo.org > > Now can you tell us what you want to do? > > It would be nice also to check if Xtreams offers (or deserves some > extensions). > > Stef > > Le 30/9/16 Ã 12:57, Fabrice Leal a Ã©crit : > > can anyone provide me some pointers on how to turn a bunch of bytes into a > utf8 string? > > i'm planning on writing a byte stream parser, would appreciate anything > you might find useful in addition to the Streams chapter from Pharo by > Example > > -- > --- > Fabrice Leal > > > -- --- Fabrice Leal

Oct. 3, 2016