Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(114)

Side by Side Diff: chrome/browser/search_engines/prepopulated_engines.json

Issue 11377049: Moving prepopulated search engines to a JSON file. (Closed) Base URL: http://git.chromium.org/chromium/src.git@master
Patch Set: Answered review comments. Created 8 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
(Empty)
1 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
2 // Use of this source code is governed by a BSD-style license that can be
3 // found in the LICENSE file.
4
5 // This file is used by json_to_struct.py to generate prepopulated_engine.h/cc.
6
7 // Engine definitions. See prepopulated_engines_schema.json for the field
8 // definitions.
9
10 // The following unique IDs are available:
11 // 53, 56, 58, 60, 61, 64, 65, 66, 70, 74, 78, 79, 80, 81, 84, 86, 88, 91,
12 // 92, 93, 94, 95, 96, 97, 98, 99, 102+
13 //
14 // IDs > 1000 are reserved for distribution custom engines.
15 //
16 // NOTES:
17 // CHANGE THE ABOVE NUMBERS IF YOU ADD A NEW ENGINE; ID conflicts = bad!
18 // CHANGE kMaxPrepopulatedEngineID in template_url_prepopulate_data.cc if you
19 // add new engine outside of the current range or it will not be counted
20 // in stats.
21
22 {
23 // Increment this if you change the above data in ways that mean users with
Peter Kasting 2012/11/09 22:07:23 Nit: This comment shouldn't say "above data"
beaudoin 2012/11/10 09:17:54 Done.
24 // existing data should get a new version.
25 "version": 45,
26
27 "engines": {
28 "abcsok": {
29 "name": "ABC S\u00f8k",
30 "keyword": "abcsok.no",
31 "favicon_url": "http://abcsok.no/favicon.ico",
32 "search_url": "http://abcsok.no/index.html?q={searchTerms}",
33 "type": "SEARCH_ENGINE_ABCSOK",
34 "id": 72
35 },
36
37 "altavista": {
38 "name": "AltaVista",
39 "keyword": "altavista.com",
40 "favicon_url": "http://www.altavista.com/favicon.ico",
41 "search_url": "http://www.altavista.com/web/results?q={searchTerms}",
42 "type": "SEARCH_ENGINE_ALTAVISTA",
43 "id": 89
44 },
45
46 "google": {
47 "name": "Google",
48 "keyword": "google.com",
49 "favicon_url": "http://www.google.com/favicon.ico",
50 "search_url": "{google:baseURL}search?q={searchTerms}&{google:RLZ} {google :acceptedSuggestion}{google:originalQueryForSuggestion}{google:assistedQueryStat s}{google:searchFieldtrialParameter}sourceid=chrome&ie={inputEncoding}",
Peter Kasting 2012/11/09 22:07:23 The space here is erroneous
beaudoin 2012/11/10 09:17:54 Done.
51 "suggest_url": "{google:baseSuggestURL}search?{google:searchFieldtrialPara meter}client=chrome&hl={language}&q={searchTerms}&sugkey={google:suggestAPIKeyPa rameter}",
52 "instant_url": "{google:baseURL}webhp?sourceid=chrome-instant&{google:RLZ} {google:instantEnabledParameter}ie={inputEncoding}",
53 "alternate_urls": "[\"{google:baseURL}#q={searchTerms}\", \"{google:baseUR L}search#q={searchTerms}\", \"{google:baseURL}webhp#q={searchTerms}\"]",
Peter Kasting 2012/11/09 22:07:23 Having to escape the quotes here sucks, can we avo
beaudoin 2012/11/10 09:17:54 Yes. It's actually one benefit of that approach: T
54 "type": "SEARCH_ENGINE_GOOGLE",
55 "id": 1
56 }
57 }
58 }
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698