- Pharo-dev - lists.pharo.org

Re: [Pharo-project] TWM on Pharo 1.4

by Frank Shearar

Are you happy with a bug just on the main Pharo buglist? frank On 19 April 2012 13:07, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Please, if you have a way to reproduce it, open a bug entry :) > > I am a bit busy right now, but I promise to have a look asap ;) > > Ben > > > On Apr 19, 2012, at 1:48 PM, Frank Shearar wrote: > >> On 19 April 2012 12:11, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >>> It was clearly a Nautilus problem (and I just fixed it) >>> >>> The problem is that the Browser API is not clearly defined, messy, and far too huge :s >>> So I add the methods step by step when someone encounter an issue. >>> >>> >>> Thanks for reporting, >> >> Thanks for fixing, Ben! I just needed to load >> Nautilus-BenjaminVanRyseghem.251 and I'm good to go! >> >> Er, but I just found another problem. In my newly-added Browser I went >> to ConfigurationOfTilingWindowManager>>#version13: (so I could prepare >> a patch for Laurent), and got a SubscriptOufOfBounds: 1 in >> CompiledMethod(Object)>>errorSubscriptBounds:. I can't reproduce this >> in a vanilla Pharo-1.4 and your just-released ConfigurationOfNautilus, >> so I'll see if I can't get a shorter "here's how to reproduce the >> problem" recipe later. >> >> frank >> >>> Ben >>> >>> On Apr 19, 2012, at 12:24 PM, Frank Shearar wrote: >>> >>>> Hi Laurent, >>>> >>>> I noticed your announcement and eagerly fired up the latest TWM using >>>> Cog r2550. I selected "New browser" under "Browser actions" and ran >>>> into an MNU: Nautilus class >> #openBrowser. >>>> >>>> That obviously sounds like a Nautilus problem; I bring it to your >>>> attention just because it's your release, and you'd know better than I >>>> whether it's Nautilus or a configuration problem. >>>> >>>> Thanks for the release though! >>>> >>>> frank >>>> >>> >>> >> > >

April 19, 2012

Re: [Pharo-project] TWM on Pharo 1.4

by Benjamin

Please, if you have a way to reproduce it, open a bug entry :) I am a bit busy right now, but I promise to have a look asap ;) Ben On Apr 19, 2012, at 1:48 PM, Frank Shearar wrote: > On 19 April 2012 12:11, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> It was clearly a Nautilus problem (and I just fixed it) >> >> The problem is that the Browser API is not clearly defined, messy, and far too huge :s >> So I add the methods step by step when someone encounter an issue. >> >> >> Thanks for reporting, > > Thanks for fixing, Ben! I just needed to load > Nautilus-BenjaminVanRyseghem.251 and I'm good to go! > > Er, but I just found another problem. In my newly-added Browser I went > to ConfigurationOfTilingWindowManager>>#version13: (so I could prepare > a patch for Laurent), and got a SubscriptOufOfBounds: 1 in > CompiledMethod(Object)>>errorSubscriptBounds:. I can't reproduce this > in a vanilla Pharo-1.4 and your just-released ConfigurationOfNautilus, > so I'll see if I can't get a shorter "here's how to reproduce the > problem" recipe later. > > frank > >> Ben >> >> On Apr 19, 2012, at 12:24 PM, Frank Shearar wrote: >> >>> Hi Laurent, >>> >>> I noticed your announcement and eagerly fired up the latest TWM using >>> Cog r2550. I selected "New browser" under "Browser actions" and ran >>> into an MNU: Nautilus class >> #openBrowser. >>> >>> That obviously sounds like a Nautilus problem; I bring it to your >>> attention just because it's your release, and you'd know better than I >>> whether it's Nautilus or a configuration problem. >>> >>> Thanks for the release though! >>> >>> frank >>> >> >> >

April 19, 2012

Re: [Pharo-project] lagging in the interface

by StÃ©phane Ducasse

On Apr 17, 2012, at 4:25 PM, Hilaire Fernandes wrote: > When using Pharo under tablet (both iPad and Android), we have noted > some lag in the user interface when clicking a button. Indeed sometime > you have to press twice a button to get the press event caught by Pharo. > > This problem does not occur with Squeak 3.9 and same StackVM. > > Any idea? No. Do you have a case? Stef

April 19, 2012

Re: [Pharo-project] Domain pharo.org

by StÃ©phane Ducasse

excellent! Stef > ... we do have the domain pharo.org now (configured to forward to pharo-project.org) > > > Marcus

April 19, 2012

Re: [Pharo-project] TWM on Pharo 1.4

by Frank Shearar

