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

Re: [Pharo-project] New Issue Tracker

by Eliot Miranda

On Fri, Feb 8, 2013 at 3:10 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Feb 9, 2013, at 12:01 AM, Frank Shearar <frank.shearar(a)gmail.com> > wrote: > > > On 8 February 2013 22:51, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> > >> On Feb 8, 2013, at 11:49 PM, Frank Shearar <frank.shearar(a)gmail.com> > wrote: > >> > >>> On 8 February 2013 22:41, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >>>> > >>>> On Feb 8, 2013, at 11:34 PM, Camillo Bruni <camillobruni(a)gmail.com> > wrote: > >>>> > >>>>>>> > >>>>>> > >>>>>> That's not a valid comparison. In Squeak trunk bugs are getting > fixed at a > >>>>>> much higher rate > >>>> > >>>> Are you sure? The list that Craig showed at Fosdem was rather short. > >>> > >>> Well, obviously Squeak is a rather smaller community, so that's hardly > >>> surprising. > >>> > >>> Squeakers _do_ need to use bugs.squeak.org, but as I'm sure you know > >>> from getting Pharo going, this is partly a matter of education. > >>> > >> > >> It is a matter of someone doing it. > > > > ... and convincing people to do it is called education. Note my use of > > the word "partly". Anyway, I'm not sure why you're getting stuck into > > this. You sound annoyed. > > I will always be annoyed about that topicâ¦ ;-) > Quite right too. The issue for me is that the bug trackers are not well-enough integrated into my Squeak work flow. Montivcello is beautifully integrated into the work flow and hence a joy to use. I'm not proposing reinventing the wheel and writing a Squeak/Pharo bug tracker (although we did that at ParcPlace/ObjectShare/Cincom and the results were excellent). But at the same time I don't want to go to an external web page to read bugs (althoguh I'm willing to) and I *definitely* don't want to go there to update fixes. I want to update fixes from my Monticello check-in and/or TestRunner. I wonder whether it is feasible to provide a skin to an existing, popular bug tracker so that at least one can have the updating/closing side of the work-flow brought much closer to Monticello check-in/TestRunner? Wouldn't the ideal work-flow be built around an interface between TestRunner and a bug tracker? If we built such an interface wouldn't there be much greater use? Imagine being able to have one-click (plus filling in a description in a submit dialogue) bug creation from TestRunner? And e.g. using pragmas or some-such, add the state and history, or simply the pointer to the bug tracker page, embedded in the test case? Then one could read, in-image, the state of the bug long after it was fixed, in the context of the test that demonstrated the bug and its fix. > > Marcus > -- best, Eliot

Feb. 9, 2013

Re: [Pharo-project] New Issue Tracker

by Benjamin

