Hi Esteban.

Try look into Ghost framework:��https://github.com/pharo-ide/Ghost.

I carefully put��GT support methods into a separate package Ghost-GTSupport .

It also includes a tool to collect all messages from given scenario (like opening inspector) which could help you:

student := GHStudent new.
student inspect.
"then check messages:"
student learning studiedMessages��

For new tools upcoming into Pharo 9 the other��support package will be required.

Also consider implementing Glorp proxies with Ghost. Use GHStudent as an example and I can answer any questions.��

Then we will have a single place (Ghost) to adopt to any tooling changes.��

��, 8 ��. 2020 ��. �� 00:35, Esteban Maringolo <emaringolo@gmail.com>:

Hi,

I'm having a hard time trying to debug some Glorp code in Pharo 8
because the inspectors and the glamour things are triggering the
instantiation of my Proxy objects.

I don't know how the inspectors, variable lists, and other tool work,
but I assume there should be a way to reimplement something in Proxy
to avoid causing a MessageNotUnderstood that triggers the
instantiation.

If there is no way for it (I guess there is, looking at some gt*
selectors in ProtoObject), please consider having a debugPrintString
(and debugPrintOn:) in the upcoming Spec2 based tools. :-)

Best regards,

Esteban A. Maringolo