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.
