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

Re: [Pharo-dev] Spotter - shortcut display on categories

by Ben Coman

okay, that makes sense. cheers -ben On Thu, Feb 25, 2016 at 6:11 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > We added it intentionally at the beginning so that you can continue typing without being disturbed. The idea is that you can do something like: > - GT > - Cmd+b > - In > > ==> #Classes GTIn > > For this scenario, it feels more natural to have the cursor at the end. On the other hand, the whole text shifts. Both options have pros and cons I think. > > Cheers, > Doru > > >> On Feb 25, 2016, at 6:05 AM, Ben Coman <btc(a)openInWorld.com> wrote: >> >> 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 >> > > -- > www.tudorgirba.com > www.feenk.com > > "One cannot do more than one can do." > > > > >

Feb. 25, 2016

Re: [Pharo-dev] Spotter - shortcut display on categories

by Tudor Girba

Hi, We added it intentionally at the beginning so that you can continue typing without being disturbed. The idea is that you can do something like: - GT - Cmd+b - In ==> #Classes GTIn For this scenario, it feels more natural to have the cursor at the end. On the other hand, the whole text shifts. Both options have pros and cons I think. Cheers, Doru > On Feb 25, 2016, at 6:05 AM, Ben Coman <btc(a)openInWorld.com> wrote: > > 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 > -- www.tudorgirba.com www.feenk.com "One cannot do more than one can do."

Feb. 25, 2016

Re: [Pharo-dev] [bloc] feature envy -> move method close to data?

by Alain Plantec

