At this moment, GT primarily means:

- Playground

- Inspector

- Debugger

(Metaceller was never a subject to debate, so I will not address it here)

The Coder will likely follow but first in a different format than one expects. Namely, it will appear first as a code editor inside the inspector.

GT is neither a whim, nor is it experimental. GT is a long term project. For example, the inspector was incubated for more than 4 years, and it is time to work with it and evolve it based on real-life experience. It is true that sometimes it is still moving but that is because it is alive :). Yet, the functionality is there, and if there are issues they should be treated as such: report them and they will be fixed.

Now, the main reason why GT is not optional for the main Moose distribution is that, as I explained one year ago at the MooseDay, Moose will provide the IDE. First, we need a new IDE in Pharo and I think we have cool set of concepts and the Moose engines are perfect for it. Second, when analyzing data from XML structures, plain files, DB, or even Pharo objects, the Inspector is cornerstone. And so is the Playground. As for the Debugger, I will remind you that it comes with working dedicated debuggers for PetitParser, Glamour, and Announcements. These alone make it worth the effort when developing Moose-based solutions.

Not to mention that we are building something that is ridiculously small for the power it harnesses. We should not stop this because we find a couple of bugs along the way.

For all these reasons, GT is here to stay.

Cheers,

Doru

p.s. Btw, the development of GT is not reserved to a closed circle. We would like to invite anyone interested in participating in the development of GT.

p.p.s. Of course, because this system is properly engineered, it can be safely replaced by the default tools:

EyeInspector registerToolsOn: Smalltalk tools.

SpecDebugger registerToolsOn: Smalltalk tools.

Workspace registerToolsOn: Smalltalk tools.

www.tudorgirba.com

"Every thing has its own flow"