March 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Did we lose edit-in-place in GT Inspector in Pharo 6?

by Tudor Girba

Hi, Indeed, this feature is temporarily not available due to the move to FastTable, but we are working on adding it back. Doru > On Mar 12, 2017, at 3:36 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Double clicking on a value in the raw tab seems to have no effect. > > p.s I asked twice in Discord with no response. I guess I'm finally getting > old enough that I don't understand how to use new platforms ;) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Did-we-lose-edit-in-place-in-GT-Inspector-in-Pharo-6-… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > -- www.tudorgirba.com www.feenk.com "It's not how it is, it is how we see it."

March 12, 2017

Did we lose edit-in-place in GT Inspector in Pharo 6?

by Sean P. DeNigris

Double clicking on a value in the raw tab seems to have no effect. p.s I asked twice in Discord with no response. I guess I'm finally getting old enough that I don't understand how to use new platforms ;) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Did-we-lose-edit-in-place-in-GT-Inspector-in-Pharo-6-… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 12, 2017

Re: [Pharo-dev] [Pharo-users] What is the craziest bug you ever face

by John Brant

> On Mar 9, 2017, at 12:50 PM, stepharong <stepharong(a)free.fr> wrote: > > The idea is that we want to see how we cn improve our debugging arsenal. > So it is important that your scenario give use some hints. > It is difficult to convey what we are really looking for :) I think one of the biggest improvements for the debugger would be for it to know the difference between my code and the system code (or not my code). Almost always, I donât want to step through any system code while debugging my code. Iâm expert enough to generally know when I should use into, over, or through, but it is a real pain to keep moving the mouse from one button to another. Often I end up hitting the wrong button by accident and have to restart the debugging process. I want a step until you come back to my code button. I think such a change would help newbies too. I donât know how much time I spent debugging though methods in OrderedCollection when I was learning Smalltalk. In over 25 years, I still havenât found a bug while stepping through OrderedCollection>>do:. Another item that Iâve thought about but have never implemented is a learning debugger. Often the hard things to debug are inside loops where you have to continuously switch between over, into and through. For example, I may know that a method is a lazy accessor and not want to step into it. However, I may want to step into the next message. A learning debugger could keep track of what I did before and do it as default the next time. Or, maybe there could be a little switch on every message send that said if you wanted over, into or through. There could also be a keep going option for all expressions. For example, I generally donât want to step through a bunch of literal assignments (e.g., âx := 4â). Such a change to the debugger would help eliminate pair debugging sessions whose conversations go like: âover, over, into, over, intoâ¦â. Such conversations donât find bugs, but are necessary to get to the location where the bug may exist. One thing that you may want in your debugging arsenal is lightweight classes to implement per object breakpoints/watchpoints. For example, you may want to set a breakpoint in a text widget. However, since that text widget is used all over, it would crash the system if you just set a breakpoint in the text widget class. Instead you can create a lightweight class with the breakpoint and change the particular text widget to use the lightweight class. This way it can trigger the breakpoint without crashing the image. I donât use lightweight classes often, but in certain cases they are really handy (and almost necessary). John Brant

March 12, 2017

Re: [Pharo-dev] Why do we have doublequoting for "?

by Tudor Girba

