• Add the library as dependency: currently it is only hosted at JCenter repository (but it should be enought right?):

  
  repositories {
  repositories {
      jcenter()
  }
  }

dependencies { compile 'br.com.edsilfer:custom-searchable:0.1.0-Beta' }

 - **Create a provider**: it will be queried to show suggestions to your app's user (the cursor that you'll delivery as a response of the query method must have the columns dicribed in the [columns](#columns) section). You can refer to [RecentSuggestionsProvider ](demo/src/main/java/br/com/edsilfer/content_provider/RecentSuggestionsProvider.java) or [CustomSuggestionsProvider ](demo/src/main/java/br/com/edsilfer/content_provider/CustomSuggestionsProvider.java) for content providers implementation examples - you can also check out this official [tutorial](http://developer.android.com/guide/topics/search/adding-custom-suggestions.html);;

 - **Register the provider in your ```AndroidManifest.xml``` file**: keep in mind that in the case where you have multiple content providers, the one that extends ```SearchRecentSuggestionsProvider``` will always have priority. In case that you have multiple custom content providers (and none that descends from ```SearchRecentSuggestionsProvider```), the last declared will be take into consideration when quering. Example:
  ```xml
  <provider android:name=".content_provider.RecentSuggestionsProvider"
    android:authorities="br.com.edsilfer.content_provider.RecentSuggestionsProvider" />

  <provider android:name=".content_provider.CustomSuggestionsProvider"
   android:authorities="br.com.edsilfer.content_provider.CustomSuggestionsProvider" />

• Set your searchable activity: searchable activity is the one that will receive the intents with the user typed data and/or the selected suggestion list item. To set your activity as searchable, just register it to receive the intents Intent.ACTION_SEARCH;

• Handle the response intents: In your searchable activity class, add code for handling the search intent:

  // Handles the intent that carries user's choice in the Search Interface
  private void handleIntent(Intent intent) {
      if (Intent.ACTION_SEARCH.equals(intent.getAction())) {
          // Receives typed query
          String query = intent.getStringExtra(SearchManager.QUERY);
  
          // Do complex processing ...
      } else if (Intent.ACTION_VIEW.equals(intent.getAction())) {
          // Receives suggested clicked item
          Bundle bundle = this.getIntent().getExtras();
  
          if (bundle != null) {
              ResultItem receivedItem = bundle.getParcelable(CustomSearchableConstants.CLICKED_RESULT_ITEM);
  
              // Do complex processing
          }
      }
  }

PS1.: Note that the POJO class ResultItem holds the abstraction for the information present in one suggestion line;

The custom-searchable library queries a content provider everytime that the user types a new letter in the search content. As a result of this query, based on the content provider interface contract, a cursor shall be returned to it. This cursor must contain the following columns:

• java SearchManager.SUGGEST_COLUMN_TEXT_1: stores the information to be displayed in the result-item first line;
• java SearchManager.SUGGEST_COLUMN_TEXT_2: stores the information to be displayed in the result-item seconde line (when set to work in two-line mode);
• java SearchManager.SUGGEST_COLUMN_ICON_1: stores the Resource ID for the result-item left icon;
• javaSearchManager.SUGGEST_COLUMN_ICON_2: stores the Resource ID for the result-item right icon;

PS2: SearchManager is an OOTB class of Android, to use its columns constants add java import android.app.SearchManager; in your class;

The class CustomSearchableInfo provides the following attributes that helps you to customize your search interface:

• barHeight: sets the search bar header height (defaul it 56dp);
• resultItemHeight: sets the result item brought in the result list height (default is 60dp);
• resultItemHeaderTextSize: sets the result item header text size (default is 16dp);
• resultItemSubheaderTextSize: sets the result item sub-header (when working with two-line mode) text size (default is 14dp);
• searchTextSize: sets the search text text size (default is 14dp);
• barDismissIcon: sets the dismiss search activity icon (return button) (default is a left point arrow);
• barMicIcon: sets the mic image that trigger the speech-to-text api (default is mic icon from Lollipop);
• simpleSuggestionsLeftIcon: sets the result item left icon (default is a clock);
• simpleSuggestionsRightIcon: sets the result item right icon (default is a arrow point left up);
• transparencyColor: sets the transparency color that will overlay the bottom activity;
• primaryColor: background color for the search bar and result row item;
• textPrimaryColor: primary text color applied to the search text, header and subheader (when working with the two-line-mode);
• textHintColor: hint text color applied to the search text;
• rippleEffectMaskColor: mask color for the ripple effect;
• rippleEffectWaveColor: wave color for the ripple effect;
• isTwoLineExhibition: sets if the result list will bring one or two lines;

In order to customize the SearchActivity layout interface with those above attributes, just call the set for them from the class CustomSearchableInfo.

The result-item list can work with one or two lines - the defaul is one line. If you want to work with two line, you've got to specify this behaviour through CustomSearchableInfo class. When working in the one-line mode, the library takes care of adding the queried words that the user have typed for you, hoewever, if you set your app to work with the two-line mode, you're the only who can decide what to put in the second line when storing it. So, you should implement the insert method right after receiving the query intent. Example:

SearchSuggestions suggestions = new SearchSuggestions(this, MySuggestionsProvider.AUTHORITY, MySuggestionsProvider.MODE);
suggestions.saveRecentQuery(queryString, "Second Line Content");