Hi Andre,
I think this is a good enhancement request. Here's a rough proposal.
1. Ask if the user wants to restore shares right now.
2. Give user option to select which shares to restore, or restore all
shares.
===
Sync Account
-----
You have 4 collections in your Chandler Hub account. Which of them
would you like to sync?
[ ] Sync all collections
[ ] Collection - 1
[ ] Collection - 2
[ ] Collection - 3
[ ] Collection - 4
[Never Sync] [Sync Later] [Sync Now]
-----
The question remains...if the user selects [Sync Later] when do we
prompt them again? Upon next start-up?
I assume this option would only pop-up the first time the user adds a
sharing account *and* when/if new collections appear in their sharing
account.
When new collections appear, we should pop-up the following dialog:
===
Sync Account
-----
You have 4 collections in your Chandler Hub account. Which of them
would you like to sync?
[ ] Sync all collections
[ ] Collection - 1
[ ] Collection - 2
[ ] Collection - 3
[ ] Collection - 4
[Never Sync] [Sync Later] [Sync Now]
-----
We would also need to add a menu item so that users can access 'Sync'
options at will. We should probably combine this menu with the 'Set
Auto-sync Intervals...' and 'Suspend Syncing' menu items.
File>>Sync, Sync Options
===
Sync Options
-----
[ ] Sync all collections
[ ] Collection - 1
[ ] Collection - 2
[ ] Collection - 3
[ ] Collection - 4
-----
Sync [Every hour...| v ]
-----
Suspend Syncing [ All, Shares, Mail | v ]
-----
[Cancel] [Save]
====
I think 'Suspend Syncing' of individual collections should be moved
to the 'Share' menu, which is how users generally manipulate sharing
settings for individual collections.
Once we have the ability to pick and choose which collections we
sync, the need to delete collections locally without removing them
from the server will lessen. But there is a bug logged to address
this issue separately as well: https://bugzilla.osafoundation.org/
show_bug.cgi?id=11165
Mimi
On Nov 3, 2007, at 6:49 PM, Andre Mueninghoff wrote:
Hi, Apologies for my not engaging earlier in this thread. After a
bit of
time with the new "Automatically Restored Published Shares" feature, I
have some feedback. It's only somewhat nice that it's automatic, and
it's a little too automatic from my perspective. To review, the
current
implementation begins to restore ones published shares immediately
after
one clicks the OK button to close the Accounts dialog (after having
entered username and password info for a Chandler Hub account).
There is
no warning that this is what will happen, and no option to cancel the
operation. Given the process intensity of the restore, Chandler
becomes
very sluggish if responsive at all. This could be alarming or
confusing
at best for users. Clues that a sync is occurring include (on Windows
XP) the processor jumping to 100% (with the familiar whirring of the
laptop processor cooling fan), and eventually in the sidebar, the
appearance of a familiar collection underneath the OOTB collections.
I appreciate the good intentions, but this new implementation is a
significant loss in flexibility for the user from the previous
implementation. At a minimum, it would be very helpful if the user
would
be prompted [Ok][Cancel] about whether to proceed with the restore.
And,
if the user proceeds with the restore, it would be very helpful to
have
presented next the list of published shares that are available to
restore. Perhaps an "All Shares" checkbox could be added to this
dialog
to streamline the path for those who really want all published shares
restored right then.
I typically do not want all my published shares on the Hub to be
restored to every other computer on which I install Chandler. For
example, on some computers, I want only certain collections that
primarily contain events like family and school calendars. Often, I
just
don't need all of the collections restored, and (if I already have my
Venti Gold Coast) would rather not wait while 15-20 collections
restored
before being able to proceed. Other times, for dogfooding, I would
like
to try and reproduce a bug with a collection or two that I would be
able
to share in a repository snapshot should I succeed in reproducing the
condition. I used to be able to selectively pick the collections I
wanted restored. Unless I'm missing something, now it seems to be
all or
nothing. As I have in the past, I suppose I could create a second user
account on the Hub and use it to subscribe to a subset of my own
collections, but in comparison to the simpler path available
previously,
this seems like a force-fit.
There's an interesting intersection with another relatively recent
change, that is, now when one deletes a published collection in
Chandler
Desktop, Chandler also will delete this collection from the Hub. I
guess
I also missed this thread on the list or something. And then I
foolishly
didn't read the friendly warning dialog from Chandler that told me
exactly what it was going to do. All of my collections are intact
on my
"master" instance of Chandler, thank goodness, but knowing this still
didn't prevent a small "amygdala hijack" when I first noticed the
half-
dozen collections missing from my Hub account and realized my error. I
will have to go find the relevant thread. I don't understand the
utility
to the user of automatically deleting published shares from the Hub
(even if the user is warned). Something like a [Yes][No] option for
the
Hub delete operation would be quite a bit more useful.
I'm sending this note to the Design list, because that is where the
"restore published shares.." thread seems to have lived. If this would
be better discussed on the Users list, please feel free to repost, or
let me know if you would like me to do that.
Cheers, Andre
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
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
