Build, Release and QA
---------------------
*Weekly checkpoint*
Bear spins:
http://lists.osafoundation.org/pipermail/chandler-dev/2007-March/007852.html
*IRC bot command*
Bear added a new IRC bot command: ~mark
http://lists.osafoundation.org/pipermail/chandler-dev/2007-March/007863.html
*rt on Linux*
Heikki observed that functional tests on Linux are very sensitive to
focus and active window changes. Running them in a nested X Server can
help (useful for VNC presentations as well). Heikki checked in a helper
script: xrt.sh
http://lists.osafoundation.org/pipermail/chandler-dev/2007-March/007881.html
*Recorded scripts as tests*
Clarifying a commit comment, Dan noted that some scripts were starting
to work.
Dev
---
*EIM, CalDAV, WebDAV*
Jared asked if "removing old sharing" meant Chandler would not be able
to store data on any server besides Cosmo. Morgen explained that
Chandler is a CalDAV client, and can share events with CalDAV servers.
Chandler can also use any WebDAV server to share items over EIMML.
http://lists.osafoundation.org/pipermail/chandler-dev/2007-March/007865.html
*Master Password*
Heikki asked for feedback, code review on his password encryption
implementation. Remaining issues:
- chandler, unit tests don't always quit (threading issue?)
- asking for master password from background thread will break
- unsetting master password before passwords are initialized
http://lists.osafoundation.org/pipermail/chandler-dev/2007-March/007854.html
*EIM attributes*
Grant summarized open issues wrt the domain model and EIM, in particular
for ContentItem, Note, Stamps. Bryan Kirsch, Brian Stearns, Morgen and
Grant discussed the details in the subsequent thread:
http://lists.osafoundation.org/pipermail/chandler-dev/2007-March/007856.html
Philippe noted at one point that needsReply should not be shared
(basically treated the same way as read/unread).
http://lists.osafoundation.org/pipermail/chandler-dev/2007-March/007884.html
*Error icons*
Morgen jumped into a design thread about error icons. His points:
- ask a Share object if it has any conflicts via share.hasConflicts()
- share.hasConflicts(item) for a particular item
- sharing.SharedItem(item).conflictingStates for a particular item
- no syncing per-item errors -- sharing layer treats a collection as an
atomic unit
- sharing error not per-item is already shown in sidebar (Share object's
"error" attribute)
http://lists.osafoundation.org/pipermail/chandler-dev/2007-March/007878.html
Grant observed that per-item errors are possible in CalDAV. Morgen
agreed, and will try and set item.error when a DAV error happens.
http://lists.osafoundation.org/pipermail/chandler-dev/2007-March/007880.html
*Skipping recursive refresh*
Morgen described a scenario that generated an error in Stearns' log.
- subscribe
- commit (on the view the repository uses to subscribe)
- wx.GetApp().PostAsyncEvent( ) lets main thread know it is time to
refresh the main repository view
The refresh doesn't happen, and a "skipping recursive refresh" message
is generated. The subscribe collection is then not found in the main
repository view. Morgen asked why this happens, and if the
PostAsyncEvent call interrupts the main thread.
http://lists.osafoundation.org/pipermail/chandler-dev/2007-March/007883.html
Update: Morgen later gave a link to an IRC discussion. It only happens
when running Wing.
http://wiki.osafoundation.org/script/getIrcTranscript.cgi?channel=chandler&date=20070316
Meetings, Announcements
-----------------------
IRC QA session, desktop recurrence:
http://lists.osafoundation.org/pipermail/chandler-dev/2007-March/007866.html
Meeting coordinating EIM-related features:
http://wiki.osafoundation.org/Projects/DumpReload#Meeting%20notes%20:%2003/13/2007
http://lists.osafoundation.org/pipermail/chandler-dev/2007-March/007850.html
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
