December 2013 - Pharo-dev - lists.pharo.org

Pharo on #code2013

by Yuriy Tymchuk

Letâs promote Pharo by tweeting: âPharo #code2013â Cheers! Happy new year. Uko

Dec. 31, 2013

Re: [Pharo-dev] debugger broken?

by StÃ©phane Ducasse

Alex this is not the debugger this is the selection Have a look at issue 12144 load it and tell us. Now we have a problem of instability of the latest vm on our servers so the integration is stalled. I spent 3 hours yesterday trying to move on and we will rollback to an older VM. Stef On 30 Dec 2013, at 23:02, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > I have faced a serious situation with the debugger today with Pharo 3.0: > 1 - Open a workspace, and doit on the expression: 1 + 4. self halt > 2 - Open the debugger, select with the mouse the expression 1 + 4 and press Cmd-p > 3 - the debugger apparently consider the word halt as a variable. > > https://pharo.fogbugz.com/f/cases/12545/Debugger-broken > > Since I am using GTDebugger (in the Moose image), I have not seen it before... > > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Dec. 31, 2013

Re: [Pharo-dev] debugger broken?

by Alexandre Bergel

Thanks Nicolai Alexandre > Le 30-12-2013 Ã 19:37, Nicolai Hess <nicolaihess(a)web.de> a Ã©crit : > > Actually it is the text selection that is broken, > > caused by 12144 and will be fixed with 12521 (waits for integration). > > BTW, I don't know if it is platform related, but on windows you can actually > use CMD-P (ALT-P) for "print it", just using "print it" from the menu does not work. > > Nicolai > > > > > 2013/12/30 Alexandre Bergel <alexandre.bergel(a)me.com> >> Hi! >> >> I have faced a serious situation with the debugger today with Pharo 3.0: >> 1 - Open a workspace, and doit on the expression: 1 + 4. self halt >> 2 - Open the debugger, select with the mouse the expression 1 + 4 and press Cmd-p >> 3 - the debugger apparently consider the word halt as a variable. >> >> https://pharo.fogbugz.com/f/cases/12545/Debugger-broken >> >> Since I am using GTDebugger (in the Moose image), I have not seen it before... >> >> Cheers, >> Alexandre >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >

Dec. 31, 2013

Re: [Pharo-dev] towards moose in the pharo ide (gtinspector / gtdebugger)

by Alexandre Bergel

I am quasi exclusively using the Moose image, which includes GTDebugger and GTInspector. These are two great tools. I use the standard Pharo 3.0 for particular needs only. When I do this, it is like using Nautilus and coming back to OB (or even the old standard browser). GTDebugger and GTInspector are great. I like them. Alexandre On Dec 30, 2013, at 2:24 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Some of you asked how the GTInspector and GTDebugger are different from the existing infrastructure. They are quite different from the norm in that: they are tiny, and they are highly extensible. Here are some posts that describe what makes them different: > > http://www.humane-assessment.com/blog/the-moldable-gtinspector-deconstructe… > http://www.humane-assessment.com/blog/dissecting-the-gtinspector/ > http://www.humane-assessment.com/blog/extending-variables-shown-in-gtinspec… > http://www.humane-assessment.com/blog/moldable-gtdebugger > > These tools are already the default development tools in the Moose image. As you can see, Moose is reshaping the Pharo IDE. I think this is exciting. > > This should be just the beginning. To make it better, we need your energy: > - Apply and extend these tools for your context (this is what makes them unique). > - Tell us what works and what does not work. > - Ideally, start working with us on this topic. In particular, I am looking for people that would like to spend some time working on Morphic widgets. > > It's your turn now. > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 30, 2013

Re: [Pharo-dev] debugger broken?

by Nicolai Hess

Actually it is the text selection that is broken, caused by 12144 <https://pharo.fogbugz.com/default.asp?12144> and will be fixed with 12521 <https://pharo.fogbugz.com/default.asp?12521> (waits for integration). BTW, I don't know if it is platform related, but on windows you can actually use CMD-P (ALT-P) for "print it", just using "print it" from the menu does not work. Nicolai <https://pharo.fogbugz.com/default.asp?12521> 2013/12/30 Alexandre Bergel <alexandre.bergel(a)me.com> > Hi! > > I have faced a serious situation with the debugger today with Pharo 3.0: > 1 - Open a workspace, and doit on the expression: 1 + 4. self halt > 2 - Open the debugger, select with the mouse the expression 1 + 4 and > press Cmd-p > 3 - the debugger apparently consider the word halt as a variable. > > https://pharo.fogbugz.com/f/cases/12545/Debugger-broken > > Since I am using GTDebugger (in the Moose image), I have not seen it > before... > > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Dec. 30, 2013

debugger broken?

by Alexandre Bergel

Hi! I have faced a serious situation with the debugger today with Pharo 3.0: 1 - Open a workspace, and doit on the expression: 1 + 4. self halt 2 - Open the debugger, select with the mouse the expression 1 + 4 and press Cmd-p 3 - the debugger apparently consider the word halt as a variable. https://pharo.fogbugz.com/f/cases/12545/Debugger-broken Since I am using GTDebugger (in the Moose image), I have not seen it before... Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 30, 2013

Re: [Pharo-dev] FogBugz status change

by StÃ©phane Ducasse

