February 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Process>>restart

by Ben Coman

On Thu, Feb 25, 2016 at 3:06 AM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > On Wed, Feb 24, 2016 at 7:23 AM, Ben Coman <btc(a)openinworld.com> wrote: >> >> Just sharing a passing thought so I don't forget it before I have time >> to think more deeply on it. >> >> Several parts of Pharo (like SHTextStyler) are designed to have a >> background process running, and when new input arrives that process is >> killed so another can be immediately started - and sometimes we seem >> to end up with large amounts of zombie processes. >> >> As I poke around Process>>terminate, I wonder if a different approach >> would be to have a Process>>restart. I see there is Context>>restart. >> >> The starting the background process might look like... >> >> stylingProcess := [ [ "do stuff with nextData". self suspend ] >> repeat ] forkAt: 30. >> >> and the code in the main morphic priority 40 thread might look like... >> >> sylingProcess suspend. >> nextData := 'blah'. >> sylingProcess restart. > > > Hi Ben, so I'm assuming restart differs from resume. Am I right in thinking > it cuts back the process to the "start"? Is the start the block from which > the process was spawned, the argument to fork or forkAt:? Thats right. Essentially like Exception>>retry, to do something like this... restart := false. workAvailable := Semaphore new. process := [ [ Transcript crShow: 'At the start'. work := 0. [ work := work + 1. Transcript crShow: 'working on ' , work printString. 1 second wait. work>8 ifTrue: [ [Transcript crShow: 'Work complete.'] fork. workAvailable wait. restart := true. ]. restart ifTrue: [self error]. work ] repeat. ] on: Error do: [:err| restart := false. err retry]. ] newProcess name:'My Restartable Worker'. process resume. "later do..." restart := true. "or after work complete..." workAvailable signal. "later still do..." process terminate ...except being able to interrupt the process anytime, i.e. not needing to wait to get to "restart ifTrue: [self error]." btw, The requirement for the fork in "[Transcript crShow: 'Work complete.'] fork" is strange. Without it the semaphore does not wait, which seems a bug. btw2, I needed to hack OCUndeclaredVariableWarning>>defaultAction to stop the transcript being polluted by unknown playground variables. No warranty on whether this is suitable to be permanent... className = 'UndefinedObject' ifFalse: [ self methodNode selector ifNotNil: [self crTrace: className, '>>', selector, ' '] ifNil: [self traceCr:'']. self traceCr: '(' , varName , ' is Undeclared1) '. ]. On Thu, Feb 25, 2016 at 2:56 AM, Max Leske <maxleske(a)gmail.com> wrote: > Fast spawning processes are very hard to debug (e.g. in the process browser). This is exactly the use case I was thinking of. Often they've been and gone before you even know they are there. Having a permanent process aids discoverability of system background functionality. cheers -ben

Feb. 25, 2016

Spotter - shortcut display on categories

by Ben Coman

I see in 50601 that Spotter categories show their shortcut. I like it a lot! Just *maybe* could the "#Implementors" text added to the search field be appended rather than prepended. Then it would feel just like typing. I say *maybe* because I'd like to use-test the idea before I'm sure of myself. Could you point me to where I could make that change to try it out locally? cheers -ben

Feb. 25, 2016

Re: [Pharo-dev] [Moose-dev] Re: short spotter demos

by Yuriy Tymchuk

