| /external/clang/test/SemaObjC/ |
| default-synthesize-1.m | 91 @property(assign,readonly) float relevance;
104 -(float)relevance {
110 -(id)initWithNode:(id )node relevance:(float)relevance isTitleMatch:(char)isTitleMatch {
111 relevance = 0.0;
|
| /external/chromium/chrome/browser/autocomplete/ |
| autocomplete_match.cc | 13 relevance(0),
25 int relevance,
29 relevance(relevance),
84 // For equal-relevance matches, we sort alphabetically, so that providers
87 if (elem1.relevance == elem2.relevance)
90 return elem1.relevance > elem2.relevance;
|
| autocomplete_result_unittest.cc | 22 // Relevance score.
23 int relevance; member in struct:AutocompleteResultTest::TestData
60 match->relevance = data.relevance;
85 EXPECT_EQ(expected_match.relevance, match.relevance) << i;
143 // Tests that if the new results have a lower max relevance score than last,
144 // any copied results have their relevance shifted down.
|
| history_contents_provider.cc | 32 MatchReference(const history::URLResult* result, int relevance)
34 relevance(relevance) {
38 int relevance; // Score of relevance computed by CalculateRelevance. member in struct:__anon2852::MatchReference
43 if (a.relevance != b.relevance)
44 return a.relevance > b.relevance;
175 // Reset the relevance counters so that result relevance won't vary o
[all...] |
| history_quick_provider.h | 53 // Determines the relevance for some input, given its type and which match it
55 // [0, kMaxSuggestions) indicating the relevance of the match (higher == more
|
| keyword_provider.h | 111 // Determines the relevance for some input, given its type, whether the user
114 // If |allow_exact_keyword_match| is false, the relevance for complete
123 // If |relevance| is negative, calculate a relevance based on heuristics.
130 int relevance);
|
| search_provider.cc | 611 // History returns results sorted for us. We force the relevance to decrease
613 // match having a relevance greater than the previous, but they might be
614 // equal. If we didn't force the relevance to decrease and we ended up in a
615 // situation where the relevance was equal, then which was shown first would
618 // relevance.
639 int relevance = CalculateRelevanceForHistory(i->time, term_looks_like_url, local
641 if (i != results.begin() && relevance >= last_relevance)
642 relevance = last_relevance - 1;
643 last_relevance = relevance;
646 relevance,
[all...] |
| extension_app_provider.cc | 75 match.relevance = CalculateRelevance(input.type(),
169 int relevance = 575 + static_cast<int>(type_count_boost) + local
171 DCHECK_LE(relevance, kMaxRelevance);
172 return relevance;
|
| keyword_provider.cc | 234 // suggestions from last time. We need to readjust the relevance to
235 // ensure it is less than the main match's relevance.
238 matches_.back().relevance = matches_[0].relevance - (i + 1);
388 int relevance) {
400 if (relevance < 0) {
401 relevance =
409 AutocompleteMatch result(this, relevance, false,
496 // the relevance of the first result (added synchronously in Start()),
|
| autocomplete_match.h | 87 int relevance,
133 // The relevance of this match. See table in autocomplete.h for scores
136 // supply matches with appropriate relevance.
140 int relevance; member in struct:AutocompleteMatch
|
| builtin_provider.cc | 53 matches_[i].relevance = kRelevance + matches_.size() - (i + 1);
|
| search_provider.h | 232 // Determines the relevance for a particular match. We use different scoring
254 // the supplied relevance. Adds this match to |map|; if such a match already
255 // exists, whichever one has lower relevance is eliminated.
258 int relevance,
267 int relevance,
|
| autocomplete_unittest.cc | 37 TestProvider(int relevance, const string16& prefix)
39 relevance_(relevance),
245 // Make sure the default match gets set to the highest relevance match. The
246 // highest relevance matches should come from the second provider.
393 // Test comparing matches relevance.
412 m1.relevance = cases[i].r1;
413 m2.relevance = cases[i].r2;
|
| search_provider_unittest.cc | 261 EXPECT_GT(term1_match.relevance, what_you_typed_match.relevance);
391 EXPECT_GT(instant_match.relevance, what_you_typed_match.relevance);
493 EXPECT_GT(what_you_typed_match.relevance, term_match.relevance);
|
| extension_app_provider.h | 67 // Calculate the relevance of the match.
|
| history_contents_provider.h | 52 // Calculates and returns the relevance of a particular result. See the
|
| autocomplete.h | 39 // history or search matches. These matches are given "relevance" scores.
40 // Higher scores are better matches than lower scores. The relevance scores and
159 // ++: a series of matches with relevance from n up to (n + max_matches).
160 // --: relevance score falls off over time (discounted 50 points @ 15 minutes,
162 // **: relevance score falls off over two days (discounted 99 points after two
342 // provider decides what (if any) matches to return, their relevance, and their
420 // we have good relevance heuristics; the controller should handle all
[all...] |
| autocomplete.cc | 608 // clamp globally. This way, old high-relevance matches will starve new
609 // low-relevance matches, under the assumption that the new matches will
611 // new low-relevance match appear and then quickly get pushed off the bottom;
754 matches_.front().relevance : new_matches[0].relevance) - 1;
756 // the highest-relevance matches, we copy in the lowest-relevance matches
765 match.relevance = std::min(max_relevance, match.relevance);
[all...] |
| history_url_provider.h | 186 // Determines the relevance for some input, given its type and which match it
188 // [0, kMaxSuggestions) indicating the relevance of the match (higher == more
|
| /external/chromium/chrome/common/extensions/docs/examples/tutorials/getstarted/ |
| popup.html | 26 "sort=relevance&" + // another good one is "interestingness-desc"
|
| /external/webrtc/src/modules/audio_processing/ns/ |
| nsx_defines.h | 45 //limit on relevance of second peak:
|
| ns_core.h | 33 //limit on relevance of second peak:
|
| /external/chromium/chrome/browser/bookmarks/ |
| bookmark_index.cc | 102 // that calculates result relevance in HistoryContentsProvider::ConvertResults
103 // will run backwards to assure higher relevance will be attributed to the
|
| /external/chromium/chrome/browser/metrics/ |
| metrics_log.cc | 487 WriteIntAttribute("relevance", i->relevance);
|
| /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.build.tools/scripts_cvs/searchcvs/www/projectName/ |
| searchcvs.php | 53 $ec = ", $match AS `relevance`";
54 $order = "ORDER BY `relevance` DESC, `date` DESC";
|