> If Linus Torvald is your model, then I quit Pharo :P I will tell you stories where democracy in open-source does not work in feb. :P Stef

Dec. 30, 2013

Re: [Pharo-dev] Spotlight Demo

by StÃ©phane Ducasse

Sounds really cool and yes the new ide guys wanted a widgets and behavior like that. How about to add Packages? > I needed an entry completion with groups, like Mac's Spotlight. While I was at it, I figured it would also be useful as a UI for the existing Spotlight. So I made a SpotlightMorph, which is a very Mac-like stand-alone Morph, which is a textField + results morph, and an adaptor for EntryCompetion, SpotlightEntryCompletion, which can be passed to #entryCompletion: > > A short screencast will be available at https://vimeo.com/82953583 in about 45 minutes. > > And here's a screenshot for the impatient ;) > > <Screen Shot 2013-12-30 at 9.23.02 AM.png> > > To load (tested in Pharo 2.0 latest): > Gofer it > smalltalkhubUser: 'SeanDeNigris' project: 'SeansPlayground'; > package: 'Spotlight'; > load. > > Then try: > SpotlightCompletionExample open. > or > SpotlightMorphExample exampleFileSearch. > or > SpotlightMorphExample exampleSmalltalkSearch.

Dec. 30, 2013

Re: [Pharo-dev] Thank you for Pharo

by StÃ©phane Ducasse

Thanks we hope that you will help us taking what is good from python (I have a long list of good and bad but the problem is that our community is not large enough yet). Stef On 30 Dec 2013, at 16:03, kilon alios <kilon.alios(a)gmail.com> wrote: > " We all appreciate when Pharo is useful. But it is not yet finished (if it ever will) and you are welcome to help moving it forward as > yet another crazy guy. Step by step it goes ..." > > Fortunately their are plenty of "crazy" people to prove "logical" people wrong and drive progress forward. > > Here is a nice article about them. > > http://listverse.com/2007/10/28/top-30-failed-technology-predictions/ > > I will also like to thank pharo people for their work. Sorry if I have replied to this thread before I have a bad memory. > > I started pharo like a "crazy" experiment, I never expected that I would abandon a well established , supported and popular programming language like python for pharo. > > The plan was simple to "steal ideas" from pharo and port them to python on the premise that I would like several things that would be doable by one person. Then I discovered more and more things I liked that became complete insane to even imagine that I could port all these things to python. I certainly did not want to abandon the comfort of python and learn things from scratch but I was completely hooked with how amazing pharo is. So here I am, I only hope I do my very small part to push pharo forward, with my project Ephestos and small bug fixes here and there. Still long way to go to really understand pharo and its libraries but as you so wisely said step by step I am moving forward and that can only be a good thing. >

Dec. 30, 2013

Re: [Pharo-dev] Pharo3 issues

by StÃ©phane Ducasse

> Hi Nicolai, > > On 30 Dec 2013, at 13:26, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> for issue 12223 >> >> please revert the changes done for editing history in Nautilus. >> It makes more trouble than it helps. >> It is a nice feature, but it is implementation has too many side effects (discard changes on close, lose changes when jump through the >> history, history has a limit) >> If no one has the time to revert this, just give me a GO, and I'll do it :-) >> >> >> Nicolai > > Yes, I think that features has given us a lot of trouble already, I concur with your conclusion: revert. Please :) > > Another thing I have been wanting to say to you: I am very impressed and very happy to see you tackle so many diverse issues with so much energy. You really embody the âjust doItâ tagline. + 1 :) > Thank you very much, I for one, appreciate it a lot ! Yes me too. > > Regards, > > Sven > > BTW, from my perspective you seem to have come from nowhere, which makes your contributions even more magical. > >> >> 2013/12/30 Marcus Denker <marcus.denker(a)inria.fr> >> >> On 30 Dec 2013, at 12:38, jannik.laval <jannik.laval(a)gmail.com> wrote: >> >>> Hi all, >>> >>> I am porting Phratch in Pharo 3.0 and I have some problems with the interface. >>> I uses a one-click Pharo3.0 #30664 >>> >>> Here is a list of what I have: >>> >>> - in a debugger, it is not possible to do a Cmd-p to evaluate an expression. This appears only if I select with the mouse. If I make the selection with shift-arrow it works. >>> It means that the selection with mouse or with shift-arrow are not the same. >>> >> yes, known bug. Introduced by 12144 TextModel>>getSelection. The only solution seems to be to revert tag for now: >> >> https://pharo.fogbugz.com/f/cases/12521/Undo-12144-TextModel-getSelection >> >> This will be in the next update. (I was offline more or less since thursday due to helping my brother moving, so this is not integrated yet) >> >>> - In monticello browser: when I select my project, all the repositories available in Pharo are shown. As in Pharo 2.0, it should show only the concerned repositories (2 or 3 max). >>> >> Yes, this was made on purpose and there is an issue that questions if that idea was good: >> >> https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-add… >> (this issue is from July) >> >> >>> - In a browser, when I did a change in the source code of a method, then I select another method, the changes are lost, without asking if I want to save changes. >>> >> >> https://pharo.fogbugz.com/f/cases/12223/Nautilus-loses-changes >> (issue date: 22/11) >> >> In short: if there would be more people *actively* helping on the issue tracker front, you would not even have seen those problems. >> >> >> Marcus >> > > > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org

Dec. 30, 2013