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

Re: [Pharo-dev] Halt once

by Sven Van Caekenberghe

Can't Menu Item not be found with Spotter ? > On 10 Oct 2016, at 02:11, Ben Coman <btc(a)openinworld.com> wrote: > > In Pharo 6 I got stuck on the same and after some delay found it under > the World > Debugger menu. > It would be nice if such rearrangement of UI elements were announced > more obviously on the mail list. > cheers -ben > > On Mon, Oct 10, 2016 at 4:38 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: >> Why no menu anymore? >> >> Phil >> >> On Sun, Oct 9, 2016 at 9:26 PM, stepharo <stepharo(a)free.fr> wrote: >>> >>> Hi guys >>> >>> we can do better in terms of comments. >>> >>> https://pharo.fogbugz.com/f/cases/19193/Halt-once-comment-mega-sucks >>> >>> In Pharo 60 I tried to use Halt once. >

Oct. 10, 2016

Re: [Pharo-dev] Halt once

by Ben Coman

In Pharo 6 I got stuck on the same and after some delay found it under the World > Debugger menu. It would be nice if such rearrangement of UI elements were announced more obviously on the mail list. cheers -ben On Mon, Oct 10, 2016 at 4:38 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Why no menu anymore? > > Phil > > On Sun, Oct 9, 2016 at 9:26 PM, stepharo <stepharo(a)free.fr> wrote: >> >> Hi guys >> >> we can do better in terms of comments. >> >> https://pharo.fogbugz.com/f/cases/19193/Halt-once-comment-mega-sucks >> >> In Pharo 60 I tried to use Halt once.

Oct. 10, 2016

Re: [Pharo-dev] Halt once

by Ben Coman

On Mon, Oct 10, 2016 at 3:26 AM, stepharo <stepharo(a)free.fr> wrote: > Hi guys > > we can do better in terms of comments. > > https://pharo.fogbugz.com/f/cases/19193/Halt-once-comment-mega-sucks > > In Pharo 60 I tried to use Halt once. > > There is no menu to set it up anymore so I looked in the class ... :( > > What a supercool and welcoming comment > > Halt is provided to support Object>>halt. > > once > | callingContext senderContext node | > <debuggerCompleteToSender> I touched that last so I'll take it on the chin. I guess there were no comments before I updated it and was complacent about comments status quo. Freshening up existing comments (or lack of) hasn't been in the forefront of my mind, but you are right, modifying an existing method is a good opportunity to improve comments. cheers -ben

Oct. 10, 2016

Re: [Pharo-dev] Halt once

by phil＠highoctane.be

Why no menu anymore? Phil On Sun, Oct 9, 2016 at 9:26 PM, stepharo <stepharo(a)free.fr> wrote: > Hi guys > > we can do better in terms of comments. > > https://pharo.fogbugz.com/f/cases/19193/Halt-once-comment-mega-sucks > > In Pharo 60 I tried to use Halt once. > > There is no menu to set it up anymore so I looked in the class ... :( > > What a supercool and welcoming comment > > Halt is provided to support Object>>halt. > > once > | callingContext senderContext node | > <debuggerCompleteToSender> > > resetOnce > (#haltOnce senders, #inspectOnce senders) do: [ :method | > method ast sendNodes do: [ :sendNode| > sendNode removeProperty: #Once ifAbsent: [ ]]] > > Not a single comment! > I'm sure that we can do a lot better and think to all the newbies that > will check pharo. > > Please comments such methods and class. > > Stef > >

Oct. 9, 2016

Re: [Pharo-dev] Halt once

by stepharo

I submitted this as class comment. Halt is a special exception provided to support breakpoints as defined in Object>>halt. !! Basic usage To manually set a breakpoint you can use message halt as follows: [[[ anObject halt. ]]] You can also use [[[ Halt now ]]] [[[ Halt now: 'With a nice explanation' ]]] !! Advanced usage The class Halt supports different halting mechanisms such as conditionals, based on iteration or simply stopping the first time. !!! Conditionals [[[ foo ... Halt if: #invokedFromThisSelector ]]] This expression will only stop the execution of method foo if this method is in the call chain (is invoked from ) message invokedFromThisSelector. [[[ foo ... Halt if: aBlock ]]] The execution of foo will stop if aBlock returns true. !!! Counting Sometimes we need to stop after a given number of iteration. [[[ Halt count: 5 ]]] !!! Once It is really useful sometimes to stop only and only one time [[[ foo ... Halt once. ]]] It will be stopped the first time. Then if you need to rearm it to stop another time you should use [[[ Halt resetOnce ]]]

Oct. 9, 2016

Halt once

by stepharo

Hi guys we can do better in terms of comments. https://pharo.fogbugz.com/f/cases/19193/Halt-once-comment-mega-sucks In Pharo 60 I tried to use Halt once. There is no menu to set it up anymore so I looked in the class ... :( What a supercool and welcoming comment Halt is provided to support Object>>halt. once | callingContext senderContext node | <debuggerCompleteToSender> resetOnce (#haltOnce senders, #inspectOnce senders) do: [ :method | method ast sendNodes do: [ :sendNode| sendNode removeProperty: #Once ifAbsent: [ ]]] Not a single comment! I'm sure that we can do a lot better and think to all the newbies that will check pharo. Please comments such methods and class. Stef

Oct. 9, 2016

Re: [Pharo-dev] Talk at Google Devdays BE accepted

by Esteban Lorenzano

this is very good Phil. this kind of presentations are what we need to expand the community :) please keep us in touch :) Esteban > On 9 Oct 2016, at 10:48, phil(a)highoctane.be wrote: > > Check 14h50 > > https://devfest.be/schedule/day1 <https://devfest.be/schedule/day1> > > <image.png> > > Question: does anyone here has made some integration with Angular (1.x) in Seaside? > I mean tag brushes for ng-app and possible other interesting associated features (like passing parms from a component to the ng-app parms, having angular service calling in Pharo Seaside callbacks etc)? > > Would be nice to have a few extra Google-centric things to show. > > > Phil > > > On Sat, Oct 8, 2016 at 6:59 PM, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: > super cool :) > > You should contact cyril because he once explained to me that the pharo version was better > > than the google one (but now they released a new version). > > > Le 7/10/16 Ã 14:03, phil(a)highoctane.be <mailto:phil@highoctane.be> a Ã©crit : > > Title is Material Design Lite in Pharo. > > Phil > > > >

Oct. 9, 2016

Re: [Pharo-dev] Talk at Google Devdays BE accepted

by phil＠highoctane.be

Check 14h50 https://devfest.be/schedule/day1 [image: Inline image 1] Question: does anyone here has made some integration with Angular (1.x) in Seaside? I mean tag brushes for ng-app and possible other interesting associated features (like passing parms from a component to the ng-app parms, having angular service calling in Pharo Seaside callbacks etc)? Would be nice to have a few extra Google-centric things to show. Phil On Sat, Oct 8, 2016 at 6:59 PM, stepharo <stepharo(a)free.fr> wrote: > super cool :) > > You should contact cyril because he once explained to me that the pharo > version was better > > than the google one (but now they released a new version). > > > Le 7/10/16 Ã 14:03, phil(a)highoctane.be a Ã©crit : > >> >> Title is Material Design Lite in Pharo. >> >> Phil >> >> > >

Oct. 9, 2016

Re: [Pharo-dev] [ANN] Tealight

by Attila Magyar

Nice extension. Thanks. -- View this message in context: http://forum.world.st/ANN-Tealight-tp4918431p4918455.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 8, 2016

Re: [Pharo-dev] Path >> fullName should not be the same as printString

by Damien Pollet

It's a breaking change and I don't know if there's a way to do it with proper deprecationâ¦ my hope is that there are not many users of it, but I haven't checked yet. Any opinions among users of FileSystem? On 8 October 2016 at 19:12, stepharo <stepharo(a)free.fr> wrote: > So damien what is the solution? > > > > Le 7/10/16 Ã 18:18, Damien Pollet a Ã©crit : > > Path >> printString returns a self-evaluating representation, which is > fine. Its symmetric is thus Compiler >> evaluate: aString. > > (Path from: aString) parses the unix/url representation of a path and > results in a Path instance. As far as I understand, #fullName should be the > symmetric of that, so that we always have (modulo syntactic normalization, > maybe) : > > (Path from: aString) fullName = aString > > Note that there's an edge case with the empty string that is wrong (at > least it should be confusing to unix guys): > > Path from: ''. "Path root" > > Usually the absolute path for the root of the filesystem is explicitly > noted '/', and an empty path is equivalent to '.' > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > > > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Oct. 8, 2016