Thank you very much. Does it dynamically update the result on each #value: send? Also Iâve spotted one behavior which is maybe not always expected. Usually when you are defining a processor, you can specify #actLogic:. But when you press enter on the history item it only runs the #spotterActDefault method. So when you are pressing enter on a catalog project you are prompted if you want to load it. If you press enter or a catalog project from history, the project is inspected. Uko > On 24 Feb 2016, at 22:22, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > Ok, this is more tricky, but it is supported :). Actually this is one of the really cool things about Spotter. > > For this we have #filter:item:. Look at the senders to find examples in the image. > > For example: > PragmaType>>spotterSendersFor: aStep > <spotterOrder: 50> > ^ aStep listProcessor > title: 'Senders'; > filter: GTFilterSubstring item: [ :filter :context | > self keyword senders do: [ :sender | > filter value: sender compiledMethod ] ] > > or: > GTSpotter>>spotterForReferencesFor: aStep > <spotterOrder: 32> > aStep listProcessor > title: 'References'; > filter: GTNullFilter item: [ :filter :context | > context textTrimmed asClassIfPresent: [ :class | > SystemNavigation default allReferencesTo: class binding do: filter ] ]; > keyBinding: $n shift meta; > itemName: [ :method | method gtDisplayString ] > > so, the block is being passed a filter which actually behaves like a block :). So, you can pass it to whatever traversal you have, and this will stream the results back to Spotter. I find this so cool that I cannot describe it :). > > Let me know if this helps. > > Cheers, > Doru > > > >> On Feb 24, 2016, at 10:14 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >> Also in your case you have `allCandidates`. I donât have this as Iâm going to query a remote service base on input and I want to display all that I will get :) >> >> Uko >> >>> On 24 Feb 2016, at 21:52, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>>> >>>> On 24 Feb 2016, at 21:41, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>>> >>>> This is super cool! But now I need to lookup: âHow to make your own Spotter engine(whatever you call the thing)â ;) >>> >>> That is actually surprisingly simple. >>> >>> To look up known Unicode Characters by partial name: >>> >>> GTSpotter>>#spotterForUnicodeCharacterFor: aStep >>> <spotterOrder: 30> >>> aStep listProcessor >>> title: 'Unicode Character'; >>> allCandidates: [ UnicodeCharacterData database values ]; >>> itemName: [ :each | each name ]; >>> filter: GTFilterSubstring; >>> wantsToDisplayOnEmptyQuery: false >>> >>> And if you want a preview: >>> >>> UnicodeCharacterData>>#spotterPreviewIn: aComposite >>> <spotterPreview: 10> >>> >>> ... same as GT inspector ... >>> >>>> Cheers! >>>> Uko >>>> >>>>> On 24 Feb 2016, at 21:38, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>>> >>>>> Hi, >>>>> >>>>> The recent debates around Spotter, showed that some of its features are not well understood. In an effort to document it more thoroughly I created a couple of (very short) videos. They have no sound. Please take a look and let us know what you think. >>>>> >>>>> >>>>> Spotting a class with GTSpotter >>>>> https://www.youtube.com/watch?v=_wIh4fekcD8 >>>>> >>>>> Scoping a search to a specific category in GTSpotter >>>>> https://www.youtube.com/watch?v=9-fY4mN6Isc >>>>> >>>>> Using category shortcuts in GTSpotter >>>>> https://www.youtube.com/watch?v=USNZ7_6gLDA >>>>> >>>>> Using preview in GTSpotter >>>>> https://www.youtube.com/watch?v=FSm5xylmTqM >>>>> >>>>> Using the dive-in action in GTSpotter >>>>> https://www.youtube.com/watch?v=C7mJBX3Oblw >>>>> >>>>> Loading a public playground with GTSpotter >>>>> https://www.youtube.com/watch?v=xeDDLLdA1v8 >>>>> >>>>> Navigating through files with GTSpotter >>>>> https://www.youtube.com/watch?v=dHQqXcS0vDI >>>>> >>>>> Refining a search through the dive-in-category action with GTSpotter >>>>> https://www.youtube.com/watch?v=IclLett0d6c >>>>> >>>>> Opening a cached playground page with GTSpotter >>>>> https://www.youtube.com/watch?v=V_yndTSsj8c >>>>> >>>>> >>>>> Cheers, >>>>> Doru >>>>> >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> www.feenk.com >>>>> >>>>> "Yesterday is a fact. >>>>> Tomorrow is a possibility. >>>>> Today is a challenge." >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> Moose-dev(a)list.inf.unibe.ch >>>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)list.inf.unibe.ch >>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)list.inf.unibe.ch >>> https://www.list.inf.unibe.ch/listinfo/moose-dev >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.tudorgirba.com > www.feenk.com > > "Every thing has its own flow." > > > > > >

Feb. 24, 2016

Re: [Pharo-dev] Spotter changes broke CodePanel

by Stephan Eggermont

On 24/02/16 20:14, Tudor Girba wrote: > I took a brief look. It looks like a strange problem. If I add the > wantsToDisplayOnEmptyQuery to false, it seems to work, but I do not > understand the real problem. At least not yet. Could you live with it > for now? I'll take a better look tomorrow. Thanks for looking into it. Stephan

Feb. 24, 2016

Re: [Pharo-dev] [Moose-dev] Re: short spotter demos

by Tudor Girba

