Hi Denis - as an argument in favour, you would only see this view when you select the Hierarchy button (so its not the default) - and by pressing hierarchy, I would argue that you want to see a hierarchy of all the classes (like you see all the classes in non-hierchy mode) - if there is lots of scrolling then that might be a code smell to look into.
As an extra data point - dolphin and visual age both work this way (maybe even visual works?) and I never saw it as a problem - which is why I was surprised that Pharo is different - however I know you guys often think differently. Tim > On 1 Feb 2017, at 13:22, Denis Kudriashov <dionisi...@gmail.com> wrote: > > > 2017-01-05 12:11 GMT+01:00 Tim Mackinnon <tim@testit.works > <mailto:tim@testit.works>>: > I finally got a chance to try this change out - and this a super helpful > change - thanks so much. (It also taught me where some of the things live in > Pharo). > > Why wouldn’t this change be made permanent in the live Pharo? I can’t see any > downside and it really helps understand new code. > > I think it is bad idea to replace current hierarchy view. > With your solution it can be difficult to see superclasses chain of selected > class when it is at the end of subclasses list. It will force user to scroll > which is bad. With current approach this problem not exists. > > But new view mode can be extra option accessible somehow from menu.
