Comment 1 Steven Spungin 2014-09-02 09:48:40 EDT

Created attachment 246620 [details]
screenshot: filtering by type

Comment 2 Steven Spungin 2014-09-02 09:53:59 EDT

Created attachment 246621 [details]
screenshot: filtering by name

Comment 3 Steven Spungin 2014-09-02 09:55:40 EDT

Created attachment 246622 [details]
screenshot: filtering by annotation

The patch for bug 201276 will display the annotation name/parameters in the outline.

Comment 4 Dani Megert 2014-09-02 10:18:20 EDT

Ideally, pure text filtering is achieved via bug 69200.

For concrete things like Deprecated, we better add a button to the local toolbar like the ones we already have (e.g. Hide Fields).

If we add more complex options they should be hidden by default.

Comment 5 Steven Spungin 2014-09-02 10:34:14 EDT

(In reply to Dani Megert from comment #4)
> Ideally, pure text filtering is achieved via bug 69200.
> 
> For concrete things like Deprecated, we better add a button to the local
> toolbar like the ones we already have (e.g. Hide Fields).
> 
> If we add more complex options they should be hidden by default.

Thanks Dani, I must have missed that bug.  Keep in mind this a 'filter', not a 'find', so the prev/next discussion in that thread does not apply.

I type 'deprecated' as the annotation name.  I could have also typed 'postConstruct', 'named' or 'GET'.  Actually, by the time I hit the first 'd' only the deprecated annotated items showed up.  This is not too concrete.  I typed the whole word in the screenshot because the outline patch to display annotations has not been applied.

We can certainly visit other ways to add additional filter options and alternate ways to display them in the GUI.  I think this would be best done at a higher level level than JDT;  That way other outline implementations could benefit and there would be some consistency among them.