On Apr 26, 2007, at 5:40 PM, Mimi Yin wrote:
Hi Morgen,
I've been thinking that perhaps we don't need to force people to
share alarms if they share triage status. What would that mean?
Well we originally thought we had to pair the 2 because otherwise,
you would get dueling ticklers.
Users A and B share a collection and share Triage status, but not
Alarms.
+ User A sets an alarm on a shared item for Time X. At Time X, the
item gets tickled to the top of the NOW section for both users A
and B (assuming they both sync with the server).
+ User B sets an alarm on the same shared item for Time X + 3
minutes. At Time X + 3 minutes, the item gets tickled to the top of
the NOW section again for both users A and B (assuming they both
sync with the server).
Is that so bad? The downside is some extra tickling. The upside is
that Users A and B can still maintain independent Alarms so that
they can each choose a different time for the alarm dialog to pop-up.
If not, then let's leave this functionality the way it is today.
Allow users to share Triage status without necessarily sharing alarms.
If we do that, I would have the default filter settings to be:
+ Share Triage Status
+ Don't share: Alarms, Event Status, Needs reply, BCC
This assumes a Desktop user (Helen the Hub) sharing with a Casual
Collaborator via Chandler Hub UI or another Desktop user. These are
not settings that we would set as defaults if we were optimizing
for sharing with yourself.
Mimi
Heh, the pairing of those two attributes in the checkboxes has been
on my todo list for a long time. Luckily I never got around to doing
it. :-)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
