Smalltalk › Cincom › VisualWorks

Browser menu Question

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

4 messages Options

Travis Griggs-4

Browser menu Question

http://objology.blogspot.com/2011/08/ive-inherited-interesting-dilemma.html

--
Travis Griggs
Objologist
"The best way to know you have a mind is to change it" -Judge Pierre Leval

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Steven Kelly

Re: Browser menu Question

As Tom Robinson wrote elsewhere, "I vote for showing all implementations
that could be executed from the starting point". So for an instance-side
method, we only search up to Object, and only on the instance side. For
a class-side method, we search the class side up to Object, and then
also the instance side of Class, ClassDescription, Behavior, Object. My
experience is that only rarely do the latter "surprising" locations show
up, and when they do, I probably want them to (e.g. searching
implementers of #new or #printOn:).

Steve

> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On
> Behalf Of Travis Griggs
> Sent: 24. elokuuta 2011 4:09
> To: VWNC NC
> Subject: [vwnc] Browser menu Question
>
>
> http://objology.blogspot.com/2011/08/ive-inherited-interesting-
> dilemma.html
>
> --
> Travis Griggs
> Objologist
> "The best way to know you have a mind is to change it" -Judge Pierre
> Leval
>
>
>
>
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Ladislav Lenart

Re: Browser menu Question

In reply to this post by Travis Griggs-4

Hello.

I also vote for NOT hiding the method(s) from ClassDescription
and the like. To cite from your blog:

What you expect to see, is only methods that you'd find
as you navigated around in the Hierarchy Browser.

If you look at it the other way around, it is even more important to
show these methods because I didn't expect to see them. UI effectively
informs me about something unusual that's going on. I will be confused
the first time I see this. I will investigate and learn something very
useful during the process. And if I already know the magic, there's no
harm - it even works as a slight reminder to me.

So please keep it the way it is.

Ladislav Lenart

On 24.8.2011 03:08, Travis Griggs wrote:
> http://objology.blogspot.com/2011/08/ive-inherited-interesting-dilemma.html

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Dave Stevenson-3

Re: Browser menu Question

In reply to this post by Travis Griggs-4

I'd like to see the results for everything that could possibly be reached by message look up if the look up were to merely note all matches, rather than stop the search at the first match.

That means if I'm browsing the class side of some typical subclass, I don't want to see its instance methods in a "heirarchy implementors" search. If I want instance methods, I should first navigate the browser to the instance side of the class.

But from the class side I *do* want to see those instance methods reachable by message look up due to the "metaclass wormhole effect".

Dave Stevenson
[hidden email]

From: Travis Griggs <[hidden email]>
To: VWNC NC <[hidden email]>
Sent: Tue, August 23, 2011 8:08:53 PM
Subject: [vwnc] Browser menu Question

http://objology.blogspot.com/2011/08/ive-inherited-interesting-dilemma.html

--
Travis Griggs
Objologist
"The best way to know you have a mind is to change it" -Judge Pierre Leval

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc