While updating the Email spec, I realized that it would be funny for
users to select an instance of a recurring event to Reply to or
Forward and then have the metadata from the master event show up in
the Notes field of the Reply/Forward.
We don't need to provide users with an option to Reply to/Forward
this instance, this and future instances or the entire event series.
We don't need to keep track of which instances or sub-group of
instances were replied to or forwarded...we have no UI to expose this
kind of metadata anyway.
We *should* however, use the metadata from the instance the user
selected in the summary pane when they hit Reply/Reply all or Forward
in the toolbar. In other words, replying to and forwarding recurring
events should work the same as replying to and forwarding any other
kind of Chandler item.
bkirsch, is this right for Preview? Am I making less work for you? or
is this somehow more complicated? :o)
I've updated the Email spec with this proposal (again in olive/khaki:
http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/Email-0.7.html
Sending, Replying to and Forwarding Recurring Events
In the Preview timeframe: Send, Update, and the Addressing fields
will always apply to the entire event series.
When Replying and Forwarding recurring events, we will not offer
users the choice of replying to/forwarding a single instance, this
and future instances or the entire event series. Instead, we will
simply take the Title, Location, Date/Time and Notes field data from
the 'selected' occurrence in the summary pane and use that in the
reply/forward.
In other words, replies and forwards to recurring events should work
like all other replies and forwards.
For more details on how sent/edited and updated recurring events will
show up in the UI, see the Recurring Events section of the Dashboard
spec: http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/
Dashboard-0.7.html
Mimi
On Feb 14, 2007, at 3:57 PM, Grant Baillie wrote:
On 14 Feb, 2007, at 14:35, Mimi Yin wrote:
As a general comment to 2--5 and 7--8 below, I'm wary of trying
to do things like replying to individual instances of events.
While the domain model can handle (or be made to handle) this
kind of thing, ICalendar isn't very well suited to yanking
individual occurrences out of recurring series, so I'm concerned
we'll have trouble with non-Chandler clients. In oither words, I
think it's a similar situation to allowing individual occurrences
within a series be in different collections.
Sure, that's fair. So what's the easiest thing to display in the
Body of the item? The contents of the Master event?
That sounds best/easiest to me.
--Grant
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
