[Design] Restoring shares on Chandler desktop after deleting repository

Sheila Mooney sheila at osafoundation.org
Wed Jul 12 15:21:54 PDT 2006


Currently, when user's delete their repository and run Chandler  
again, they need to restore all their shares individually. Published  
shares are restored using the restore menu item. You have to select  
each sharing account individually and restore shares one at a time.  
For subscribed shares, you will have to re-subscribe to URLs one at a  
time.

The design team proposed that there be some one-step way to re-create  
your sharing world a bit easier. The proposal is to replace the  
current restore dialog with a hierarchical view of all your sharing  
accounts and what shares you have published under that account. This  
would be followed by a list of the shares we have subscribed to.  
Mockup below...

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Alpha4_Restore_shares.png
Type: image/png
Size: 23367 bytes
Desc: not available
Url : http://lists.osafoundation.org/pipermail/design/attachments/20060712/19e5c72d/Alpha4_Restore_shares.png
-------------- next part --------------

Somehow each share you had published or subscribed to previously  
would be automatically selected and you simply have to click ok to  
set this up again. After discussions with Morgen, there are several  
issues or questions/issues around this.

+ With the above proposal, you first need to go to the accounts  
dialog and add the details for your sharing accounts as a separate  
step. As Morgen suggested, does it make sense to have some kind of  
way to back up personal settings and accounts?
+ Should we be somehow limiting this to only the default sharing  
account rather than trying to build the hierarchy for all shares on  
each server? How many people will be using different servers?
+ We would have to go to each server, return the list of what's under  
your account then auto-select whatever you had in your chandler view  
last time. Not sure what the technical implications are here but it  
seems like overkill.
+ Are there other options we can consider - I believe Morgen  
suggested storing some information locally.




More information about the Design mailing list