What I wan to say is that when you know what you want you do not need to navigate.
Object
+ cmd click
+ #ref

is too long for me.



Le 4/6/15 21:52, Tudor Girba a écrit :
Hi Stef,

What you are proposing is interesting.

The criteria for the current language is to be minimalistic and composable because it is supposed to work with any object, not just with code, and the speed should be as good as possible in all cases.

At this point, # means filter the existing list by the category. You do not need #ref. It's enough #r. The nice thing about it is that it has clear semantics, is cheap and composable through diving. I think this is a useful operator that we should not remove. But, this does not mean that we cannot play with other operators.

We played also with other predicates, but the problem is that they are slow, and we have limited bandwidth (we have only one process for all computations).

All in all, it would be cool to have experiments in this direction. However, I would want to have simple semantics that can be explained easily. We already have a few simple actions and people still do not use them to their full potential.

Cheers,
Doru



On Thu, Jun 4, 2015 at 9:35 PM, stepharo <[email protected] <mailto:[email protected]>> wrote:

    But why this is so complex?
    Why I cannot have

        #ref Object?

    or something like that.
    And why do we need #ref and not
        #r
        #m
        #s
    ?
    we could have
        #p
        #c

    I'm a super user and I want super user tools :)

    Stef

    Le 3/6/15 01:20, Tudor Girba a écrit :
    Hi,

    But, that is already possible:
    - Search for a class, like Object.
    - Dive in (Cmd+Right)
    - Type #ref

    And you will get the list of references to Object.

    Cheers,
    Doru




    On Wed, Jun 3, 2015 at 1:17 AM, Ben Coman <[email protected]
    <mailto:[email protected]>> wrote:

        I guess he means... Analyse > Class refs
        and maybe wanting a syntax like...    MyClass #ref
        cheers -ben

        On Wed, Jun 3, 2015 at 4:12 AM, Tudor Girba
        <[email protected] <mailto:[email protected]>> wrote:
        > Hi,
        >
        > If you know the name of the spotter category, you can use
        the #category,
        > like here:
        >
        
http://www.humane-assessment.com/blog/scoping-for-specific-search-category-in-gtspotter/
        >
        > Is this what you are looking for?
        >
        > Cheers,
        > Doru
        >
        >
        >
        > On Tue, Jun 2, 2015 at 10:08 PM, stepharo <[email protected]
        <mailto:[email protected]>> wrote:
        >>
        >> Hi guys
        >>
        >> I often know that I want to look not for the class, its
        package or
        >> methods....
        >> but that I want to get the references to a class.
        >>
        >> Is there a syntax that I can use to instruct spotter about
        my needs?
        >>
        >> Stef
        >>
        >
        >
        >
        > --
        > www.tudorgirba.com <http://www.tudorgirba.com>
        >
        > "Every thing has its own flow"




-- www.tudorgirba.com <http://www.tudorgirba.com>

    "Every thing has its own flow"




--
www.tudorgirba.com <http://www.tudorgirba.com>

"Every thing has its own flow"

Reply via email to