April 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] why we removed debugTest from nautilus?

by kilon alios

+1 On Sat, Apr 11, 2015 at 3:58 PM, Max Leske <maxleske(a)gmail.com> wrote: > > On 11 Apr 2015, at 10:10, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2015-04-10 17:28 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: > >> Well I guess I used to click proceed and not close the debugger... >> > > > I don't know who is working on the breakpoint support and I don't know how > long it will take. > Maybe we can fix thie image freeze and re-include the debugtest code until > the new breakpoint support. > > what do you think? > > > I would love that. I know a couple of people who already complained about > the test debug feature missing and I think that said feature is really an > important point of the IDE. That being said, it will probably mean delaying > the release another week or two. Then again, releasing something in a good > state is better IMHO than releasing on time. > > Cheers, > Max > > > > >> >> 2015-04-10 1:24 GMT-07:00 Max Leske <maxleske(a)gmail.com>: >> >> For a little more context: the issue was originally raised by Clara in >>> the thread titled "MNU: receiver of "stepToCallee:" is nilâ. IIRC the >>> issue was easily reproducible when debugging a test, then closing the >>> debugger (via the close icon). Clicking âProceedâ on the other hand >>> gracefully terminated the process. >>> >>> Cheers, >>> Max >>> >>> >>> On 10 Apr 2015, at 09:56, Nicolai Hess <nicolaihess(a)web.de> wrote: >>> >>> 2015-04-10 2:37 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: >>> >>>> I was using it frequently too and I have never experienced any issues... >>>> >>> >>> Ok, can you describe a use case, what test case you can start and >>> close the debugger without image freeze? >>> >>> Maybe we can find what is the difference between that >>> test case and those that freeze the image, and than find a fix. >>> >>> >>>> >>>> 2015-04-09 14:58 GMT-07:00 Nicolai Hess <nicolaihess(a)web.de>: >>>> >>>> >>>>> 2015-04-09 23:38 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: >>>>> >>>>>> No Debug Tests? >>>>>> >>>>>> Geez, I am using that all the time. >>>>>> >>>>> >>>>> And you're never encountered this issue 14689 >>>>> <https://pharo.fogbugz.com/default.asp?14689>? >>>>> Or did this work in older versions? >>>>> >>>>> >>>>> >>>>> >>>>>> >>>>>> Phil >>>>>> >>>>>> >>>>>> On Thu, Apr 9, 2015 at 10:21 PM, Marcus Denker < >>>>>> marcus.denker(a)inria.fr> wrote: >>>>>> >>>>>>> >>>>>>> > On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean(a)clipperadams.com> >>>>>>> wrote: >>>>>>> > >>>>>>> > Nicolai Hess wrote >>>>>>> >> >>>>>>> http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-… >>>>>>> > >>>>>>> > Ah, I miss that too! From that thread, it seems it was removed >>>>>>> temporarily >>>>>>> > until we have real breakpoints. Is there an issue for its return? >>>>>>> > >>>>>>> >>>>>>> Not yet. >>>>>>> >>>>>>> Marcus >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >>> >> > >

April 11, 2015

Re: [Pharo-dev] why we removed debugTest from nautilus?

by Max Leske

