Brian,
I think it'd be a step forward to get rid of the notion of 'subject'
internally (that is, I think we should get rid of the Calculated Andi
mentions; the mail service would just treat displayName as the subject.
Where it's necessary to _label_ the displayName differently, I think the
UI layer can take care of special-casing it. What do you think?
...Bryan
Andi Vajda wrote:
After your next 'svn update' you need to get the latest chandlerdb
version
by running in 'chandler':
make chandlerdb - OR -
make install
This update removes support for "redirectTo".
I changed all the remaining uses of redirectTo to use a python
property() or a schema.Calculated() instead.
One thing to watch out for are uses of getAttributeValue() and
setAttributeValue() on the attributes that became properties or
Calculateds.
As these are no longer Chandler attribute, a NoSuchAttributeError
should be reported when using these old APIs.
It is strongly recommended to use getattr() and setattr() instead
anyway, at least for performance reasons.
Also, emails that were not shared as anything else such as a task or a
calendar event prior to this change may lose their 'subject'. That
attribute used to be redirected to 'displayName' but there were a
bunch of backwards compatilibity tricks played to keep sharing
subjects as <subject> instead of <displayName>. These tricks are now
gone and 'subject' is just a schema.Calculated() based on
ContentItem.displayName.
Andi..
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