Hi Stef, I am still thinking about this point, but I do not have an intelligent answer yet. I just wanted to say that I did not forget it :). Cheers, Doru > On Feb 26, 2017, at 11:16 PM, stepharong <stepharong(a)free.fr> wrote: > > I hate my mail client.... > Apparently I wrote email to explain what I finally understood and it never sent it nor archive it :( > So I will try to summarize it and take some time tomorrow to reexplain it. > > Now I understand why I got confused > > printit is currently a function from > objects -> literals (this handles the self-evaluating objects) + (and this is unfortunate non literals such as string objects by opposition to literal strings) > > It means that there ares case where we can have > object -> a string object (and not a literal) in that case we use the string object as a mediocre "reference" to the object. > > > If we would have > printgraphics > we would have objects -> graphics and unknow objects would be represented by a little blue square and clicking on it would bring > and object representation (inspectors or whatever) > > Now how to we improve the situation. I have the impression that it would be good to have instead of printOn: which is used to do too many things. > > - first printOn: should not be used for list/combo or any widgets (this will avoid some friends I know to get interfaces with ' inside their comboxchoice) but to use displayString > > - second I would introduce > asLiteralOn: > which garantee that you cannot escape > > this way printIt will only prints strings as literal strings and the contract is clear. > > objects -> literals (this handles the self-evaluating objects) > > 1 > >>> 1 > > false > >>> > false > > but > (Directory name: 'comics') > >>> 'comics' > > { 1 . Browser new} > >>> 'anArray with (1, a Browser') > > now we can ask ourselves if > > { (Directory name: 'comics') } > >>> > { 'comics' } I do not like it > or > >>> 'anArray with ( comics ) > > > back to my confusion: > > I was confused about the fact that I was hijacking the textual representation > 'comics' is not a directory but a string > now may be I should have return a storeOn: representation > or 'aDirectory (comics)' > > and introduce displayString > 'comics' > > Probably that printOn: should not be used the way I did it. > but I do not know. > > I think that this is a subtle domain and we should provide better guidelines. > > Do you understand my points? > What do you think? > > Stef -- www.tudorgirba.com www.feenk.com "Presenting is storytelling."

March 11, 2017

Re: [Pharo-dev] Debugger: is there a way to skip a message?

by Tudor Girba

Oh, maybe âReturn entered valueâ is what Stef was looking for. If yes, you can obtain it from the contextual menu of the Stack. Cheers, Doru > On Mar 11, 2017, at 3:03 PM, Ben Coman <btc(a)openInWorld.com> wrote: > > On Sat, Mar 11, 2017 at 4:20 AM, stepharong <stepharong(a)free.fr> wrote: >> Hi >> >> I need to skip message while debugging and I thought that it was possible. >> May be I do not see it. > > This would be a nice feature. I never noticed if we ever had it > Two work arounds I sometimes use... > * select rest of the method and "Debug It". > * step-Into, and then "Return entered value" > > cheer -ben > -- www.tudorgirba.com www.feenk.com "Every thing should have the right to be different."

March 11, 2017

Re: [Pharo-dev] 60437 empty catalog

by Ben Coman

On Sat, Mar 11, 2017 at 10:41 PM, David T. Lewis <lewis(a)mail.msen.com> wrote: > On Sat, Mar 11, 2017 at 10:14:58PM +0800, Ben Coman wrote: >> Anyone else getting an empty Catalog? >> >> In 60437 & CoInterpreter * VMMaker.oscog-eem.2143 uuid: >> fe064b6b-e530-4766-837d-799ffe1e8dcd Mar 3 2017 >> (i386itimer-201703031554.zip) >> >> Sorry I'm too tired to bisect it myself right now. >> (Just spent 10 hours sanding the wooden floors of my brothers house) >> > > It looks ok to me. Try deleting the file from your local package cache, > sometime an error condition can leave junk there. Thanks Dave. Testing again, from PharoLauncher I do... Local/60437 > "Create an Image" which essentially unzips 60437.zip with an empty package cache, then Existing Images > 60437-01 > Launch. Tools > Catalog ==> still empty. PharoLauncher settings... * Spur VM Full Path = /home/ben/.local/share/Pharo/VMs/i386itimer-201703031554/pharo downloaded from... * http://files.pharo.org/vm/pharo-spur32/linux/pharo-linux-i386itimer-2017030… cheers -ben

March 11, 2017

Re: [Pharo-dev] 60437 empty catalog

by David T. Lewis

On Sat, Mar 11, 2017 at 10:14:58PM +0800, Ben Coman wrote: > Anyone else getting an empty Catalog? > > In 60437 & CoInterpreter * VMMaker.oscog-eem.2143 uuid: > fe064b6b-e530-4766-837d-799ffe1e8dcd Mar 3 2017 > (i386itimer-201703031554.zip) > > Sorry I'm too tired to bisect it myself right now. > (Just spent 10 hours sanding the wooden floors of my brothers house) > It looks ok to me. Try deleting the file from your local package cache, sometime an error condition can leave junk there. Dave

March 11, 2017

60437 empty catalog

by Ben Coman

Anyone else getting an empty Catalog? In 60437 & CoInterpreter * VMMaker.oscog-eem.2143 uuid: fe064b6b-e530-4766-837d-799ffe1e8dcd Mar 3 2017 (i386itimer-201703031554.zip) Sorry I'm too tired to bisect it myself right now. (Just spent 10 hours sanding the wooden floors of my brothers house) cheers -ben

March 11, 2017

Re: [Pharo-dev] Debugger: is there a way to skip a message?

by Ben Coman

On Sat, Mar 11, 2017 at 4:20 AM, stepharong <stepharong(a)free.fr> wrote: > Hi > > I need to skip message while debugging and I thought that it was possible. > May be I do not see it. This would be a nice feature. I never noticed if we ever had it Two work arounds I sometimes use... * select rest of the method and "Debug It". * step-Into, and then "Return entered value" cheer -ben

March 11, 2017

what is the SpecLayout architecture?

by Peter Uhnak

Hi, this is probably a tall order, but is there some description of SpecLayout architecture? To clarify: I am NOT asking how to use SpecLayout, I am asking how SpecLayout works internally. iirc SpecInterpreter was rewritten by Johan & Stef, so maybe you guys have some notes? Thanks, Peter

March 11, 2017