[Chandler-dev] Notes on EIMML email integration

[Philippe Bossut]

Hi,

Grant, Reid, BKirsch and BStearns had a short meeting this afternoon to 
review the integration strategy of their pending changes, all revolving 
around EIMML email and Edit/Update. Here's my notes:

Integration strategy:
- Bkirsch proposing to send a diff around. Bstearns prefers a commit. 
Bkirsch says he can't do that before Tuesday. Seems to late for Reid at 
least.
- Should we start an EIM branch? Prefered solution for Reid. Grant to 
prepare one once he received a diff from Bkirsch.
- Grant to change PimBlocks so that Reid can trigger the change to the 
toolbar correctly. Will put that in the branch as soon as created

Questions:
- Who's updating lastModified?
. the repo is not updating that, the UI is (going through the blockItem 
class)
. what about ordinary email? who's doing this since the UI hasn't been 
called? Not done yet, bkirsch to add that.
- CommunicationStatus attribute: don't modify that itself but the other 
attributes (modified, lastModified, lastModification) that are used to 
compute it. Use changeEditState() that does the right bookeping.
- Send/Update: there's a method existing to know if the item is 
sendable. Undistinct comment from bkirsch about a "VMMailService" to 
know if the item has been downloaded (bkirsch, can you clear this up?)
- Grant and bkirsch to discuss off line about sent items

Guys, feel free to add/comment if I missed something important.

Cheers,
- Philippe