On Sep 28, 2006, at 7:27 PM, Andi Vajda wrote:
On Thu, 28 Sep 2006, Morgen Sagen wrote:
Bug 6857 is a request to take the In and Out collections out of
the "Mine" collection. This is a trivial fix (removing a couple
lines from osaf/pim/__init__.py), but I wonder if there was a
reason these were part of Mine to begin with. Anyone see a
problem with taking them out of Mine?
Are they 'mine' because mail to me and from me can be considered to
be mine ?
If the meaning of 'mine' is not mine then maybe that needs to be
renamed too.
Here is a more detailed description of the current situation:
"In" contains all email items whose isOutbound attribute is False;
"Out" contains all email items whose isOutbound is True. They don't
take into account whether the user is in any of the email headers, so
they aren't really a good indicator of "mine-ness". Where this is a
problem is when you subscribe to a collection that contains email
messages someone else has shared. When those emails are brought into
the repository, they end up in the "Out" collection (because they are
emails, and the initialValue of isOutbound is True), and since "Out"
is a source for "Mine", and "Mine" feeds into the "All" collection,
you see them in the Dashboard -- even if the collection you
subscribed to was marked as "keep out of Dashboard".
I see two solutions:
1) Remove "In" and "Out" as sources for the "Mine" collection as Mimi
asked for
2) Change the filter for "In" and "Out" to also examine the email
headers and only include those messages that are actually to or from
the user. I have a feeling this will be inefficient, but maybe
someone can suggest a good way to implement it.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
