Hi, See in-line...
On Jun 18, 2007, at 1:55 PM, Jeffrey Harris wrote:
Hi Mimi and Morgen,
The proposed solution is:
1. User A deletes or removes an entire event series from a share.
User B has local changes on one, some or all instances in that
series.
2. User B would accept the deletion/removal for all instances in the
series that they have *not* made local changes to.
I'm not sure what you mean here. Do we want any occurrences to
go away? It seems better to me if all occurrences display a conflict,
listing which occurrences had changed locally.
From what you say below, it sounds like this might be easier?
Could we make this work consistently for This and Future deletions as
well? So, if there's a recurring series with 4 instances and I do a
This and Future deletion starting with instance #3 and sync. And then
it turns out you edited instance #4, do you see both 3 and 4 with
pending deletions? Or just #4 with a pending deletion.
4. Those remaining instances would display a 'Pending Changes'
warning informing User B that User A has deleted/removed the entire
series from the share.
When User B applies User A's deletion, User B's locally changed
instances will also get deleted. ** * * *Q *However, when User B
discards User A's deletion, does the entire series get restored? or
just the instances User B changed locally? (I think the whole series
should get restored...)
If we want the whole series to be restored, I think it would be
best (at
least, easiest) to not delete anything, and display a conflict on all
occurrences. Then if the conflict is discarded on any occurrence,
it'll
go away for all occurrences.
Okay.
What we do now is preserve any modifications if they've been changed,
even though they're not part of the recurrence rule any more. I
suppose
we could mark each orphaned occurrence as having a pending
change to delete it, since it sounds like we're going to start
supporting pending deletions.
What if we kept all the deleted instances around instead of just the
locally modified ones? If you discarded the pending This and Future
deletion, would it restore the original end-date on the series as a
whole? I think that means we'd have to register a Pending change on
the recurrence end-date on all the instances in the 1st 1/2 of the
series. Basically, this means linking the pending deletion to the
pending end-date change, which sounds like infrastructure work.
I think for Preview, it'd be fine to just orphan locally edited
instances and tell the user that there's a pending deletion on that
instance. What I'm describing above is starting to creep into the
territory of logging sharing history and undo.
+ What about deletions of instances that result from changes to
Recurrence Rules? For example, User A turns a Daily event series to a
Weekly event series, thereby deleting a whole lot of instances, some
of which User B made local changes to. Can we keep User B's locally
changed instances around and mark them with the pending changes icon?
In this case, we currently keep User B's old occurrences around,
without
marking anything as pending. Again, we could perhaps mark such
orphaned
occurrence as having a pending deletion. That actually seems pretty
reasonable to me.
Okay.
If User B discards User A's recurrence rule change, can we restore
the series to recur Daily?
I was thinking discarding changes on a particular occurrence would
just
keep that specific off-rule occurrence around instead of deleting
it (so
you'd have to accept changes for potentially several individual
modifications). That would be easy. But recreating the daily
recurrence rule would be a big pain in the butt, I think.
Yup, I see that.
*Other stuff Morgen and I settled on:* + User A's Chandler
automagically turns a modified instance back into an un-modified
instance, thereby removing that modified instances from the recurring
series and User B has made local changes to that modification,
thereby keeping it a modification, User B's local changes win and the
modified instances is put back on the server. (This works today.)
*Jeffrey*, when does this happen?
If you change an occurrence's start time, move it back to its original
start time, then click the triage button that occurrence will stop
being
a modification.
Or, if you have a NOW modification, then mark it DONE, it'll
eventually
go away if it's not the most recent DONE occurrence.
Oh really? When does it go away?
Is that what you were asking?
Yup.
Thanks Jeffrey!
Mimi
Sincerely,
Jeffrey
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
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
