Posted by
Tim Mackinnon on
Jul 23, 2017; 8:48pm
URL: https://forum.world.st/Why-do-we-separate-class-instance-methods-in-the-browser-tp4956231p4956473.html
Thierry, i'd forgotten about alt-browser, I recall reading about it a long time ago. I'll check it out as it's sounds like the metaphor I'm thinking about.
The current class/instance toggle just doesn't work well in my opinion - I like the idea of a tree on the protocol pane, that feels like a good use of space.
Anyway, it seems like I'm a bit of a lone voice on this - but that's no problem, I can write something for myself and see how I get on.
If Calypso lives up to what I saw, it sounds like I should be able to mould it happily for me.
Tim
Sent from my iPhone
> On 23 Jul 2017, at 18:25, Thierry Goubier <
[hidden email]> wrote:
>
>> Le 23/07/2017 à 18:58, Attila Magyar a écrit :
>> Maybe if the protocol list was a tree instead of a list then it would make
>> sense to include the class methods there. This would also make easier to
>> move methods from class side to instance side or vica versa with simple drag
>> and drop (without relying on the refactor/move to class side option).
>
> The AltBrowser has been providing that tree view for a few years.
>
> That view is very convenient when you want to see class methods names while writing an instance method (and the reverse).
>
> Never thought of that need for the drag and drop feature. Maybe I'll add it (or simply check how it currently behaves for that use case).
>
> Thierry
>
>> --
>> View this message in context:
http://forum.world.st/Why-do-we-separate-class-instance-methods-in-the-browser-tp4956231p4956439.html>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>
>