January 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Nautilus often loses context

by Pharo4Stef

Thanks a lot! > me too, but it is only sometimes I can not tell, how to reproduce it. > > > On Thu, Jan 30, 2014 at 8:31 PM, Johan Brichau <johan(a)inceptive.be> wrote: > Hi all, > > When working with Nautilus in Pharo 3, I often experience that the browser looses its context after a save. > I edit a method, save it, and Nautilus will jump away from that context, essentially showing itself as if it was just opened from scratch so I need to manually reselect the class, the protocol and the method I was working on. > > It's very annoying and I wonder if this is something other people experience too and that this is known? > > At first I thought it was when I was editing methods in class extensions. But it happens randomly, sometimes after I got the dialog to 'save your changes' but sometimes not. > > Anybody? > > Johan > > > > > > Most of the time it happens the first time a package gets dirty. > And it is related to this error: > > 12734 Nautilus accept changes shows prompt for cancel dialog > > The fix is there, but not yet integrated. > > > > Nicolai

Jan. 31, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by Johan Fabry

The behavior that Stef explains is indeed what was intended: when they are used show them, when not, not. This is just like Traits. The implementation was broken in this respect though. Sorry for that. I have submitted a fix. https://pharo.fogbugz.com/f/cases/12752 Note that the original way in which classes are created was never adapted, only the way the classes are shown in Nautilus is different than before. ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

Jan. 30, 2014

Re: [Pharo-dev] Nautilus often loses context

by Nicolai Hess

2014-01-30 Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com>: > me too, but it is only sometimes I can not tell, how to reproduce it. > > > On Thu, Jan 30, 2014 at 8:31 PM, Johan Brichau <johan(a)inceptive.be> wrote: > >> Hi all, >> >> When working with Nautilus in Pharo 3, I often experience that the >> browser looses its context after a save. >> I edit a method, save it, and Nautilus will jump away from that context, >> essentially showing itself as if it was just opened from scratch so I need >> to manually reselect the class, the protocol and the method I was working >> on. >> >> It's very annoying and I wonder if this is something other people >> experience too and that this is known? >> >> At first I thought it was when I was editing methods in class extensions. >> But it happens randomly, sometimes after I got the dialog to 'save your >> changes' but sometimes not. >> >> Anybody? >> >> Johan >> >> >> >> > Most of the time it happens the first time a package gets dirty. And it is related to this error: 12734 <https://pharo.fogbugz.com/default.asp?12734> Nautilus accept changes shows prompt for cancel dialog The fix is there, but not yet integrated. Nicolai

Jan. 30, 2014

Re: [Pharo-dev] Nautilus often loses context

by Sabine KnÃ¶fel

me too, but it is only sometimes I can not tell, how to reproduce it. On Thu, Jan 30, 2014 at 8:31 PM, Johan Brichau <johan(a)inceptive.be> wrote: > Hi all, > > When working with Nautilus in Pharo 3, I often experience that the browser > looses its context after a save. > I edit a method, save it, and Nautilus will jump away from that context, > essentially showing itself as if it was just opened from scratch so I need > to manually reselect the class, the protocol and the method I was working > on. > > It's very annoying and I wonder if this is something other people > experience too and that this is known? > > At first I thought it was when I was editing methods in class extensions. > But it happens randomly, sometimes after I got the dialog to 'save your > changes' but sometimes not. > > Anybody? > > Johan > > > >

Jan. 30, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by Pharo4Stef

In fact I do not understand why the solution can just display Pool when there are and none when not. I think that this is what johan wanted to do. Iâm curious to see why this is not the case. Because it looks obvious that current users should not get impacted. I like the idea to remove pool entry when we do not need it. Sebastien can you give an example of what does not work. Stef

Jan. 30, 2014

Nautilus often loses context

by Johan Brichau

Hi all, When working with Nautilus in Pharo 3, I often experience that the browser looses its context after a save. I edit a method, save it, and Nautilus will jump away from that context, essentially showing itself as if it was just opened from scratch so I need to manually reselect the class, the protocol and the method I was working on. It's very annoying and I wonder if this is something other people experience too and that this is known? At first I thought it was when I was editing methods in class extensions. But it happens randomly, sometimes after I got the dialog to 'save your changes' but sometimes not. Anybody? Johan

Jan. 30, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by Esteban Lorenzano

