I suggest you ...

enhance search filtration

The combined Search interface is good, but the search filtration system is a bit cumbersome. In general I think one knows whether one is searching for a type/member/property/namespace/method/string etc, and the super-advanced combination filtration system is probably overkill.

I suggest adding a system to allow one to quickly identify the scope of the search within the search box, when the advanced filtration system is more than is needed. Some examples:

type:guid
method:execute
property:isempty
namespace:search.dictionary
member:potato <- searches properties, fields and methods
class:monkey <- only types that are classes
struct:flapjack <- only types that are structs
enum:pancake <- I think you get the idea

These would all be "contains" type searches and would essentially preset the filtration from the search box.

3 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Richard HauerRichard Hauer shared this idea  ·   ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base