11 Oct
2016
11 Oct
'16
2:40 p.m.
2016-10-11 14:27 GMT+02:00 Hernán Morales Durand <hernan.morales(a)gmail.com>om>:
We may never replace tools that let us explore the code. I'd take
interactive tools over documentation any day, as long as those interactive
tools do work properly...
Regards,
Thierry
2016-10-11 2:47 GMT-03:00 Thierry Goubier <thierry.goubier(a)gmail.com>om>:
I wouldn't mind replacing if it means gaining more power ;)
Hi Hernán,
Le 10/10/2016 à 23:37, Hernán Morales Durand a écrit :
No, nobody said replacing :). I was thinking more in adding a class menu
item to open a Call Graph visualization.
Hi Thierry,
I know the Flow Message Browser since Squeak, but it doesn't provide a
graph.
I would love to have integrated a graph view into the Browser so we can
quickly determine importance of methods.
Replacing whatever is used to navigate between classes and methods in the
browser with a graph that you can use to select methods?
Toggling between normal / hierarchy / call graph
/ whatever...
Depending on the way the target code is structured, it may be more or
less important for understanding.
Yes, as long as we don't have metrics or better documentation (I mean
quality doc) integrated **into** the Browser, we need more tools to quickly
view interactions and help understanding.
Hernán