[Pharo-dev] towards moose in the pharo ide (gtinspector / gtdebugger)
tudor at tudorgirba.com
Tue Dec 31 08:04:23 EST 2013
Thank you, Alex.
On Mon, Dec 30, 2013 at 11:40 PM, Alexandre Bergel
<alexandre.bergel at 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.
> On Dec 30, 2013, at 2:24 AM, Tudor Girba <tudor at 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/dissecting-the-gtinspector/
> > 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
> > This should be just the beginning. To make it better, we need your
> > - Apply and extend these tools for your context (this is what makes them
> > - 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
> > It's your turn now.
> > Cheers,
> > Doru
> > --
> > www.tudorgirba.com
> > "Every thing has its own flow"
> Alexandre Bergel http://www.bergel.eu
"Every thing has its own flow"
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pharo-dev