See in-line
On Nov 9, 2006, at 10:37 AM, Dan Steinicke wrote:
If you publish an item and then latter stamp it as 'never share'
the current behavior seems a little odd. I don't know where this
functionality fits into the current release schedule goals but
current behavior seems a bit rough and at some point we probably
want to spend some time thinking about how this should work.
The way it works now is that the side of the share that clicked the
'never share' icon will no longer propagate changes to that item to
the other sharEEs. What seems odd is that the other sharEEs can
still make changes to that item and those changes will propagate
back to the 'never-share-clickers' calendar.
Ooh, that's wrong. It should either remove the item from the share.
Or exclude that particular user from sharing the item.
Does it make sense to allow a user to give 'never share' status to
an item that has already been shared? (I think we should only
allow an item to have 'never share' status if it has not yet been
shared)
That would probably be the simplest solution. Or we could call it
'Stop sharing this item' if it's already shared.
Does the one way blocking of changes that happens when someone
'never shares' an already shared item make sense? (If we do allow
an already shared item to have 'never share' status then I think it
should be deleted from subscribed calendars on the next sync after
becoming 'never share', eliminating the possibility of subscribers
modifying the 'never share' event)
No, that doesn't make sense, that would be a bug. Good catch!
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