On 30 Jan 2014, at 20:03, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > On Thu, Jan 30, 2014 at 10:58 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 30 Jan 2014, at 19:43, Torsten Bergmann <astares(a)gmx.de> wrote: > > > I checked: it was introduced in update no. 30711 with #issue 12163 > > including the following statements: > > > >> "Who uses poolDictionaries? I suspect extremely few of us." > >> ... > >> "It would be a bit cleaner. I know us old timers don't even see the poolDictionaries: line anymore, but >I dislike having to explain it to students." > > > > > > <humor> > > I would also vote for not displaying Traits anymore. It confuses me when I see them. > > Instance variables are also overvalued - we should remove them from the default > > template too. It's just too confusing to have them there. > > > > And categories now make no sense either - we now have real packages. Let's remove them > > since nobody understands them. > > he, humor or not, is our objective to replace them for real packages. Is just that we still do not have the time :) > > So VMMaker will get completely broken :-(. Has everyone forgotten IIABDFI? it will be compatible, when we do itâ¦ and will be compatible for a long time. but donât worry, in any case it will not happen in a really *long* time :) and the problem of brokenness, is that it depends a lot on points of view and purposes. Esteban > > > > > Object subclass: #Foo > > > > would be much easier to understand! Maybe we should remove superclass as well - lets > > inherit from Object. Would also avoid deep hierarchies like Morphic ;) > > </humor> > > > > But for real: > > If it is too complicated for students one could build a custom "teaching" image. > > > > From the info I see on the issue tracker it sounds to me like an "academic" change > > - still do not understand the real reason... > > > > Bye > > T. > > -- > best, > Eliot

Jan. 30, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by Eliot Miranda

On Thu, Jan 30, 2014 at 10:58 AM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > > On 30 Jan 2014, at 19:43, Torsten Bergmann <astares(a)gmx.de> wrote: > > > I checked: it was introduced in update no. 30711 with #issue 12163 > > including the following statements: > > > >> "Who uses poolDictionaries? I suspect extremely few of us." > >> ... > >> "It would be a bit cleaner. I know us old timers don't even see the > poolDictionaries: line anymore, but >I dislike having to explain it to > students." > > > > > > <humor> > > I would also vote for not displaying Traits anymore. It confuses me when > I see them. > > Instance variables are also overvalued - we should remove them from the > default > > template too. It's just too confusing to have them there. > > > > And categories now make no sense either - we now have real packages. > Let's remove them > > since nobody understands them. > > he, humor or not, is our objective to replace them for real packages. Is > just that we still do not have the time :) > So VMMaker will get completely broken :-(. Has everyone forgotten IIABDFI? > > > Object subclass: #Foo > > > > would be much easier to understand! Maybe we should remove superclass as > well - lets > > inherit from Object. Would also avoid deep hierarchies like Morphic ;) > > </humor> > > > > But for real: > > If it is too complicated for students one could build a custom > "teaching" image. > > > > From the info I see on the issue tracker it sounds to me like an > "academic" change > > - still do not understand the real reason... > > > > Bye > > T. > -- best, Eliot

Jan. 30, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by Esteban Lorenzano

On 30 Jan 2014, at 19:43, Torsten Bergmann <astares(a)gmx.de> wrote: > I checked: it was introduced in update no. 30711 with #issue 12163 > including the following statements: > >> "Who uses poolDictionaries? I suspect extremely few of us." >> ... >> "It would be a bit cleaner. I know us old timers don't even see the poolDictionaries: line anymore, but >I dislike having to explain it to students." > > > <humor> > I would also vote for not displaying Traits anymore. It confuses me when I see them. > Instance variables are also overvalued - we should remove them from the default > template too. It's just too confusing to have them there. > > And categories now make no sense either - we now have real packages. Let's remove them > since nobody understands them. he, humor or not, is our objective to replace them for real packages. Is just that we still do not have the time :) > > Object subclass: #Foo > > would be much easier to understand! Maybe we should remove superclass as well - lets > inherit from Object. Would also avoid deep hierarchies like Morphic ;) > </humor> > > But for real: > If it is too complicated for students one could build a custom "teaching" image. > > From the info I see on the issue tracker it sounds to me like an "academic" change > - still do not understand the real reason... > > Bye > T. >

Jan. 30, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by Torsten Bergmann

I checked: it was introduced in update no. 30711 with #issue 12163 including the following statements: >"Who uses poolDictionaries? I suspect extremely few of us." >... >"It would be a bit cleaner. I know us old timers don't even see the poolDictionaries: line anymore, but >I dislike having to explain it to students." <humor> I would also vote for not displaying Traits anymore. It confuses me when I see them. Instance variables are also overvalued - we should remove them from the default template too. It's just too confusing to have them there. And categories now make no sense either - we now have real packages. Let's remove them since nobody understands them. Object subclass: #Foo would be much easier to understand! Maybe we should remove superclass as well - lets inherit from Object. Would also avoid deep hierarchies like Morphic ;) </humor> But for real: If it is too complicated for students one could build a custom "teaching" image. >From the info I see on the issue tracker it sounds to me like an "academic" change - still do not understand the real reason... Bye T.

Jan. 30, 2014