Hello, very good remark. This is one of the main consequence of the design review we made recently. In the first design, this was the case, the drawing was delegated. For now, it is a known issue of the current design. Cheers Alain > On 25 fÃ©vr. 2016, at 09:56, stepharo <stepharo(a)free.fr> wrote: > > Hi Blockers > > I do not really understand why drawOnAthensCanvas: is not defined on BlShape > (especially when we see how many self space are defined in this method. > And this is one of the few things I thought I understood from bloc (grouping the rendering in a separate object). > > > drawOnAthensCanvas: aCanvas > "Actually render receiver on aCanvas in local bounds. > Override to customize. > aCanvas is an instance of AthensCanvas > aCanvas must not be nil" > > | pathTransform | > pathTransform := aCanvas pathTransform. > "First we fill" > pathTransform > restoreAfter: > [ | path fillExtent fillTranslation | > "We fill inside natural element's bounds" > fillExtent := self shape path fillExtentFor: self shape inBounds: self localBounds. > path := self shape path pathOn: aCanvas forExtent: fillExtent. > "Translate fill if needed" > fillTranslation := self shape path > fillTranslationFor: self shape > inBounds: self localBounds. > pathTransform translateBy: fillTranslation. > aCanvas > setPaint: self shape fillPaint; > drawShape: path ]. > pathTransform > restoreAfter: > [ | path strokeExtent strokeTranslation | > "We stroke inside natural element's bounds" > strokeExtent := self shape path strokeExtentFor: self shape inBounds: self localBounds. > path := self shape path pathOn: aCanvas forExtent: strokeExtent. > "Translate stroke if needed" > strokeTranslation := self shape path > strokeTranslationFor: self shape > inBounds: self localBounds. > pathTransform translateBy: strokeTranslation. > aCanvas > setPaint: self shape strokePaint; > drawShape: path ] >

Feb. 25, 2016

Re: [Pharo-dev] [bloc] feature envy -> move method close to data?

by Tudor Girba

Hi, Good question. The reason we want to have the morph be responsible because subclasses might decide to draw in a different way regardless of the shape being used. This gives us the maximum freedom for more specific blocs. Still, this is something to experiment with once we have more complicated examples built with Bloc. Cheers, Doru > On Feb 25, 2016, at 9:56 AM, stepharo <stepharo(a)free.fr> wrote: > > Hi Blockers > > I do not really understand why drawOnAthensCanvas: is not defined on BlShape > (especially when we see how many self space are defined in this method. > And this is one of the few things I thought I understood from bloc (grouping the rendering in a separate object). > > > drawOnAthensCanvas: aCanvas > "Actually render receiver on aCanvas in local bounds. > Override to customize. > aCanvas is an instance of AthensCanvas > aCanvas must not be nil" > > | pathTransform | > pathTransform := aCanvas pathTransform. > "First we fill" > pathTransform > restoreAfter: > [ | path fillExtent fillTranslation | > "We fill inside natural element's bounds" > fillExtent := self shape path fillExtentFor: self shape inBounds: self localBounds. > path := self shape path pathOn: aCanvas forExtent: fillExtent. > "Translate fill if needed" > fillTranslation := self shape path > fillTranslationFor: self shape > inBounds: self localBounds. > pathTransform translateBy: fillTranslation. > aCanvas > setPaint: self shape fillPaint; > drawShape: path ]. > pathTransform > restoreAfter: > [ | path strokeExtent strokeTranslation | > "We stroke inside natural element's bounds" > strokeExtent := self shape path strokeExtentFor: self shape inBounds: self localBounds. > path := self shape path pathOn: aCanvas forExtent: strokeExtent. > "Translate stroke if needed" > strokeTranslation := self shape path > strokeTranslationFor: self shape > inBounds: self localBounds. > pathTransform translateBy: strokeTranslation. > aCanvas > setPaint: self shape strokePaint; > drawShape: path ] > -- www.tudorgirba.com www.feenk.com "Sometimes the best solution is not the best solution."

Feb. 25, 2016

Re: [Pharo-dev] GTSpotter displayed shortcut glitch

by stepharo

ok Le 24/2/16 19:00, Tudor Girba a Ã©crit : > Hi, > >> On Feb 24, 2016, at 6:00 PM, stepharo <stepharo(a)free.fr> wrote: >> >> Hi doru and andrei >> >> I saw that you are displaying the shortcuts that can be used and this is good. >> Now may be I got it wrong but >> Cmd + M is not for implementors everywhere else it is Cmd + m >> Same for senders >> So I checked and Cmd + n is senders but displayed Cmd+N >> Cmd+N shows references and this is cool. > We used the same logic of displaying the keybindings as it is used in the menu. There if you have Shift, it appears explicitly. For example, for references, we have Shif+Cmd+N. I also think that we should have the letters in smallcaps, but at least now it is uniform. We can decide to change it everywhere, and I would be fine with that. > > Cheers, > Doru > >> Stef >> > -- > www.tudorgirba.com > www.feenk.com > > "Every thing has its own flow." > > > > > > >

Feb. 25, 2016

[bloc] feature envy -> move method close to data?

by stepharo

Hi Blockers I do not really understand why drawOnAthensCanvas: is not defined on BlShape (especially when we see how many self space are defined in this method. And this is one of the few things I thought I understood from bloc (grouping the rendering in a separate object). drawOnAthensCanvas: aCanvas "Actually render receiver on aCanvas in local bounds. Override to customize. aCanvas is an instance of AthensCanvas aCanvas must not be nil" | pathTransform | pathTransform := aCanvas pathTransform. "First we fill" pathTransform restoreAfter: [ | path fillExtent fillTranslation | "We fill inside natural element's bounds" fillExtent := self shape path fillExtentFor: self shape inBounds: self localBounds. path := self shape path pathOn: aCanvas forExtent: fillExtent. "Translate fill if needed" fillTranslation := self shape path fillTranslationFor: self shape inBounds: self localBounds. pathTransform translateBy: fillTranslation. aCanvas setPaint: self shape fillPaint; drawShape: path ]. pathTransform restoreAfter: [ | path strokeExtent strokeTranslation | "We stroke inside natural element's bounds" strokeExtent := self shape path strokeExtentFor: self shape inBounds: self localBounds. path := self shape path pathOn: aCanvas forExtent: strokeExtent. "Translate stroke if needed" strokeTranslation := self shape path strokeTranslationFor: self shape inBounds: self localBounds. pathTransform translateBy: strokeTranslation. aCanvas setPaint: self shape strokePaint; drawShape: path ]

Feb. 25, 2016

[bloc] why redefining new is not enough?

by stepharo

BlElement class>>basicNew "Redefined to set the space of the element" ^ super basicNew basicSpace: BlUniverse default runningSpace why redefining new is not enough? Ok now back to the mooc videos :(

Feb. 25, 2016

Re: [Pharo-dev] fork during debugging to auto spawn new debugger

by stepharo

Le 23/2/16 15:14, Denis Kudriashov a Ã©crit : > Hi Ben > > 2016-02-23 14:08 GMT+01:00 Ben Coman <btc(a)openinworld.com > <mailto:btc@openinworld.com>>: > > Maybe if somehow a Process new it was > being debugged and the new process inherited that state. > > > I plan to introduce inheriting state for spawn processes. Idea is to > add InheritedProcessSpecificVariable. > Particularly I want mark processes which was forked during test > execution and maybe manage it automatically: terminating on test > completion, collecting failures as additional test result. oh yes !!

Feb. 25, 2016

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

by stepharo

It would be ok for me. Now I need to understand how I can create a newpage in pillar Stef Le 24/2/16 20:05, Tudor Girba a Ã©crit : > 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. 25, 2016

Re: [Pharo-dev] short spotter demos

by stepharo

Thanks I was going to do some of them. So I will copy what you did. Le 24/2/16 21:38, Tudor Girba a Ã©crit : > 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. 25, 2016