[Chandler-dev] [Sum] Dec 18 - 24

[Katie Capps Parlante]

Build, Release and QA
---------------------
*Checkpoint*
Bear spins 0.7alpha5 trunk checkpoint on Dec 18:
http://lists.osafoundation.org/pipermail/chandler-dev/2006-December/007436.html
Dan tests:
http://lists.osafoundation.org/pipermail/chandler-dev/2006-December/007438.html

*ElementTree performance*
Heikki pointed out that cElementTree is notably faster than the pure 
Python version. He noted that we should switch our usage in zanshin and 
sharing code, and asked if there are other cases. (Heikki is tracking 
this in Bug 7602. He's attached a patch for sharing, and Grant has 
updated zanshin, but has not yet switched Chandler over. Summary from 
comments in the bug.)
http://lists.osafoundation.org/pipermail/chandler-dev/2006-December/007440.html

*ICS diff tool*
Jeffrey added ics_diff as a command line tool to vobject 0.4.6. Jeffrey 
added an option to ignore dtstamp lines. Ascii art elves optional.
http://vobject.skyhouseconsulting.com/
http://lists.osafoundation.org/pipermail/chandler-dev/2006-December/007445.html

*Dogfood instructions*
Aparna replied to Davor's feedback on the dogfood instructions. In 
particular, she noted that OSAF is working on providing a public server 
for people to submit repositories or ics files for debugging. She 
updated the current instructions to point out the privacy issue and 
suggest that users make a comment in bugzilla if they had files 
available for dogfooding -- developers will contact users directly.
http://lists.osafoundation.org/pipermail/chandler-dev/2006-December/007437.html

*Dogfood list*
Katie asked Andre what he meant by "dogfooding specific list". Andre 
explained that he thought it would be useful to have a mailing list for 
dogfooders to assist each other. He felt that a community of technically 
skilled dogfooders helping out others might help in reproducing bugs, 
discover configuration problems, and generally in logging higher quality 
bugs for developers. This community might help prevent bugs getting 
stuck at the "works for me" stage where developers aren't going to make 
progress toward resolving them.
http://lists.osafoundation.org/pipermail/chandler-dev/2006-December/007443.html

Dev
---
*Edit/update domain model*
Grant gave an overview of upcoming changes to the domain model to 
support edit/update features. In particular, the work supports 
"lastModified", with enough of the UI hooked up so that you can tell the 
edit state is being tracked. The UI is proof-of-concept; it still needs 
work to get positioning, fonts, etc. correct.
Overview points:
- Modification enumerated type, for the type of the last change 
(edited/queued/sent/updated)
- lastModification and modifiedFlags added to ContentItem: tracks both 
the last change as well as the history
- changeEditState method added to ContentItem (updates 
lastModified-related attributes)
- "byline" Calculated attribute, string used by UI to show last edit
- "error" attribute, contains last error associated with given item
- mail delivery code uses changeEditState
- UI calls changeEditState. Instead of finding all setattr() calls in 
AttributeEditor subclasses, Grant modified the occurrence proxy to call 
changeEditState, even for items that are not recurring events.
- some logic for the communication column icons moved to an Annotation 
in osaf.pim.mail (CommunicationStatus)
- communication column's index uses the CommunicationStatus.status attribute
- detail view fields to show byline and error strings
- detail view "from" field changes to "send as" for outgoing messages
Todo:
- support for lastModifiedBy (Contact? EmailAddress?)
- review CommunicationStatus states
- recurring events and edit/update
- SMTPDeliveryStatus class, integrate with communication status
- add support for 'created' Modification type
- UI work (review with Reid and Bryan)
More detail and code snippets in Grant's writeup:
http://lists.osafoundation.org/pipermail/chandler-dev/2006-December/007444.html

Brian Kirsch explained that he plans to decouple communication from 
email. Mail delivery code can be factored out, CommunicationStatus can 
be used to track the state of mail communications.
http://lists.osafoundation.org/pipermail/chandler-dev/2006-December/007447.html

Meetings, Announcements
-----------------------
No apps meeting, status:
http://wiki.osafoundation.org/bin/view/Journal/AppsMeeting20061221