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

Re: [Pharo-dev] Pharo3 issues

by Sean P. DeNigris

Sean P. DeNigris wrote > and here is that person I would've fixed it already, but since someone went through the trouble to add a setting, I figured maybe there was a use case I was missing... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo3-issues-tp4733048p4733318.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Dec. 31, 2013

Re: [Pharo-dev] Pharo3 issues

by Sean P. DeNigris

StÃ©phane Ducasse wrote > So if somebody thinks that something that is not in our critical path > should be changed he should submit code. +1... and here is that person. The question in my post was: "will anyone speak up for this 'feature'?" If not, I will be happy to revert to the old behavior. While Marcus' suggestion will quickly fix the problem, every setting we add makes the system more complex to understand... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo3-issues-tp4733048p4733316.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Dec. 31, 2013

Re: [Pharo-dev] Pharo3 issues

by StÃ©phane Ducasse

Doru The point of marcus is that we cannot take into account all wishes of everybody: else we would not do anything else. So if somebody thinks that something that is not in our critical path should be changed he should submit code. I have tons of ideas that could be implemented now since we do not have infinite ressources we focus on the important ones. Stef > I do not understand this reaction :( > > Doru > > > On Tue, Dec 31, 2013 at 12:01 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 31 Dec 2013, at 11:58, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> I think this should not be a global preference at all. Most of the time, you actually want to commit in the same repository where you always do. Only from time to time do you need to switch and copy to another repo. So, the preference should be per browser, not global. >> > > consider that the issue was open since July. How likely is it that what you describe will ever be done? > >> Cheers, >> Doru >> >> >> On Tue, Dec 31, 2013 at 11:55 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> On 30 Dec 2013, at 14:42, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> >> > Marcus Denker-4 wrote >> >>> - In monticello browser: when I select my project, all the repositories >> >>> available in Pharo are shown. As in Pharo 2.0, it should show only the >> >>> concerned repositories (2 or 3 max). >> >>> >> >> Yes, this was made on purpose and there is an issue that questions if that >> >> idea was good: >> >> >> >> https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-add… >> >> (this issue is from July) >> > >> > I commented in the issue: >> > +1. I don't like this change at all. Would someone comment on whether there >> > is an unseen purpose or this is a bug? >> > >> >> I think we should set the default of the preference to be the opposite, then itâs fixed with no >> problems for those wanting the other behaviour. >> >> Marcus >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Dec. 31, 2013

Re: [Pharo-dev] WhatsUp from: 2013-12-16 until: 2013-12-31

by HernÃ¡n Morales Durand

2013/12/16 <seaside(a)rmod.lille.inria.fr> > Hi! We're sending this automatic email twice a month, to give the > community an opportunity to easily know what's happening and to coordinate > efforts. Just answer informally, and feel free to spawn discussions > thereafter! > > ### Here's what I've been up to since the last WhatsUp: > > - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS > > - Added ConfigurationOfKomHttpServer to Pharo 3.0 - Added ConfigurationOfDiacritics to Pharo 3.0 - Ported Iliad to Pharo 2.0 and 3.0 - Started to use Log4s in application - Started learning Roassal > ### What's next, until 2013-12-31 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION > > Learn ZeroConf Continuing with AppSec package > (*) we'll be expecting results by then ;) > >

Dec. 31, 2013

Re: [Pharo-dev] Pharo3 issues

by Stephan Eggermont

Marcus wrote: >On 31 Dec 2013, at 11:58, Tudor Girba <[hidden email]> wrote: > > >I think this should not be a global preference at all. Most of the time, you actually want to commit in the same repository where >you always do. Only from time to time do you need to switch and copy to another repo. So, the preference should be per >browser, not global. > > > >consider that the issue was open since July. How likely is it that what you describe will ever be done? Oh, I'm quite positive. I took a look at the code in 30664. Changing view preference is already in the right-click menu on the repositories, and it is global. I *never* found it there before. Though it has something to do with repositories, putting it in the repositories menu is not helpful, as its context is not a single repository. The same problem exists with the package side, the sort methods don't belong in the context menu of individual packages. I'd suggest adding a dropdown-menu on a button in the searchfield-row for both the packages and the repositories, allowing the setting of all-package and all-repository properties. And of course removing the preference and moving it to the instance side. Stephan

Dec. 31, 2013

Re: [Pharo-dev] towards moose in the pharo ide (gtinspector / gtdebugger)

by Alexandre Bergel

Hey! What is the browser you are using? Looks really cool! Alexandre On Dec 31, 2013, at 10:55 AM, NISHIHARA Satoshi <goonsh(a)gmail.com> wrote: > now, i am trying to use it for personal experimental project. > > > 2013/12/31 Tudor Girba <tudor(a)tudorgirba.com>: >> Thank you, Alex. >> >> Doru >> >> >> On Mon, Dec 30, 2013 at 11:40 PM, Alexandre Bergel <alexandre.bergel(a)me.com> >> wrote: >>> >>> I am quasi exclusively using the Moose image, which includes GTDebugger >>> and GTInspector. >>> These are two great tools. I use the standard Pharo 3.0 for particular >>> needs only. When I do this, it is like using Nautilus and coming back to OB >>> (or even the old standard browser). >>> >>> GTDebugger and GTInspector are great. I like them. >>> >>> Alexandre >>> >>> >>> On Dec 30, 2013, at 2:24 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>>> Hi, >>>> >>>> Some of you asked how the GTInspector and GTDebugger are different from >>>> the existing infrastructure. They are quite different from the norm in that: >>>> they are tiny, and they are highly extensible. Here are some posts that >>>> describe what makes them different: >>>> >>>> >>>> http://www.humane-assessment.com/blog/the-moldable-gtinspector-deconstructe… >>>> http://www.humane-assessment.com/blog/dissecting-the-gtinspector/ >>>> >>>> http://www.humane-assessment.com/blog/extending-variables-shown-in-gtinspec… >>>> http://www.humane-assessment.com/blog/moldable-gtdebugger >>>> >>>> These tools are already the default development tools in the Moose >>>> image. As you can see, Moose is reshaping the Pharo IDE. I think this is >>>> exciting. >>>> >>>> This should be just the beginning. To make it better, we need your >>>> energy: >>>> - Apply and extend these tools for your context (this is what makes them >>>> unique). >>>> - Tell us what works and what does not work. >>>> - Ideally, start working with us on this topic. In particular, I am >>>> looking for people that would like to spend some time working on Morphic >>>> widgets. >>>> >>>> It's your turn now. >>>> >>>> Cheers, >>>> Doru >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Every thing has its own flow" >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" > > > > -- > -- > "NISHIHARA Satoshi" > [:goonsh :nsh | ^ nishis perform: goonsh with: nsh] > <moose.jpg> -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 31, 2013

Re: [Pharo-dev] The Moldable Debugger - screencasts

by Tudor Girba

Thanks, Andrei. These are really cool demos! :) Doru On Tue, Dec 31, 2013 at 2:50 PM, Andrei Chis <chisvasileandrei(a)gmail.com>wrote: > Hi, > > I made two new screencasts showing a small domain-specific debugger for > SUnit and one for PetitParser. > > https://vimeo.com/83017763 - SUnit > https://vimeo.com/83017762 - PetitParser > > There is also an older one for announcements (https://vimeo.com/83020584) > > The debuggers were created using the GTDebugger a.k.a. the "moldable > debugger" framework <http://scg.unibe.ch/research/moldabledebugger> > > Cheers, > Andrei > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 31, 2013