Hi, Ok, this is more tricky, but it is supported :). Actually this is one of the really cool things about Spotter. For this we have #filter:item:. Look at the senders to find examples in the image. For example: PragmaType>>spotterSendersFor: aStep <spotterOrder: 50> ^ aStep listProcessor title: 'Senders'; filter: GTFilterSubstring item: [ :filter :context | self keyword senders do: [ :sender | filter value: sender compiledMethod ] ] or: GTSpotter>>spotterForReferencesFor: aStep <spotterOrder: 32> aStep listProcessor title: 'References'; filter: GTNullFilter item: [ :filter :context | context textTrimmed asClassIfPresent: [ :class | SystemNavigation default allReferencesTo: class binding do: filter ] ]; keyBinding: $n shift meta; itemName: [ :method | method gtDisplayString ] so, the block is being passed a filter which actually behaves like a block :). So, you can pass it to whatever traversal you have, and this will stream the results back to Spotter. I find this so cool that I cannot describe it :). Let me know if this helps. Cheers, Doru > On Feb 24, 2016, at 10:14 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Also in your case you have `allCandidates`. I donât have this as Iâm going to query a remote service base on input and I want to display all that I will get :) > > Uko > >> On 24 Feb 2016, at 21:52, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> >>> On 24 Feb 2016, at 21:41, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>> >>> This is super cool! But now I need to lookup: âHow to make your own Spotter engine(whatever you call the thing)â ;) >> >> That is actually surprisingly simple. >> >> To look up known Unicode Characters by partial name: >> >> GTSpotter>>#spotterForUnicodeCharacterFor: aStep >> <spotterOrder: 30> >> aStep listProcessor >> title: 'Unicode Character'; >> allCandidates: [ UnicodeCharacterData database values ]; >> itemName: [ :each | each name ]; >> filter: GTFilterSubstring; >> wantsToDisplayOnEmptyQuery: false >> >> And if you want a preview: >> >> UnicodeCharacterData>>#spotterPreviewIn: aComposite >> <spotterPreview: 10> >> >> ... same as GT inspector ... >> >>> Cheers! >>> Uko >>> >>>> On 24 Feb 2016, at 21:38, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> >>>> Hi, >>>> >>>> The recent debates around Spotter, showed that some of its features are not well understood. In an effort to document it more thoroughly I created a couple of (very short) videos. They have no sound. Please take a look and let us know what you think. >>>> >>>> >>>> Spotting a class with GTSpotter >>>> https://www.youtube.com/watch?v=_wIh4fekcD8 >>>> >>>> Scoping a search to a specific category in GTSpotter >>>> https://www.youtube.com/watch?v=9-fY4mN6Isc >>>> >>>> Using category shortcuts in GTSpotter >>>> https://www.youtube.com/watch?v=USNZ7_6gLDA >>>> >>>> Using preview in GTSpotter >>>> https://www.youtube.com/watch?v=FSm5xylmTqM >>>> >>>> Using the dive-in action in GTSpotter >>>> https://www.youtube.com/watch?v=C7mJBX3Oblw >>>> >>>> Loading a public playground with GTSpotter >>>> https://www.youtube.com/watch?v=xeDDLLdA1v8 >>>> >>>> Navigating through files with GTSpotter >>>> https://www.youtube.com/watch?v=dHQqXcS0vDI >>>> >>>> Refining a search through the dive-in-category action with GTSpotter >>>> https://www.youtube.com/watch?v=IclLett0d6c >>>> >>>> Opening a cached playground page with GTSpotter >>>> https://www.youtube.com/watch?v=V_yndTSsj8c >>>> >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> www.feenk.com >>>> >>>> "Yesterday is a fact. >>>> Tomorrow is a possibility. >>>> Today is a challenge." >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)list.inf.unibe.ch >>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)list.inf.unibe.ch >>> https://www.list.inf.unibe.ch/listinfo/moose-dev >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com www.feenk.com "Every thing has its own flow."

Feb. 24, 2016

short spotter demos

by Tudor Girba

Hi, The recent debates around Spotter, showed that some of its features are not well understood. In an effort to document it more thoroughly I created a couple of (very short) videos. They have no sound. Please take a look and let us know what you think. Spotting a class with GTSpotter https://www.youtube.com/watch?v=_wIh4fekcD8 Scoping a search to a specific category in GTSpotter https://www.youtube.com/watch?v=9-fY4mN6Isc Using category shortcuts in GTSpotter https://www.youtube.com/watch?v=USNZ7_6gLDA Using preview in GTSpotter https://www.youtube.com/watch?v=FSm5xylmTqM Using the dive-in action in GTSpotter https://www.youtube.com/watch?v=C7mJBX3Oblw Loading a public playground with GTSpotter https://www.youtube.com/watch?v=xeDDLLdA1v8 Navigating through files with GTSpotter https://www.youtube.com/watch?v=dHQqXcS0vDI Refining a search through the dive-in-category action with GTSpotter https://www.youtube.com/watch?v=IclLett0d6c Opening a cached playground page with GTSpotter https://www.youtube.com/watch?v=V_yndTSsj8c Cheers, Doru -- www.tudorgirba.com www.feenk.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

Feb. 24, 2016

Re: [Pharo-dev] Help with PrStef with Fonts

