![]() If a strategy is not in place, the second part of this task involves creating a strategy specific to address books. d) Develop strategies for handling conflicts between the two address books - this task first entails familiarizing oneself with OOo's strategies for conflict resolution, especially if a strategy is already in place for address book integration. One replaces the reading from and writing to a text file from (a) with the interaction with the Mac OS X Address Book API from (b). c) Make a prototype for OOo Mac OS X address book integration - given (a) and (b), this process is straightforward. The result of this task is a small program that uses the Mac OS X Address Book API to create the text file from which the section of code created in task (a) reads. One place to look, if the API itself is unclear, is Quicksilver's Apple Address Book Module, which uses the API. b) Familiarize oneself with the Mac OS X Address Book API - after (a), the information needed from the Mac OS X Address Book should be known, so this task is largely a matter of reading up on the API and seeing what is available and in what forms. This task involves first experimenting with the Mozilla address book implementation by changing bits of the code and seeing how those changes manifest in the OOo address book functionality, then creating an equivalent to the Mozilla address book integration that works with a text file (since nothing makes a person more familiar with code than building it). ![]() a) Familiarize oneself with the current OOo Mozilla Address Book integration - this task belongs first because it will be a guide for exactly which parts of the Max OS X Address Book API are important (see (b)). This project has four phases, the first three of which are described briefly on 's project page.
0 Comments
Leave a Reply. |