I think we can all say a big thank you :) Ben On Feb 9, 2013, at 12:27 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-02-09, at 00:24, Benjamin Pollack <benjamin(a)bitquabit.com> wrote: > >> On Fri, Feb 8, 2013, at 06:14 PM, Camillo Bruni wrote: >>> in you are... ;) >>> >>> On 2013-02-09, at 00:12, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> >>> wrote: >>> >>>> I wanna play too :) >>>> >>>> Ben >>>> >>>> On Feb 9, 2013, at 12:05 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>>> >>>>> >>>>> On Feb 8, 2013, at 11:59 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>>>>> >>>>>>> Fog Creek would be happy to provide all of you with a free FogBugz On >>>>>>> Demand account. It has a good API, it has file attachments, it has >>>>>>> custom workflows, triggers, and plugins, and we're about to release a >>>>>>> version that's Gmail-level fast (which I could turn on immediately for a >>>>>>> Pharo account, so you don't have to use the existing "slow" version). I >>>>>>> know it's a relatively complete tracker compared to e.g. GitHub Issues, >>>>>>> but I'd like to believe that our UI is easier to navigate than some of >>>>>>> the other options. Plus, I'd be happy to help migrate your issues from >>>>>>> Google Code to FogBugz on your behalf, with full history if you'd like. >>>>>>> >>>>>>> I know I pretty much lurk on this list these days, but I've been >>>>>>> programming in Squeak since 1996 and Pharo since it came into existence; >>>>>>> giving all of you a free, good bug tracker would make me quite happy. >>>>>>> >>>>>>> --Benjamin >>>>>> >>>>>> Very interesting offer indeed. >>>>>> Would be very cool. >>>>>> >>>>> >>>>> Yes! Camillo already did a tracker for playing: >>>>> >>>>> https://pharo.fogbugz.com >>>>> >>>>> Can you enable us to be testers for the new version? >>>>> >>>>> Marcus >>>>> >>>>> >> >> We've got a blizzard right now, so I'm having some trouble getting in >> touch with the FogBugz team to bump you to the super-fast beta version, >> but I've made the pharo.fogbugz.com trial expire in 2023, turned on Kiln >> just in case that's interesting, and modified the account to accept >> unlimited users--in other words, you've got everything *except* the >> super-fast beta version. Worst-case, I'll turn that on myself on >> Monday. Best-case, someone from the FogBugz team can turn it on for you >> before then. I know this is hand-wavy, but imagine you've got what you >> see now, except that search and case navigation/case actions are >> effectively instant. If you don't want to take my word for it, please >> accept we've got a blizzard and give me until Monday to turn things on. >> :) >> >> Please feel free to ask me question, either here or as bmp on Freenode. >> >> --Benjamin > > thanks ;) > > >

Feb. 8, 2013

Re: [Pharo-project] New Issue Tracker

by Camillo Bruni

On 2013-02-09, at 00:24, Benjamin Pollack <benjamin(a)bitquabit.com> wrote: > On Fri, Feb 8, 2013, at 06:14 PM, Camillo Bruni wrote: >> in you are... ;) >> >> On 2013-02-09, at 00:12, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> >> wrote: >> >>> I wanna play too :) >>> >>> Ben >>> >>> On Feb 9, 2013, at 12:05 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>>> >>>> On Feb 8, 2013, at 11:59 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>>>> >>>>>> Fog Creek would be happy to provide all of you with a free FogBugz On >>>>>> Demand account. It has a good API, it has file attachments, it has >>>>>> custom workflows, triggers, and plugins, and we're about to release a >>>>>> version that's Gmail-level fast (which I could turn on immediately for a >>>>>> Pharo account, so you don't have to use the existing "slow" version). I >>>>>> know it's a relatively complete tracker compared to e.g. GitHub Issues, >>>>>> but I'd like to believe that our UI is easier to navigate than some of >>>>>> the other options. Plus, I'd be happy to help migrate your issues from >>>>>> Google Code to FogBugz on your behalf, with full history if you'd like. >>>>>> >>>>>> I know I pretty much lurk on this list these days, but I've been >>>>>> programming in Squeak since 1996 and Pharo since it came into existence; >>>>>> giving all of you a free, good bug tracker would make me quite happy. >>>>>> >>>>>> --Benjamin >>>>> >>>>> Very interesting offer indeed. >>>>> Would be very cool. >>>>> >>>> >>>> Yes! Camillo already did a tracker for playing: >>>> >>>> https://pharo.fogbugz.com >>>> >>>> Can you enable us to be testers for the new version? >>>> >>>> Marcus >>>> >>>> > > We've got a blizzard right now, so I'm having some trouble getting in > touch with the FogBugz team to bump you to the super-fast beta version, > but I've made the pharo.fogbugz.com trial expire in 2023, turned on Kiln > just in case that's interesting, and modified the account to accept > unlimited users--in other words, you've got everything *except* the > super-fast beta version. Worst-case, I'll turn that on myself on > Monday. Best-case, someone from the FogBugz team can turn it on for you > before then. I know this is hand-wavy, but imagine you've got what you > see now, except that search and case navigation/case actions are > effectively instant. If you don't want to take my word for it, please > accept we've got a blizzard and give me until Monday to turn things on. > :) > > Please feel free to ask me question, either here or as bmp on Freenode. > > --Benjamin thanks ;)

Feb. 8, 2013

Re: [Pharo-project] New Issue Tracker

by Benjamin Pollack

On Fri, Feb 8, 2013, at 06:14 PM, Camillo Bruni wrote: > in you are... ;) > > On 2013-02-09, at 00:12, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > wrote: > > > I wanna play too :) > > > > Ben > > > > On Feb 9, 2013, at 12:05 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> > >> On Feb 8, 2013, at 11:59 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >>>> > >>>> Fog Creek would be happy to provide all of you with a free FogBugz On > >>>> Demand account. It has a good API, it has file attachments, it has > >>>> custom workflows, triggers, and plugins, and we're about to release a > >>>> version that's Gmail-level fast (which I could turn on immediately for a > >>>> Pharo account, so you don't have to use the existing "slow" version). I > >>>> know it's a relatively complete tracker compared to e.g. GitHub Issues, > >>>> but I'd like to believe that our UI is easier to navigate than some of > >>>> the other options. Plus, I'd be happy to help migrate your issues from > >>>> Google Code to FogBugz on your behalf, with full history if you'd like. > >>>> > >>>> I know I pretty much lurk on this list these days, but I've been > >>>> programming in Squeak since 1996 and Pharo since it came into existence; > >>>> giving all of you a free, good bug tracker would make me quite happy. > >>>> > >>>> --Benjamin > >>> > >>> Very interesting offer indeed. > >>> Would be very cool. > >>> > >> > >> Yes! Camillo already did a tracker for playing: > >> > >> https://pharo.fogbugz.com > >> > >> Can you enable us to be testers for the new version? > >> > >> Marcus > >> > >> We've got a blizzard right now, so I'm having some trouble getting in touch with the FogBugz team to bump you to the super-fast beta version, but I've made the pharo.fogbugz.com trial expire in 2023, turned on Kiln just in case that's interesting, and modified the account to accept unlimited users--in other words, you've got everything *except* the super-fast beta version. Worst-case, I'll turn that on myself on Monday. Best-case, someone from the FogBugz team can turn it on for you before then. I know this is hand-wavy, but imagine you've got what you see now, except that search and case navigation/case actions are effectively instant. If you don't want to take my word for it, please accept we've got a blizzard and give me until Monday to turn things on. :) Please feel free to ask me question, either here or as bmp on Freenode. --Benjamin

Feb. 8, 2013

Re: [Pharo-project] Things i am working on now

by Frank Shearar

On 8 February 2013 23:12, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 8 February 2013 22:12, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Igor >> >> I would like to try on my new machine because may be if there is a large difference with yours we can plan to buy one with an SSD >> and recycle yours. Does anybody have an idea if this is worth? >> > i don't know.. > i think it won't work much faster because it is under virtual box > anyways, which causing a lot of overhead. Hm, maybe I missed something - you're running virtualbox on a drive, and you're thinking it won't work much faster on an SSD? I found the opposite (running Windows on VMWare Player) - using an SSD _vastly_ increased the performance of the VM. frank >> Stef >> >>> pff... >>> it finally built.. >>> >>> [ 99%] Building C object >>> CMakeFiles/Pharo.dir/C_/COG/blessed/platforms/win32/vm/sqWin32Prefs.c.obj >>> [ 99%] Building C object >>> CMakeFiles/Pharo.dir/C_/COG/blessed/platforms/win32/vm/sqWin32Utils.c.obj >>> Linking C executable /C/COG/blessed/results/Pharo.exe >>> Creating library file: c:/COG/blessed/results/libPharo.dll.a >>> [100%] Built target Pharo >>> >>> building all stuff from scratch takes a lot of time >>> (cairo , freetype, png, ssl ...) >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >> >> > > > > -- > Best regards, > Igor Stasenko. >

Feb. 8, 2013

Re: [Pharo-project] [update 2.0] #20531

by Camillo Bruni

yes! smart chars and completion got usable again!! thanks guys! On 2013-02-09, at 00:12, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 20531 > ----- > > Issue 7464: Code critic - codecritc browser > http://code.google.com/p/pharo/issues/detail?id=7464 > > Issue 7102: Dont insert spaces between SmartCharacters > http://code.google.com/p/pharo/issues/detail?id=7102 > > Issue 7466: PluggableTextMorph redo still not working > http://code.google.com/p/pharo/issues/detail?id=7466 > > > Diff information: > http://ss3.gemstone.com/ss/Pharo20/NECompletion-MarcusDenker.91.diff > http://ss3.gemstone.com/ss/Pharo20/Morphic-MarcusDenker.1350.diff > http://ss3.gemstone.com/ss/Pharo20/Manifest-CriticBrowser-MarcusDenker.57.d… > http://ss3.gemstone.com/ss/Pharo20/Manifest-Core-MarcusDenker.111.diff > >

Feb. 8, 2013

Re: [Pharo-project] Less than 50 issues!

by Marcus Denker

On Feb 8, 2013, at 11:30 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Current stats: > 27 Open 2.0 Issues (down from 41) [1] > 02 Ready to Review (down from 15) [2] > 01 Ready to Integrate [3] > ______ = > 22 Outstanding [4] > > Less than half of the original 50 left!! What a great sprint :) > Yes! Now we are down to 25 with 3 blocked (on one that is nearly fixed, too). Marcus

