Merge lp:~tomdroid-dev/tomdroid/search-interface into lp:~tomdroid-maintainers/tomdroid/main
Status: | Merged |
---|---|
Merged at revision: | 237 |
Proposed branch: | lp:~tomdroid-dev/tomdroid/search-interface |
Merge into: | lp:~tomdroid-maintainers/tomdroid/main |
Diff against target: |
455 lines (+272/-13) 13 files modified
AndroidManifest.xml (+15/-0) res/layout/main.xml (+9/-3) res/layout/search.xml (+50/-0) res/menu/main.xml (+8/-4) res/values/strings.xml (+10/-0) res/xml/preferences.xml (+6/-1) res/xml/searchable.xml (+7/-0) src/org/tomdroid/NoteManager.java (+26/-4) src/org/tomdroid/ui/PreferencesActivity.java (+20/-1) src/org/tomdroid/ui/Search.java (+104/-0) src/org/tomdroid/ui/Tomdroid.java (+4/-0) src/org/tomdroid/util/Preferences.java (+1/-0) src/org/tomdroid/util/SearchSuggestionProvider.java (+12/-0) |
To merge this branch: | bzr merge lp:~tomdroid-dev/tomdroid/search-interface |
Related bugs: | |
Related blueprints: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Olivier Bilodeau | Approve | ||
Review via email: mp+68150@code.launchpad.net |
Description of the change
Search ability for Tomdroid!
* Created standard Android Search Interface, called by clicking on Search button or Search menu
* Search Results are shown in a Results List, clicking on the List-items opens the note.
* Search history is saved and presented as suggestions while typing.
* Search history can be deleted in Preferences.
* Search is a SingleTop Activity -> clicking on back button in Results List brings you direct to Tomdroid List View.
* Clicking on search button in Results List opens another search
I suggest to also merge usability-
Started the review.
One minor thing I note is that you need to be more careful about consistency. For ex: in the new search strings there is search_hint (underscore separation), strNoResults (java-style object name) and SearchResultTitle (java-style class name). We should aim for only one notation style unless we have a pattern.
Really not a big problem, not enough to go back and fix it IMO but with new code/strings we should aim to avoid it.