User:Anaaktgeboren/SearchEngineSync: Difference between revisions

Line 43: Line 43:
** /profile/search.json
** /profile/search.json
*** "directories" will have two entries, the default one ("/Applications/Firefox.app/Contents/MacOS/searchplugins") & "/Users/mozilla/Documents/inbox-desktop/test_profiles/searchplugins" in my case) The first has no usefully syncable data, though it does have a lastModifiedTime (this is the lastModifiedTime of the directory, used for cache invalidation --Gavin)
*** "directories" will have two entries, the default one ("/Applications/Firefox.app/Contents/MacOS/searchplugins") & "/Users/mozilla/Documents/inbox-desktop/test_profiles/searchplugins" in my case) The first has no usefully syncable data, though it does have a lastModifiedTime (this is the lastModifiedTime of the directory, used for cache invalidation --Gavin)
** /profile/search.sqlite (this is no longer used after bug 699856, replaced by search-metadata.json --Gavin)
** /profile/search.sqlite(DO NOT SYNC) (this is no longer used after bug 699856, replaced by search-metadata.json --Gavin)
*** engineid column identifies engine xml file, and notably where it came fromt[app] or [profile]  
*** engineid column identifies engine xml file, and notably where it came fromt[app] or [profile]  
**** which would map to the directories list in the search.json?
**** which would map to the directories list in the search.json?
Line 52: Line 52:
** pref browser.search.useDBForOrder i bet that represents ordering (this gets set to true once the user has customized the search engine order, to indicate that we should use the positioning information in search-metadata.json rather than the one in default prefs (browser.search.order.*) --Gavin)
** pref browser.search.useDBForOrder i bet that represents ordering (this gets set to true once the user has customized the search engine order, to indicate that we should use the positioning information in search-metadata.json rather than the one in default prefs (browser.search.order.*) --Gavin)
** pref browser.search.order.1-3 are hard coded defaults. do not sync
** pref browser.search.order.1-3 are hard coded defaults. do not sync
** JAR loading code is for mobile, for their default plugin handling
** getting a 3rd party search thingy
** getting a 3rd party search thingy
*** right click on a website search bar (ie youtube) and /profile/searchplugins will be created with an OpenSearch .xml
*** right click on a website search bar (ie youtube) and /profile/searchplugins will be created with an OpenSearch .xml
Line 60: Line 61:
* current problems
* current problems
** how do i gracefully slurp the json content?
** how do i gracefully slurp the json content?
** how much of the json content do I need?
** how do i handle hidden?
** why do google/bing end up with duplicate entries in the search table? if a keyword is used a new row is added except value is the keyword?
** what does used mean in the sql table? in the name column?
** design pondering
** design pondering
*** Should this be like tabs and a one-record /client
*** Should this be like tabs and a one-record /client
Confirmed users
385

edits