GT / Debugger Inspector Duplication
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 -- View this message in context: http://forum.world.st/GT-Debugger-Inspector-Duplication-tp4806064.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
On 17 Feb 2015, at 01:59, Sean P. DeNigris <sean@clipperadams.com> 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
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 <marcus.denker@inria.fr> wrote:
On 17 Feb 2015, at 01:59, Sean P. DeNigris <sean@clipperadams.com> 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"
participants (3)
-
Marcus Denker -
Sean P. DeNigris -
Tudor Girba