1,007
edits
CloudServices/Sync/FxSync/Developer/ClientAPI: Difference between revisions
CloudServices/Sync/FxSync/Developer/ClientAPI (view source)
Revision as of 03:22, 30 January 2009
, 30 January 2009→Overview
| Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
This page describes how to the client-side Weave API for sync engines (and their helper classes). The focus is on using this API to create a new sync engine to synchronize a new data type. The data type can be anything that extension JS code has access to through any Mozilla API; this means this page must of necessity be pretty vague about reading and writing the underlying data. You'll have to fill in those blanks yourself. Try browsing the [link] xpcom documentation to find out how to get at the many types of useful data that Mozilla stores. | |||
To sync a new data type, you'll need to write an engine class* that extends the base SyncEngine class; you'll also need to extend three helper classes. Here are the classes you need to extend, and the files in which they're defined: | |||
# <tt>SyncEngine</tt>, in <tt>weave/modules/engines.js</tt> | |||
# <tt>CryptoWrapper</tt>, in <tt>weave/modules/base_records/crypto.js</tt> | |||
# <tt>Store</tt>, in <tt>weave/modules/stores.js</tt> | |||
# <tt>Tracker</tt>, in <tt>weave/modules/trackers.js</tt> | |||
It will be very helpful to look at the existing sync engines -- such as the one for bookmarks and the one for history -- and their helper classes, for guidance. You can find these files at: | |||
* <tt>weave/modules/engines/bookmarks.js</tt> -- the <tt>BookmarkEngine</tt>, <tt>BookmarkStore</tt>, and <tt>BookmarkTracker</tt>. | |||
* <tt>weave/modules/type_records/bookmark.js</tt> -- the Record classes for the various subtypes of bookmarks | |||
* <tt>weave/modules/engines/history.js</tt> -- the <tt>HistoryEngine</tt>, <tt>HistoryStore</tt>, and <tt>HistoryTracker</tt>. | |||
* <tt>weave/modules/type_records/history.js</tt> -- the <tt>HistoryRec</tt> record class. | |||
After implementing your classes, you'll have to register them with Weave; you should also add a check-box to the Weave preferences screen to let the user turn your engine on and off. How to do these thing is explained at the end of the page. | |||
* - Javascript is prototype-based, not class-based, so technically it's not correct to talk about "subclassing" or "extending a class", but what we're doing is very much the equivalent of that, and I don't know any other terminology to explain it as clearly. | |||
== Writing a Record class == | == Writing a Record class == | ||