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

Re: [Pharo-project] Versionner in pharo 2.0

by stephane ducasse

Christophe isâ¦ and will probably reply. We want this tool. On Mar 28, 2013, at 11:17 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > Is there work in progress to make Versionner work in pharo 2.0? The problems I see are at first related to the removal SystemChangeNotifier. > If nobody is working on it is there any reading material about the changes from SystemChangeNotifier to Announcements? I could fix it myself then but I don't know nothing about this system internal. > > thanks, > > Norbert

March 28, 2013

Re: [Pharo-project] Looking for a Seaside 3.1 Configuration for Pharo 2.0

by stephane ducasse

On Mar 28, 2013, at 11:00 AM, Johan Brichau <johan(a)inceptive.be> wrote: > I think it's not a good idea to dump the 3.0.x branch this is not what I meant. I was talking about marketing = name of the release ( I prefer to use a soft that is 3.3 and 3.0.0.0.2.alpha - even if semantic versionning is cool). > Many people are using that + 3.1 is still in development

March 28, 2013

[Pharo-project] Multiselect in method pane

by Norbert Hartl

What is the rationale for having the method pane as multi-select list? I don't think it is of greater use when editing code. I could imagine that some refactoring tasks could be easier having multi-select lists. Anyway, if I try to rename a method without using the refactoring engine I just change the selector, save and delete the method with the old selector. In pharo 2.0 when you rename a method and then click on the old selector both methods are selected and shortcut invocation for deleting deletes both. Which is quite annoying. In my opinion there is no reason for two methods being selected. If you agree I'll happily enter a bug. Norbert

March 28, 2013

[Pharo-project] Versionner in pharo 2.0

by Norbert Hartl

Is there work in progress to make Versionner work in pharo 2.0? The problems I see are at first related to the removal SystemChangeNotifier. If nobody is working on it is there any reading material about the changes from SystemChangeNotifier to Announcements? I could fix it myself then but I don't know nothing about this system internal. thanks, Norbert

March 28, 2013

Re: [Pharo-project] Looking for a Seaside 3.1 Configuration for Pharo 2.0

by Johan Brichau

I think it's not a good idea to dump the 3.0.x branch Many people are using that + 3.1 is still in development On 28 Mar 2013, at 10:32, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > thanks Paul. > > I should say that I would have love not to have > 3.0.1. > 3.0.2 > so I'm really eager to get seaside 3.1 out > but at least something that can be marketed as movement. > > Stef > On Mar 27, 2013, at 11:29 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > >> StÃ©phane Ducasse wrote >>> Hi guys >>> >>> we would like to use seaside to validate the VM and also make sure that >>> Seaside31. works perfectly in Pharo2.0. >>> I saw that some of you have a working configuration. Where can we find it >>> because we would like to publish it in the >>> MetaRepoForPharo20. >>> >>> Stef >> >> >> 3.1 is not released. That being said see if this set of packages works for >> you >> >> http://dl.dropbox.com/u/4460862/seaside31Config.zip >> >> but they are also not official versions of anything and the official ones >> will likely be different. they are just something I cobbled together that >> seemed to work at the beginning of the month. >> >> >> >> >> >> >> -- >> View this message in context: http://forum.world.st/Looking-for-a-Seaside-3-1-Configuration-for-Pharo-2-0… >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > >

March 28, 2013

Re: [Pharo-project] in anybody out there? who uses 2.0?

by stephane ducasse