> On 11 Apr 2015, at 10:10, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2015-04-10 17:28 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com <mailto:bera.clement@gmail.com>>: > Well I guess I used to click proceed and not close the debugger... > > > I don't know who is working on the breakpoint support and I don't know how long it will take. > Maybe we can fix thie image freeze and re-include the debugtest code until the new breakpoint support. > > what do you think? I would love that. I know a couple of people who already complained about the test debug feature missing and I think that said feature is really an important point of the IDE. That being said, it will probably mean delaying the release another week or two. Then again, releasing something in a good state is better IMHO than releasing on time. Cheers, Max > > > > 2015-04-10 1:24 GMT-07:00 Max Leske <maxleske(a)gmail.com <mailto:maxleske@gmail.com>>: > > For a little more context: the issue was originally raised by Clara in the thread titled "MNU: receiver of "stepToCallee:" is nilâ. IIRC the issue was easily reproducible when debugging a test, then closing the debugger (via the close icon). Clicking âProceedâ on the other hand gracefully terminated the process. > > Cheers, > Max > > >> On 10 Apr 2015, at 09:56, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: >> >> 2015-04-10 2:37 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com <mailto:bera.clement@gmail.com>>: >> I was using it frequently too and I have never experienced any issues... >> >> Ok, can you describe a use case, what test case you can start and >> close the debugger without image freeze? >> >> Maybe we can find what is the difference between that >> test case and those that freeze the image, and than find a fix. >> >> >> 2015-04-09 14:58 GMT-07:00 Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>>: >> >> >> 2015-04-09 23:38 GMT+02:00 phil(a)highoctane.be <mailto:phil@highoctane.be> <phil(a)highoctane.be <mailto:phil@highoctane.be>>: >> No Debug Tests? >> >> Geez, I am using that all the time. >> >> And you're never encountered this issue 14689 <https://pharo.fogbugz.com/default.asp?14689>? >> Or did this work in older versions? >> >> >> >> >> Phil >> >> >> On Thu, Apr 9, 2015 at 10:21 PM, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> >> > On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean(a)clipperadams.com <mailto:sean@clipperadams.com>> wrote: >> > >> > Nicolai Hess wrote >> >> http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-… <http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-…> >> > >> > Ah, I miss that too! From that thread, it seems it was removed temporarily >> > until we have real breakpoints. Is there an issue for its return? >> > >> >> Not yet. >> >> Marcus >> >> >> >> > > >

April 11, 2015

Re: [Pharo-dev] why we removed debugTest from nautilus?

by Ben Coman

I miss it. I think I remember that a <Restart> <Close> would work, so a hack fix could be the do a restart when the close button is pushed. Reintroducing it with the problem fixed would be welcome. cheers -ben On Sat, Apr 11, 2015 at 4:10 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > 2015-04-10 17:28 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: > >> Well I guess I used to click proceed and not close the debugger... >> > > > I don't know who is working on the breakpoint support and I don't know how > long it will take. > Maybe we can fix thie image freeze and re-include the debugtest code until > the new breakpoint support. > > what do you think? > > > >> >> 2015-04-10 1:24 GMT-07:00 Max Leske <maxleske(a)gmail.com>: >> >> For a little more context: the issue was originally raised by Clara in >>> the thread titled "MNU: receiver of "stepToCallee:" is nilâ. IIRC the >>> issue was easily reproducible when debugging a test, then closing the >>> debugger (via the close icon). Clicking âProceedâ on the other hand >>> gracefully terminated the process. >>> >>> Cheers, >>> Max >>> >>> >>> On 10 Apr 2015, at 09:56, Nicolai Hess <nicolaihess(a)web.de> wrote: >>> >>> 2015-04-10 2:37 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: >>> >>>> I was using it frequently too and I have never experienced any issues... >>>> >>> >>> Ok, can you describe a use case, what test case you can start and >>> close the debugger without image freeze? >>> >>> Maybe we can find what is the difference between that >>> test case and those that freeze the image, and than find a fix. >>> >>> >>>> >>>> 2015-04-09 14:58 GMT-07:00 Nicolai Hess <nicolaihess(a)web.de>: >>>> >>>> >>>>> 2015-04-09 23:38 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: >>>>> >>>>>> No Debug Tests? >>>>>> >>>>>> Geez, I am using that all the time. >>>>>> >>>>> >>>>> And you're never encountered this issue 14689 >>>>> <https://pharo.fogbugz.com/default.asp?14689>? >>>>> Or did this work in older versions? >>>>> >>>>> >>>>> >>>>> >>>>>> >>>>>> Phil >>>>>> >>>>>> >>>>>> On Thu, Apr 9, 2015 at 10:21 PM, Marcus Denker < >>>>>> marcus.denker(a)inria.fr> wrote: >>>>>> >>>>>>> >>>>>>> > On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean(a)clipperadams.com> >>>>>>> wrote: >>>>>>> > >>>>>>> > Nicolai Hess wrote >>>>>>> >> >>>>>>> http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-… >>>>>>> > >>>>>>> > Ah, I miss that too! From that thread, it seems it was removed >>>>>>> temporarily >>>>>>> > until we have real breakpoints. Is there an issue for its return? >>>>>>> > >>>>>>> >>>>>>> Not yet. >>>>>>> >>>>>>> Marcus >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >>> >> >

April 11, 2015

Re: [Pharo-dev] Problem during the loading of setting on Pharo 4

by Tudor Girba

