towards moose in the pharo ide (gtinspector / gtdebugger)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

towards moose in the pharo ide (gtinspector / gtdebugger)

Tudor Girba-2
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:


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

--

"Every thing has its own flow"
Reply | Threaded
Open this post in threaded view
|

Re: towards moose in the pharo ide (gtinspector / gtdebugger)

Alain Busser
OK I understood the message :-D

I plan to test the Moose image with MathsOntologie and you will get plenty of stupid questions like "how can I do this?" or "why that doesn't work?", after all this is all that you deserve

This is my peculiar way to wish to you and all the team an happy and successful year

Alain


On Mon, Dec 30, 2013 at 9:24 AM, Tudor Girba <[hidden email]> 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:


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

--

"Every thing has its own flow"

Reply | Threaded
Open this post in threaded view
|

Re: towards moose in the pharo ide (gtinspector / gtdebugger)

Tudor Girba-2
Thank you, Alain.

I am looking forward for all your questions :)

Doru


On Wed, Jan 1, 2014 at 8:34 AM, Alain Busser <[hidden email]> wrote:
OK I understood the message :-D

I plan to test the Moose image with MathsOntologie and you will get plenty of stupid questions like "how can I do this?" or "why that doesn't work?", after all this is all that you deserve

This is my peculiar way to wish to you and all the team an happy and successful year

Alain


On Mon, Dec 30, 2013 at 9:24 AM, Tudor Girba <[hidden email]> 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:


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

--

"Every thing has its own flow"




--

"Every thing has its own flow"