[Design] Restore and Free/Busy

Philippe Bossut pbossut at osafoundation.org
Wed Apr 12 21:45:06 PDT 2006


Mimi Yin wrote:
>> I think I understand Jeffrey's point however, I wonder:
>> - what "restoring" free/busy should do? Right now, it creates a 
>> collection with empty events which is plain wrong, that's not what 
>> the publisher of the free/busy share wants. What he wants is to have 
>> Chandler in a state that was identical to what it was before he has 
>> to clean up his repository, i.e., the .ifb over there and recognized 
>> by Chandler (so that Sync works).
>
> When you say: have Chandler in a state that was identical to what it 
> was before...Do you mean...have Chandler in a state where it is 
> gathering together your f/b information and making it available to 
> others? Or restoring the old f/b information. I guess the idea is that 
> the .ifb file on the server may be really out of date.
Yes, the .ifb file on the server is likely out of date and should be 
updated from... what? Typically, it's from your "My Calendar". Is that 
the way free/busy is created when you first choose "Publish my Free/Busy"?

When I said "identical state" I meant that the user should see no 
difference between the state of his Chandler prior to the repository 
being clean and after the whole set of shares has been restored.
>
>> - what "not restoring" free/busy means? Now if I choose not to 
>> restore the ifb, what is this ifb supposed to be? Can others still 
>> subscribe to it? what does it mean to do that? As a user, what I'd 
>> like to do if I'm not restoring something is to delete it so that no 
>> one takes those info into account anymore. Having an option to delete 
>> a share right here and there in the Restore dialog would be extremely 
>> useful (for Cosmo folks, I know you can do that through the Cosmo web 
>> UI but I'm talking about doing this from Chandler)
>
> Deleting shares on the server would be very useful. I find I have a 
> lot of extra published collections on the server from various attempts 
> to share the same collection.
Ditto here. I propose that we rename "Restore published shares..." to 
"Manage published shares..." and add the relevant buttons to cover the 
management operations: restore, delete...

Cheers,
- Philippe


More information about the Design mailing list