Hi, This is because you exported all your settings previously and in the meantime, this particular setter has changed to cacheDirectory:. This is a systematic problem with the current setting mechanism and we will have to deal with it after the Pharo 4 release. To circumvent the problem for now, I have added a backward compatible customDirectory: setter. It is available in the latest GT-Playground and will be integrated in Pharo 4: Name: GT-Playground-TudorGirba.110 Author: TudorGirba Time: 11 April 2015, 2:18:59.123037 pm UUID: 58b68605-0af7-4854-be65-b3cda2385cef Ancestors: GT-Playground-TudorGirba.109 introduced customDirectory: for backward compatibility Cheers, Doru On Fri, Apr 10, 2015 at 4:59 PM, Ferlicot D. Cyril <cyril.ferlicot(a)gmail.com > wrote: > Hi ! > I use Pharo Launcher and each time I open a new Pharo 4 image, this image > load my Pharo 4 settings. But since the version 40601 when Pharo load the > settings i've an error: "MessageNotUnderstood: GTPlayBook class>> > customDirectory:". > > If others have the same problem i'll open a bug repport. > > -- www.tudorgirba.com "Every thing has its own flow"

April 11, 2015

Re: [Pharo-dev] Nautilus: Why is Search Field Pre-filled?

by Peter UhnÃ¡k

