Hi Jeffrey,
I certainly appreciate the complexity of this problem and changes at
this late hour should not be taken lightly. I just had a few more
questions for due diligence sake.
On Apr 11, 2007, at 2:54 PM, Jeffrey Harris wrote:
I guess it wouldn't be the end of the world for Chandler users to see
something different from email recipients (they obviously see
different
things now),
I too think it wouldn't be so bad. The Chandler User will have a lot
more context because they will see the item as an event and can view
it on the calendar. Aparna's problem is especially bad for the email
recipient because they just have the message body to go on...or they
have to go down several clicks to investigate the .ics in a calendar
app.
Also for updates to recurring events you already have, as a Chandler
user, you will only see the modified/updated occurrence in the NOW
section of your Dashboard, marked as Unread, no? So the Chandler user
will experience the whole thing as if they only received that single,
modified, updated occurrence?
But again, I don't fee strongly about this. I think we'll survive if
this short-term hack isn't implemented for Preview.
but... making this sort of change makes me nervous. For
instance, if we make this change, if I really want the email body of
what's sent to reflect the first occurrence of a series, I have to go
find the first occurrence.
That seems like the less common case? More commonly it seems like
you'd want to send out updates when you make single occurrence
modifications (aka Aparna's use case).
My feeling is that what we have now is less than perfect, but there
isn't a lot of coherent middle ground between our
mail-sends-the-whole-series compromise and a full featured system for
choosing to send a subset of the series.
Sincerely,
Jeffrey
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