Re: [Pharo-dev] towards moose in the pharo ide (gtinspector / gtdebugger)

by NISHIHARA Satoshi

now, i am trying to use it for personal experimental project. 2013/12/31 Tudor Girba <tudor(a)tudorgirba.com>: > Thank you, Alex. > > Doru > > > On Mon, Dec 30, 2013 at 11:40 PM, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: >> >> I am quasi exclusively using the Moose image, which includes GTDebugger >> and GTInspector. >> These are two great tools. I use the standard Pharo 3.0 for particular >> needs only. When I do this, it is like using Nautilus and coming back to OB >> (or even the old standard browser). >> >> GTDebugger and GTInspector are great. I like them. >> >> Alexandre >> >> >> On Dec 30, 2013, at 2:24 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> > Hi, >> > >> > Some of you asked how the GTInspector and GTDebugger are different from >> > the existing infrastructure. They are quite different from the norm in that: >> > they are tiny, and they are highly extensible. Here are some posts that >> > describe what makes them different: >> > >> > >> > http://www.humane-assessment.com/blog/the-moldable-gtinspector-deconstructe… >> > http://www.humane-assessment.com/blog/dissecting-the-gtinspector/ >> > >> > http://www.humane-assessment.com/blog/extending-variables-shown-in-gtinspec… >> > http://www.humane-assessment.com/blog/moldable-gtdebugger >> > >> > These tools are already the default development tools in the Moose >> > image. As you can see, Moose is reshaping the Pharo IDE. I think this is >> > exciting. >> > >> > This should be just the beginning. To make it better, we need your >> > energy: >> > - Apply and extend these tools for your context (this is what makes them >> > unique). >> > - Tell us what works and what does not work. >> > - Ideally, start working with us on this topic. In particular, I am >> > looking for people that would like to spend some time working on Morphic >> > widgets. >> > >> > It's your turn now. >> > >> > Cheers, >> > Doru >> > >> > -- >> > www.tudorgirba.com >> > >> > "Every thing has its own flow" >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" -- -- "NISHIHARA Satoshi" [:goonsh :nsh | ^ nishis perform: goonsh with: nsh]

Dec. 31, 2013

The Moldable Debugger - screencasts

by Andrei Chis

Hi, I made two new screencasts showing a small domain-specific debugger for SUnit and one for PetitParser. https://vimeo.com/83017763 - SUnit https://vimeo.com/83017762 - PetitParser There is also an older one for announcements (https://vimeo.com/83020584) The debuggers were created using the GTDebugger a.k.a. the "moldable debugger" framework <http://scg.unibe.ch/research/moldabledebugger> Cheers, Andrei

Dec. 31, 2013

chasing a VM bug

by StÃ©phane Ducasse

Pavel do you remember when we hacked together at Prague some of your queries crashed systematically the VM. Which version were you using? I will try to provide a reproducible case for esteban and eliot. I have the impression that this is the same that tobias reported. Stef

Dec. 31, 2013