User:Anaaktgeboren/SearchEngineSync: Difference between revisions

Line 154: Line 154:


== Scratch and Notes ==
== Scratch and Notes ==
* Insights
=== Insights ===
** user created keywords are called 'alias'es in code, stored in search-metadata.json
** user created keywords are called 'alias'es in code, stored in search-metadata.json
** search-metadata.json
** search-metadata.json
Line 170: Line 170:
** Mobile will support search keywords & search suggest in the nearish future.
** Mobile will support search keywords & search suggest in the nearish future.


* Poking Pointers
** http://jsontoxml.utilities-online.info/ convert between the two data formats
** changes frequently dont show up immediate (but get written on close)
** ordering in data store includes hidden engines. the number may not match the observed number
*** note in the example below all engines are off by 1 because google is order:1 and hidden, so youtube appears first in the list but has order:2
** 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
*** searchplugins doesn't exist until you create a non-default one
** SQLite table: install addon, go to tools -> SQLiteManager -> select db, go
** default engines have a hidden value, which afaic, is never applied to custom engines?


* current problems
=== current problems ===
** search suggest has global preferences associated with it. to sync or not to sync?
** search suggest has global preferences associated with it. to sync or not to sync?
*** and if so, should it go in the preferences engine, or in this one? I'm inclined to think it matters even if engines are not synced
*** and if so, should it go in the preferences engine, or in this one? I'm inclined to think it matters even if engines are not synced
Line 192: Line 182:
** can i dump the json content back into the data store *without* the xml?
** can i dump the json content back into the data store *without* the xml?
** design pondering
** design pondering
*** Should this be like tabs and a one-record /client
*** or breakdown the table's multiple entry, grab the json and make it one record per 3rd party (but what about ordering of defaults?)
*** treat the table & the json as entirely separate things, essentially two record types? tis not really the sync way and I do not even know if it is feasible
*** do i extract the values of the json blob and rebuild it on the client, or send the thing over the wire wholesale?


=== What do these data formats look like anyway? ===
=== What do these data formats look like anyway? ===
Line 564: Line 550:
}
}
</pre></div>
</pre></div>
=== Digging around in the code Pointers ===
** http://jsontoxml.utilities-online.info/ convert between the two data formats
** changes frequently dont show up immediate (but get written on close)
** ordering in data store includes hidden engines. the number may not match the observed number
*** note in the example below all engines are off by 1 because google is order:1 and hidden, so youtube appears first in the list but has order:2
** 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
*** searchplugins doesn't exist until you create a non-default one
** SQLite table: install addon, go to tools -> SQLiteManager -> select db, go
** default engines have a hidden value, which afaic, is never applied to custom engines?
Confirmed users
385

edits