I'll fix soon what you've noticed and will repost the document.
Post by Stefano FornariCiao Valentino,
it looks a pretty good document to me. I do not have major concerns,
just some random comments.
1. editorial: please make sure you do not have empty lines between
text objects or images. Use styles and frame margins instead.
2. editorial: there is some Outlook plug-in quoted somewhere.
3. "4.2 AddressBookSyncSource": the description is either too detailed
or too vague. I mean that it is maybe a bit too detailed for an high
level design, but too vague for a detailed design. I would suggest to
stay high level, and explain how the SyncSource interact with the
client on one side and how it interacts with the mac sync engine on
the other side. Do not explicit that you create a pointer or so. One
or more sequence diagrams are probably appropriate (again, you do not
have to go at the code level... there is the code for that :) ).
4. still in the same section, why do we need to keep the lists of ids
(I think I understand why, but it is not clear in the design); I guess
it is missing a brief overview of how a mac sync application should
work.
5. in 4.3 there is a missing reference
6. in 4.4. "Here is a list with descriptions of main DLL interface
functions used by UI": what does this actually mean? I guess here a
description about how TargetApplication can use such methods is
missing.
7. check that what specfied in the table make sense for the reader;
for example, what's ABAddressBook? what's the sync mutex? Everything
quoted there must refer to information already obtained reading the
previous sections.
8. I would add a specific section about how to terminate the sync;
this is usually an aspect easy to neglect, but it is instead crucial
to give a proper user experience. An application lifecycle section
could probably make it.
9. As above, error and exceptions is another section that is very
important. Please spend more words on it (we do not have to fill it
completely now, you can update it over time while developing).
10. editorial: please create a reference for each reference and use
the OO reference fields.
I think this is all for now.
I look forward to reading the next draft.
Ste
Post by Valentino MassaroHi all,
this is a first draft of iSync to Funambol plugin design document.
Now I'll start to write the code.
Let me know your comments.
Regards,
Valentino
---------------------------------------------------------------------
----
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Funambol-developers mailing list
https://lists.sourceforge.net/lists/listinfo/funambol-developers
--
Stefano Fornari - Funambol Chief Architect / Funambol CTO
=======================================================
http://www.funambol.org
http://www.funambol.org/documentation/documents.html
http://www.funambol.org/support/faq.html
https://wiki.objectweb.org/sync4j/
http://groups.yahoo.com/group/Sync4j (login required)
http://sourceforge.net/mailarchive/forum.php?forum_id=215 (sync4j-
users)
http://sourceforge.net/mailarchive/forum.php?forum_id=48877
(funambol-dev)
----------------------------------------------------------------------
---
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a
browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Funambol-developers mailing list
https://lists.sourceforge.net/lists/listinfo/funambol-developers
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.