19 Dec
2013
19 Dec
'13
9:29 p.m.
Hi Doru,
On 19 Dec 2013, at 07:50, Tudor Girba <tudor(a)tudorgirba.com> wrote:
Hi,
I took a bit of time to describe how the GTInspector works, what makes it different, and
to provide hints for several usage scenarios.
http://www.humane-assessment.com/blog/the-moldable-gtinspector-deconstructed
It's a long post, I know :), but please take a look. As you might know, this is the
default inspector in the Moose image, but it can also be loaded in a fresh Pharo image.
I am particularly interested in the following:
- if you never used it, and tried it now, what don't you like?
- if you used it, was there anything that you did not know?
- and of course, what do you like about it?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
I read the blog post and installed the code in my working Pharo 3 image. First off, I like
the debugger, it feels polished, and I like the inspector, it is quite interesting. The
clear tables for instance variables names and values and dictionary keys and values are
much better. SequenceableCollection indexes would be nice. Paging is cool.
I miss an option to go back to less columns, like from 1 to 2 and back to 1, I can’t seem
to deselect something in the first one, which would be a way to let the second one
disappear again. I hope I am making myself clear ;-)
We have specialised inspectors for Integer and Float (and maybe some more) standard in
Pharo, showing more high level virtual fields, it would be nice if you could implement
those as well, maybe as alternative views.
Which brings me to my final question: how do I write simple custom inspectors, given that
I am not familiar with Glamour/Moose - that could maybe be another blog post ?
Anyway, thanks for pushing this !
Sven
PS: I wonder whether it would be possible to have both types of inspectors/debuggers
available at the same time, so that one can switch on the fly, compare them, use one or
the other depending on the task ?
--
Sven Van Caekenberghe
http://stfx.eu
Smalltalk is the Red Pill