On 19 April 2012 12:11, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > It was clearly a Nautilus problem (and I just fixed it) > > The problem is that the Browser API is not clearly defined, messy, and far too huge :s > So I add the methods step by step when someone encounter an issue. > > > Thanks for reporting, Thanks for fixing, Ben! I just needed to load Nautilus-BenjaminVanRyseghem.251 and I'm good to go! Er, but I just found another problem. In my newly-added Browser I went to ConfigurationOfTilingWindowManager>>#version13: (so I could prepare a patch for Laurent), and got a SubscriptOufOfBounds: 1 in CompiledMethod(Object)>>errorSubscriptBounds:. I can't reproduce this in a vanilla Pharo-1.4 and your just-released ConfigurationOfNautilus, so I'll see if I can't get a shorter "here's how to reproduce the problem" recipe later. frank > Ben > > On Apr 19, 2012, at 12:24 PM, Frank Shearar wrote: > >> Hi Laurent, >> >> I noticed your announcement and eagerly fired up the latest TWM using >> Cog r2550. I selected "New browser" under "Browser actions" and ran >> into an MNU: Nautilus class >> #openBrowser. >> >> That obviously sounds like a Nautilus problem; I bring it to your >> attention just because it's your release, and you'd know better than I >> whether it's Nautilus or a configuration problem. >> >> Thanks for the release though! >> >> frank >> > >

April 19, 2012

Re: [Pharo-project] moose build broke due to ConfigurationOfNautilus

by Benjamin

You are right, I had totally forgotten than Moose was depending on Nautilus :s But now, it should not change for a while (the configuration API ^^) Sorry again, Ben On Apr 19, 2012, at 1:15 PM, Tudor Girba wrote: > Hi, > > It's not a problem. > > I fixed the problem easily, but I was just raising the issue so that > we can prevent it in the future, perhaps through communication. > > Cheers, > Doru > > > On Thu, Apr 19, 2012 at 1:05 PM, Benjamin > <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> I am sorry :( >> >> But we were preparing Nautilus for Pharo 2.0, and we wanted to reduce the amount of groups to not disturb to much users. >> >> So now there are 'core' and 'release' groups... >> >> >> Sorry again, and thank you for using Nautilus :) >> >> Ben >> >> On Apr 19, 2012, at 8:17 AM, Tudor Girba wrote: >> >>> Hi, >>> >>> The Moose build just broke due to the loadRefactorings method being removed from ConfigurationOfNautilus. >>> >>> In general, it would be great to remove as little methods as possible from Configuration classes. >>> >>> Cheers, >>> Doru >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Speaking louder won't make the point worthier." >>> >>> >> >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

April 19, 2012

Re: [Pharo-project] moose build broke due to ConfigurationOfNautilus

by Tudor Girba

Hi, It's not a problem. I fixed the problem easily, but I was just raising the issue so that we can prevent it in the future, perhaps through communication. Cheers, Doru On Thu, Apr 19, 2012 at 1:05 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > I am sorry :( > > But we were preparing Nautilus for Pharo 2.0, and we wanted to reduce the amount of groups to not disturb to much users. > > So now there are 'core' and 'release' groups... > > > Sorry again, and thank you for using Nautilus :) > > Ben > > On Apr 19, 2012, at 8:17 AM, Tudor Girba wrote: > >> Hi, >> >> The Moose build just broke due to the loadRefactorings method being removed from ConfigurationOfNautilus. >> >> In general, it would be great to remove as little methods as possible from Configuration classes. >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "Speaking louder won't make the point worthier." >> >> > > -- www.tudorgirba.com "Every thing has its own flow"

April 19, 2012

Re: [Pharo-project] TWM on Pharo 1.4

by Benjamin

It was clearly a Nautilus problem (and I just fixed it) The problem is that the Browser API is not clearly defined, messy, and far too huge :s So I add the methods step by step when someone encounter an issue. Thanks for reporting, Ben On Apr 19, 2012, at 12:24 PM, Frank Shearar wrote: > Hi Laurent, > > I noticed your announcement and eagerly fired up the latest TWM using > Cog r2550. I selected "New browser" under "Browser actions" and ran > into an MNU: Nautilus class >> #openBrowser. > > That obviously sounds like a Nautilus problem; I bring it to your > attention just because it's your release, and you'd know better than I > whether it's Nautilus or a configuration problem. > > Thanks for the release though! > > frank >

April 19, 2012

Re: [Pharo-project] moose build broke due to ConfigurationOfNautilus

by Benjamin

I am sorry :( But we were preparing Nautilus for Pharo 2.0, and we wanted to reduce the amount of groups to not disturb to much users. So now there are 'core' and 'release' groups... Sorry again, and thank you for using Nautilus :) Ben On Apr 19, 2012, at 8:17 AM, Tudor Girba wrote: > Hi, > > The Moose build just broke due to the loadRefactorings method being removed from ConfigurationOfNautilus. > > In general, it would be great to remove as little methods as possible from Configuration classes. > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Speaking louder won't make the point worthier." > >

April 19, 2012

[Pharo-project] TWM on Pharo 1.4

by Frank Shearar

Hi Laurent, I noticed your announcement and eagerly fired up the latest TWM using Cog r2550. I selected "New browser" under "Browser actions" and ran into an MNU: Nautilus class >> #openBrowser. That obviously sounds like a Nautilus problem; I bring it to your attention just because it's your release, and you'd know better than I whether it's Nautilus or a configuration problem. Thanks for the release though! frank

April 19, 2012