Search contact context sensitive

Question

Since implementing search inside an app is not recommended I wonder if the search contract could act context sensitive. Meaning you are already deep inside the app and want to search in that specific part/view of the app.

Would you recommend an inline/in app filter control (text, date) to further reduce the current view or use the search contract for all of that instead?

So if you already in the view where you see all your PNG files and you are looking for PNGs files with specific data you would have to open the search charm and it would only search in the current view or should that be done on the canvas using filter controls?

Answer 1

Phil,

What you are describing is better handled by "find-in-page" and not a Search contract. 
http://msdn.microsoft.com/en-us/library/windows/apps/hh465233.aspx

-Jeff

---

Jeff Sanders (MSFT)

Answer 2

I have to say that a scoped search doesn't really feel the same as a "find in page" to me. For example, in Windows Explorer you can make the same kind of queries inside a folder as from the Start menu in Windows 7 (or Files search in Windows 8). It is the same thing, just scoped differently, whereas find-in-page is something different. 

I wish the "just start typing to search" mechanism from Start were adopted for apps as well. Not only is it convenient (or if you like "fast and fluid") but after doing it in Start I find I instinctively try it elsewhere and am disappointed when it doesn't work - feels like something is broken.

Answer 3

I have implemented what I called "instant search" like in the starmenu using this simple JS code:

document.body.addEventListener('keypress', function(event) {
      var searchPane, _ref;
      if ((_ref = document.activeElement.tagName.toLowerCase()) === 'input' || _ref === 'select') {
        return;
      }
      if (event.ctrlKey || event.key.length > 1) {
        return;
      }
      searchPane = Windows.ApplicationModel.Search.SearchPane.getForCurrentView();
      searchPane.show(event.key);
      event.preventDefault();
      event.stopImmediatePropagation();
      return true;
    });

This is generated code from CoffeeScript, but I guess you get the idea :)