- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Urgent]: Clean up Download Instructions before 4.0 Release

by Jigyasa Grover

As discussed, a tutorial for Pharo Launcher ( https://github.com/SquareBracketAssociates/PharoInProgress/pull/5) has been included in Pharo In Progress under the guidance of Mr. Sean DeNigris. Kindly review it and post in your suggestions/comments. Thanks Jigyasa Grover On Sat, Apr 11, 2015 at 11:43 PM, Bernardo Ezequiel Contreras < vonbecmann(a)gmail.com> wrote: > Peter, > here is the announcement > > http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2014-September/1… > > made by Jan Vrany. you can ask him. > > > > On Sat, Apr 11, 2015 at 4:37 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > >> On Sat, Apr 11, 2015 at 5:31 AM, Bernardo Ezequiel Contreras < >> vonbecmann(a)gmail.com> wrote: >> >>> Peter, >>> The latest vm (http://files.pharo.org/vm/pharo/linux/latest.zip) in >>> debian wheezy gives you the already know problem >>> >>> /lib/i386-linux-gnu/i686/cmov/libc.so.6: *version `GLIBC_2.15' not >>> found* (required by /home/vonbecmann/workspaces/pharo-40/target/pharo) >>> >>> that's why you need the vm ( >>> https://swing.fit.cvut.cz/jenkins/view/Projects/job/pharo-vm-stable-swing/l…) >>> that requires glibc 2.13. >>> >> >> Ah, debian stable; I didn't think of that. But does the swing vm support >> glibc 2.13 _intentionally_ or on accident by just being half a year old? >> Because it doesn't say that anywhere so as a user I would have no idea of >> knowing. And since I have debian testing/unstable then I already have glibc >> 2.19+. And this is why I am that some explanation should be put there. >> >> Peter >> > > > > -- > Bernardo E.C. > > Sent from a cheap desktop computer in South America. >

April 11, 2015

Re: [Pharo-dev] [Urgent]: Clean up Download Instructions before 4.0 Release

by Bernardo Ezequiel Contreras

Peter, here is the announcement http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2014-September/1… made by Jan Vrany. you can ask him. On Sat, Apr 11, 2015 at 4:37 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > On Sat, Apr 11, 2015 at 5:31 AM, Bernardo Ezequiel Contreras < > vonbecmann(a)gmail.com> wrote: > >> Peter, >> The latest vm (http://files.pharo.org/vm/pharo/linux/latest.zip) in >> debian wheezy gives you the already know problem >> >> /lib/i386-linux-gnu/i686/cmov/libc.so.6: *version `GLIBC_2.15' not found* >> (required by /home/vonbecmann/workspaces/pharo-40/target/pharo) >> >> that's why you need the vm ( >> https://swing.fit.cvut.cz/jenkins/view/Projects/job/pharo-vm-stable-swing/l…) >> that requires glibc 2.13. >> > > Ah, debian stable; I didn't think of that. But does the swing vm support > glibc 2.13 _intentionally_ or on accident by just being half a year old? > Because it doesn't say that anywhere so as a user I would have no idea of > knowing. And since I have debian testing/unstable then I already have glibc > 2.19+. And this is why I am that some explanation should be put there. > > Peter > -- Bernardo E.C. Sent from a cheap desktop computer in South America.

April 11, 2015

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

by ClÃ©ment Bera

2015-04-11 1:10 GMT-07:00 Nicolai Hess <nicolaihess(a)web.de>: > > > 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 think break points were done by Clara Allende. As far as I know, they work but there's no IDE support for them. I think they are not ready for this release but I am not sure about the status. Marcus can confirm it will not be ready. Yes this image freeze could be fixed but I can't really work on the Pharo release this week (I'm working with Eliot on Cogit...). I could review the fix if you want just tagged me in fogbugz. > >> 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] Nautilus: Why is Search Field Pre-filled?

by Peter UhnÃ¡k

There are at least three competing approaches: 1. "browse full" Since this is basically copying the original nautilus, this should preserve the filter of the original nautilus 2. "new nautilus" (from shortcut/world) This is more up to user preference, because sometimes you want to preserve it, and sometimes you want it clear. At least in my case the former (preserve it) is much more common. 3. "from another interface" (this means from Spotter, Finder, Senders, "browse" shortcut, and many others. This is questionable for me; I am mostly interested only in the particular class and the fact that it always adds the package to the filter is very annoying to me. One idea might be to remove it from the filter again if the window is closed - since if I close the window I am no longer interested in the class, nor the package. But this would depend heavily on use cases and workflows of people (and I have only my own skewed perspective :)). Peter On Sat, Apr 11, 2015 at 5:51 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > stepharo wrote > > we could have a plus/pin button that logs the previous search. > > That sounds good or a search history because continuing with the same > package set is only one use case and I feel this gets in my way although > maybe I'll get used to it > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Nautilus-Why-is-Search-Field-Pre-filled-tp4819003p481… > 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 Sean P. DeNigris

stepharo wrote > we could have a plus/pin button that logs the previous search. That sounds good or a search history because continuing with the same package set is only one use case and I feel this gets in my way although maybe I'll get used to it ----- Cheers, Sean -- View this message in context: http://forum.world.st/Nautilus-Why-is-Search-Field-Pre-filled-tp4819003p481… 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 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