we should plit that in bug entries and take actions collectively :) On Mar 28, 2013, at 4:56 AM, Yanni Chiu <yanni(a)rogers.com> wrote: > On 27/03/13 10:24 AM, Esteban Lorenzano wrote: >> >> Here in Pharo headquarters we are shock that there are just 10 new bugs reported for 2.0 after the release... >> So... I wonder... is that because we made a really cool release, or just because nobody is using it? > > Just before the release I loaded up my project, and did a quick check to find that everything looked fine - except that I would have to migrate to Fuel-1.9. > > I had noticed that package loading seemed extremely slow, but did not look further into it. I think I saw mention that it's due to some usage of #become:, during the compiling of code. Based on build times (of just loading the rough equivalent code), it seems about 3 times slower to do a build on a Pharo-2.0 vs. Pharo-1.4. > > The slowness is not just an annoyance, because I actually compile code in my application - it's just compiling getters and setters. I've not got enough working yet to see whether it's going to adversely affect the usability (it could make startup time too slow). > > Another thing I've noticed is occasional sluggishness in the UI. It's hard to pinpoint, I often feel like my clicks are being lost. > > The behaviour of the TestRunner was odd. Eventually I discovered running tests via the Nautilus browser, but the UI feedback is extremely confusing for "abstract" test cases. I still don't quite understand the results I see there, so I do a final run of the tests in the TestRunner. > > Another strange issue I had with test cases was to do with the interaction of the deprecation warnings. In by build script, I run: > Deprecation raiseWarning: false. > Deprecation showWarning: false. > so the build can run headless. It took me a few hours, and a careful single stepping, to find that the deprecation exceptions were being swallowed. I'm sure the TestRunner did not behave this way before. If you ran a test, you would still see the deprecation exceptions. It was really frustrating to see your test fail, but have the stack cleared out before you could debug the exception that caused the test failure. > > Are these bugs, or just me getting used to the new release? > >

March 28, 2013

Re: [Pharo-project] Nautilus: Class Side vs. Instance Side

by stephane ducasse

did you see that when there is no class methods the checkbox tell it to you ;) > Hi people, > > I've installed Pharo 2.0 to give it a try. All good until now! > > Looking at Nautilus I see that where there used to be two buttons for switching between class-side and instance-side methods, now there is a checkbox. > > As I was slowly trying to get used to it... it occurred to me that I would have liked even more if I would not have to switch at all. In fact it would be so much nicer to see everything about a class at once. One solution might be splitting the protocols panel in two for instance and class side. do you imagine newbies? I do not think that this is a suitable approch. Stef

March 28, 2013

Re: [Pharo-project] Looking for a Seaside 3.1 Configuration for Pharo 2.0

by stephane ducasse

thanks Paul. I should say that I would have love not to have 3.0.1. 3.0.2 so I'm really eager to get seaside 3.1 out but at least something that can be marketed as movement. Stef On Mar 27, 2013, at 11:29 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > StÃ©phane Ducasse wrote >> Hi guys >> >> we would like to use seaside to validate the VM and also make sure that >> Seaside31. works perfectly in Pharo2.0. >> I saw that some of you have a working configuration. Where can we find it >> because we would like to publish it in the >> MetaRepoForPharo20. >> >> Stef > > > 3.1 is not released. That being said see if this set of packages works for > you > > http://dl.dropbox.com/u/4460862/seaside31Config.zip > > but they are also not official versions of anything and the official ones > will likely be different. they are just something I cobbled together that > seemed to work at the beginning of the month. > > > > > > > -- > View this message in context: http://forum.world.st/Looking-for-a-Seaside-3-1-Configuration-for-Pharo-2-0… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

March 28, 2013

Re: [Pharo-project] Looking for a Seaside 3.1 Configuration for Pharo 2.0

by stephane ducasse

Excellent! I really want to demo Seaside with 2.0 > I'm merging mine and Paul's configuration for Seaside 3.0.7 into Diego's and Stefan's work. > > Of course, there's always stuff that gets in the way of finishing that (like moving our offices ;-). > > I hope to have one by end of the week for Seaside 3.0.7. The intention is that we merge this into the Seaside3.1 configuration. > > Stef wrote: >>> we would like to use seaside to validate the VM and also make sure that Seaside31. works perfectly in Pharo2.0. >>> I saw that some of you have a working configuration. Where can we find it because we would like to publish it in the >>> MetaRepoForPharo20. >> >> We have it working, but it does not have the Seaside Panel (& browser). At last Esug Seaside sprint I started redoing >> them in Spec, but never managed to spend more time on them. They are in the Seaside31 repository >> on squeaksource: Seaside-Pharo-Tools-Spec (might need renaming to Pharo20). >> >> Stephan >> >> >> >> > >

March 28, 2013

[Pharo-project] [update 3.0] #30015

by Marcus Denker

March 28, 2013