Feb. 8, 2013

Re: [Pharo-project] Things i am working on now

by Camillo Bruni

On 2013-02-09, at 00:12, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 8 February 2013 22:12, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Igor >> >> I would like to try on my new machine because may be if there is a large difference with yours we can plan to buy one with an SSD >> and recycle yours. Does anybody have an idea if this is worth? >> > i don't know.. > i think it won't work much faster because it is under virtual box > anyways, which causing a lot of overhead. btw, did you enable multiple cores in virtualbox for your windows slave?

Feb. 8, 2013

Re: [Pharo-project] New Issue Tracker

by Camillo Bruni

in you are... ;) On 2013-02-09, at 00:12, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > I wanna play too :) > > Ben > > On Feb 9, 2013, at 12:05 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On Feb 8, 2013, at 11:59 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>> Fog Creek would be happy to provide all of you with a free FogBugz On >>>> Demand account. It has a good API, it has file attachments, it has >>>> custom workflows, triggers, and plugins, and we're about to release a >>>> version that's Gmail-level fast (which I could turn on immediately for a >>>> Pharo account, so you don't have to use the existing "slow" version). I >>>> know it's a relatively complete tracker compared to e.g. GitHub Issues, >>>> but I'd like to believe that our UI is easier to navigate than some of >>>> the other options. Plus, I'd be happy to help migrate your issues from >>>> Google Code to FogBugz on your behalf, with full history if you'd like. >>>> >>>> I know I pretty much lurk on this list these days, but I've been >>>> programming in Squeak since 1996 and Pharo since it came into existence; >>>> giving all of you a free, good bug tracker would make me quite happy. >>>> >>>> --Benjamin >>> >>> Very interesting offer indeed. >>> Would be very cool. >>> >> >> Yes! Camillo already did a tracker for playing: >> >> https://pharo.fogbugz.com >> >> Can you enable us to be testers for the new version? >> >> Marcus >> >> >

Feb. 8, 2013

Re: [Pharo-project] Things i am working on now

by Igor Stasenko

On 8 February 2013 22:12, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Igor > > I would like to try on my new machine because may be if there is a large difference with yours we can plan to buy one with an SSD > and recycle yours. Does anybody have an idea if this is worth? > i don't know.. i think it won't work much faster because it is under virtual box anyways, which causing a lot of overhead. > Stef > >> pff... >> it finally built.. >> >> [ 99%] Building C object >> CMakeFiles/Pharo.dir/C_/COG/blessed/platforms/win32/vm/sqWin32Prefs.c.obj >> [ 99%] Building C object >> CMakeFiles/Pharo.dir/C_/COG/blessed/platforms/win32/vm/sqWin32Utils.c.obj >> Linking C executable /C/COG/blessed/results/Pharo.exe >> Creating library file: c:/COG/blessed/results/libPharo.dll.a >> [100%] Built target Pharo >> >> building all stuff from scratch takes a lot of time >> (cairo , freetype, png, ssl ...) >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > -- Best regards, Igor Stasenko.

Feb. 8, 2013