Not exactly the same, but related... one of the features I REALLY miss from the Dolphin Smalltalk debugger is the listing of the stack variables in the debugger. This way, I could see, manipulate and inspect intermediate objects, assigned to temporal variables like _stack1, _stack2, etc. [1] That really speeds up my daily debugging. Esteban A. Maringolo [1] http://imgur.com/DhyJ1xU 2014-03-12 5:02 GMT-03:00 Tudor Girba <tudor@tudorgirba.com>:
Hi,
Yes, these are all points for research. It is these things that can make Pharo define its own ground and change dramatically the meaning of programming. There is so much we can do in this space.
If anyone wants to start playing let me know so that we can coordinate.
Cheers, Doru
On Tue, Mar 11, 2014 at 3:56 PM, Friedrich Dominicus <frido@q-software-solutions.de> wrote:
anyway. Has anyone considered adding filtering to the Debugger (in my case the Glamorous Debugger) in a way that not all instance variables values are shown in the value pane?
Well a kind of watch as in other debuggers. You just can "ask" to watch e.g field firstName but not lastName or something like that. Even if I try to keep the information down some classes still do have a lot of elements (think of articles, which usually have at least some kind of id, a description, a price tag, but also some other information (be it internal or extenal for the programm)
-- www.tudorgirba.com
"Every thing has its own flow"