> > It is considered as a feature :) >> (14634 <https://pharo.fogbugz.com/default.asp?14634> Package Filter in >> Nautilus should use the last used filter when a new window is opened) >> > I think this also answers Sean's original question. Peter (note to self: do not use reply-to-all; sorry Nicolai :))

April 11, 2015

Re: [Pharo-dev] Nautilus: Why is Search Field Pre-filled?

by Peter UhnÃ¡k

On Sat, Apr 11, 2015 at 10:59 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > 2015-04-11 9:27 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > >> I think there is a problem with it... >> if I browse a class with shortcut "ctrl+b", then the name of the package >> where the class is is added to the search. >> This at least to me quite annoying as I often do lookups of other classes >> but I am not interested in the whole package... so every so often I have to >> clear it. >> Is this a bug or a feature? >> > > It is considered as a feature :) > (14634 <https://pharo.fogbugz.com/default.asp?14634> Package Filter in > Nautilus should use the last used filter when a new window is opened) > I don't know, to me it looks like side effect, I'll ask Juraj. Peter > > > > >> >> Peter >> >> On Sat, Apr 11, 2015 at 8:12 AM, stepharo <stepharo(a)free.fr> wrote: >> >>> when you type a search and close the browser and reopen it you do not >>> have to retype again and again. >>> We should revisit this pane >>> because we could have a plus/pin button that logs the previous search. >>> >>> Stef >>> >>> Le 11/4/15 04:54, Sean P. DeNigris a Ã©crit : >>> >>> What is the rationale? I don't like it. >>>> >>>> >>>> >>>> ----- >>>> Cheers, >>>> Sean >>>> -- >>>> View this message in context: http://forum.world.st/ >>>> Nautilus-Why-is-Search-Field-Pre-filled-tp4819003.html >>>> Sent from the Pharo Smalltalk Developers mailing list archive at >>>> Nabble.com. >>>> >>>> >>>> >>> >>> >> >

April 11, 2015

Re: [Pharo-dev] Nautilus: Why is Search Field Pre-filled?

by Nicolai Hess

2015-04-11 9:27 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > I think there is a problem with it... > if I browse a class with shortcut "ctrl+b", then the name of the package > where the class is is added to the search. > This at least to me quite annoying as I often do lookups of other classes > but I am not interested in the whole package... so every so often I have to > clear it. > Is this a bug or a feature? > It is considered as a feature :) (14634 <https://pharo.fogbugz.com/default.asp?14634> Package Filter in Nautilus should use the last used filter when a new window is opened) > > Peter > > On Sat, Apr 11, 2015 at 8:12 AM, stepharo <stepharo(a)free.fr> wrote: > >> when you type a search and close the browser and reopen it you do not >> have to retype again and again. >> We should revisit this pane >> because we could have a plus/pin button that logs the previous search. >> >> Stef >> >> Le 11/4/15 04:54, Sean P. DeNigris a Ã©crit : >> >> What is the rationale? I don't like it. >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> View this message in context: http://forum.world.st/ >>> Nautilus-Why-is-Search-Field-Pre-filled-tp4819003.html >>> Sent from the Pharo Smalltalk Developers mailing list archive at >>> Nabble.com. >>> >>> >>> >> >> >

April 11, 2015

Re: [Pharo-dev] why we removed debugTest from nautilus?

by Nicolai Hess

2015-04-10 17:28 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: > Well I guess I used to click proceed and not close the debugger... > I don't know who is working on the breakpoint support and I don't know how long it will take. Maybe we can fix thie image freeze and re-include the debugtest code until the new breakpoint support. what do you think? > > 2015-04-10 1:24 GMT-07:00 Max Leske <maxleske(a)gmail.com>: > > For a little more context: the issue was originally raised by Clara in the >> thread titled "MNU: receiver of "stepToCallee:" is nilâ. IIRC the issue >> was easily reproducible when debugging a test, then closing the debugger >> (via the close icon). Clicking âProceedâ on the other hand gracefully >> terminated the process. >> >> Cheers, >> Max >> >> >> On 10 Apr 2015, at 09:56, Nicolai Hess <nicolaihess(a)web.de> wrote: >> >> 2015-04-10 2:37 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: >> >>> I was using it frequently too and I have never experienced any issues... >>> >> >> Ok, can you describe a use case, what test case you can start and >> close the debugger without image freeze? >> >> Maybe we can find what is the difference between that >> test case and those that freeze the image, and than find a fix. >> >> >>> >>> 2015-04-09 14:58 GMT-07:00 Nicolai Hess <nicolaihess(a)web.de>: >>> >>> >>>> 2015-04-09 23:38 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: >>>> >>>>> No Debug Tests? >>>>> >>>>> Geez, I am using that all the time. >>>>> >>>> >>>> And you're never encountered this issue 14689 >>>> <https://pharo.fogbugz.com/default.asp?14689>? >>>> Or did this work in older versions? >>>> >>>> >>>> >>>> >>>>> >>>>> Phil >>>>> >>>>> >>>>> On Thu, Apr 9, 2015 at 10:21 PM, Marcus Denker <marcus.denker(a)inria.fr >>>>> > wrote: >>>>> >>>>>> >>>>>> > On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean(a)clipperadams.com> >>>>>> wrote: >>>>>> > >>>>>> > Nicolai Hess wrote >>>>>> >> >>>>>> http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-… >>>>>> > >>>>>> > Ah, I miss that too! From that thread, it seems it was removed >>>>>> temporarily >>>>>> > until we have real breakpoints. Is there an issue for its return? >>>>>> > >>>>>> >>>>>> Not yet. >>>>>> >>>>>> Marcus >>>>>> >>>>> >>>>> >>>> >>> >> >> >

April 11, 2015

Re: [Pharo-dev] Problem with asClass usage

by Ben Coman

On Fri, Apr 10, 2015 at 7:44 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Ben Coman wrote > > I believe #asClass itself was introduced for a use case to simplify > > Workspace "user interactive" Gofer scripts to retrieve and load > > Configurations. > > Yes. But it's no longer necessary due to... > > > Ben Coman wrote > > extended Gofer with a method #configurationOf: > > We already have this :) > > Gofer it > ... > configurationOf: 'MyCoolProject'; > loadStable. > > So there is no conflict: > 1. Use the new Gofer API in the workspace (or the Metacello one Christophe > pointed out) > ahhh, cool. The rest sounds fine then. cheers -ben > 2. Handle dependencies like we did for decades prior to #asClass ;) > 3. Remove #asClass before it poisons our beloved system!!! >

April 11, 2015

Pillar package dependency

by Johan Brichau

Hi all, Can someone give me access to the Pillar repository or fix the issue below? I was trying to play around with Pier3 (which uses Pillar) but immediately hit an issue. When loading: Metacello new configuration: 'Pier3'; version: #'release3.1'; load. And then opening localhost:8080 pier gives you a DNU on MacOSXPlatform>>pillarLineEnding The issue is that the code of Pillar-Model (which is loaded by Pier) is dependent on Pillar-ExporterCore (which contains the method above). I think two things need to be done: - move the #pillarLineEnding method to the Pillar-Model - move the #pillarLineEnding method from Platform class to GRPlatform class to ease porting to other Smalltalks thanks Johan

April 11, 2015