by Nicolai Hess

2016-02-24 17:45 GMT+01:00 stepharo <stepharo(a)free.fr>: > this is what I started to suspect!!! > Ok I saw that you already commit the code you were faster than me :) > No, thats not from me. I'll check. > > Stef > > Le 24/2/16 17:29, Nicolai Hess a Ã©crit : > > > Am 24.02.2016 5:26 nachm. schrieb "stepharo" < <stepharo(a)free.fr> > stepharo(a)free.fr>: > > > > > >>> > >>> may be > >>> > >>> showLesson: aLesson withTitle: aString > >>> self window setLabel: aString. > >>> self sourceTextModel setText: aLesson lesson. > >>> self isOpenInWindow ifFalse: [ self open ] > >>> > >>> > >>> but I do not know :( > >>> > >>> Stef > >>> > >> > >> Maybe both, > >> beForSmalltalkCode and beForSmalltalkScripting in > >> RubScrolledTextMorph should use > >> self textArea font: StandardFonts codeFont > >> > >> At the moment, only beForSmalltalkCode sets this font. > > > > > > Yes I did the same as you, I tried to add > > > > beForSmalltalkScripting > > self textArea beForSmalltalkScripting. > > > > self textArea font: StandardFonts codeFont > > > > But without success. I'm puzzled. > > Stef > > > > And you need to reset the tutorial, it reuses the existing lesson view. > > >

Feb. 24, 2016

Re: [Pharo-dev] Spotter changes broke CodePanel

by Tudor Girba

Hi, I took a brief look. It looks like a strange problem. If I add the wantsToDisplayOnEmptyQuery to false, it seems to work, but I do not understand the real problem. At least not yet. Could you live with it for now? GTSpotterMorph new extent: (World width / 3.25 @ (World height / 2.25)) asIntegerPoint; spotterModel: ((GTSpotter new) processorsFilter: (CodePanelProcessorFilter new configuredWith: [ :aProcessor | aProcessor actLogic: [ :aMethod :step | step exit. aMethod ifNil: [ self new openInWindowLabeled: 'Code panel' ] ifNotNil: [ |panel| panel := self new. panel openInWindowLabeled: 'Code panel'. panel newCardFor: aMethod.]]; candidatesLimit: 50; wantsToDisplayOnEmptyQuery: false ])); openCenteredInWorld Cheers, Doru > On Feb 24, 2016, at 7:46 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > > On 24-02-16 19:37, Tudor Girba wrote: >> Hi, >> >> Could you provide a fully loadable sample to look at this? > > Just load NewUI from the configuration browser. > > Stephan > > > -- www.tudorgirba.com www.feenk.com "Quality cannot be an afterthought."

Feb. 24, 2016

Re: [Pharo-dev] Process>>restart

by Eliot Miranda

On Wed, Feb 24, 2016 at 7:23 AM, Ben Coman <btc(a)openinworld.com> wrote: > Just sharing a passing thought so I don't forget it before I have time > to think more deeply on it. > > Several parts of Pharo (like SHTextStyler) are designed to have a > background process running, and when new input arrives that process is > killed so another can be immediately started - and sometimes we seem > to end up with large amounts of zombie processes. > > As I poke around Process>>terminate, I wonder if a different approach > would be to have a Process>>restart. I see there is Context>>restart. > > The starting the background process might look like... > > stylingProcess := [ [ "do stuff with nextData". self suspend ] > repeat ] forkAt: 30. > > and the code in the main morphic priority 40 thread might look like... > > sylingProcess suspend. > nextData := 'blah'. > sylingProcess restart. > Hi Ben, so I'm assuming restart differs from resume. Am I right in thinking it cuts back the process to the "start"? Is the start the block from which the process was spawned, the argument to fork or forkAt:? > anyway, back to the grind for me, > cheers -ben > _,,,^..^,,,_ best, Eliot

Feb. 24, 2016

Re: [Pharo-dev] About contents of Pharo by Example updated

by Tudor Girba

Hi, I think this is a good idea. Another idea would be to point people to the help and then institute a help page per-tool policy. We can just create empty items and fill them over time. What do you think? Cheers, Doru > On Feb 24, 2016, at 8:02 PM, stepharo <stepharo(a)free.fr> wrote: > > Hi > > I'm looking at some chapters of Pharo by Example like environment that presents many tools > and I think that I cannot spend time updating this chapter. > What I will do is to have one tool per page with a small description and key points. > Else the book will again get obsolete. > > I do not know what you think but I do not have the cycles for all the tiny details. > > Stef > -- www.tudorgirba.com www.feenk.com "It's not how it is, it is how we see it."

Feb. 24, 2016