Smalltalk › Pharo › Pharo Smalltalk Developers

GT / Debugger Inspector Duplication

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Sean P. DeNigris

Feb 17, 2015; 12:59am

GT / Debugger Inspector Duplication

Administrator

5777 posts

Right now, for the Debugger one must describe an object-specific inspector using EyeInspector, and then again with GT for the Playground. Can these tools be unified and build themselvs using the same declarative code?

Cheers,
Sean

Marcus Denker-4

Feb 17, 2015; 6:13am

Re: GT / Debugger Inspector Duplication

7582 posts

> On 17 Feb 2015, at 01:59, Sean P. DeNigris <[hidden email]> wrote:
>
> Right now, for the Debugger one must describe an object-specific inspector
> using EyeInspector, and then again with GT for the Playground. Can these
> tools be unified and build themselvs using the same declarative code?

Yes, we right now have 2 sets of inspectors in the system: GT and Eye.
The debugger is the eye-based debugger.
There is a debugger in developlement (and already used by Moose)
that is based on GT.

Marcus

Tudor Girba-2

Feb 17, 2015; 6:21am

Re: GT / Debugger Inspector Duplication

7411 posts

Indeed, this debugger only uses the GT inspector. Once the debugger will be integrated in Pharo, the whole tooling will be more uniform.

Cheers,

Doru

On Tue, Feb 17, 2015 at 7:19 AM, Marcus Denker <[hidden email]> wrote:

> On 17 Feb 2015, at 01:59, Sean P. DeNigris <[hidden email]> wrote:
>
> Right now, for the Debugger one must describe an object-specific inspector
> using EyeInspector, and then again with GT for the Playground. Can these
> tools be unified and build themselvs using the same declarative code?

Yes, we right now have 2 sets of inspectors in the system: GT and Eye.
The debugger is the eye-based debugger.
There is a debugger in developlement (and already used by Moose)
that is based on GT.

Marcus

www.tudorgirba.com

"Every thing has its own flow"