(bkirsch, question for at the bottom.)
Oh I think the default is the WebDAV because we're waiting to switch
the default to the new sharing f/w?
On Apr 17, 2007, at 10:47 AM, Morgen Sagen wrote:
No, I would like to be able to create a Chandler Hub Sharing
account (which uses the new morsecode protocol), and have it be the
default. Any time a user has more than one sharing account, they
should be able to choose one to be the default when publishing.
The real problem is that if your default sharing account is not
filled in, you can't publish anything, even though you *have* added
another sharing account that is filled in. Since there is no way
to tell Chandler to make the new account the default, Chandler will
continue to try and use the out-of-the-box default account, which
if not filled in, will prevent you from publishing.
Oh that's weird.
To work around this for now, I added code that does the following:
When you click Ok in the accounts dialog, it will see if your
default account is one that is not filled in. If so, it will look
to see if the user *has* filled in any other sharing accounts, and
will randomly select one to be the new default. This at least gets
around the following scenario people have been running into:
Does this work for email accounts too?
1) Start a new Chandler
2) Create a collection to share
3) Bring up Accounts dialog
4) Create new Chandler Hub Sharing account and fill it in
5) Try to publish the collection
6) Chandler complains that you haven't set up a Sharing account
(because the default sharing account is not filled in)
My workaround prevents #6 from happening because the account
created in #4 will be automatically be the default.
So it just hit me that since your first question was whether there
*was* a default sharing account out of the box, that maybe you
don't really think we *need* the notion of a default account. If
that's the case we need to resolve this because the current account
dialog and sharing code is geared toward having a default account
to use. We *could* get rid of the notion of a default sharing
account, but as someone who has quite a few sharing accounts, I
appreciated being able to select a default from time to time. We
either need to embrace the notion of a default or get rid of it,
because at the moment we're in a state of limbo.
I think having a full-blown Defaults functionality is kind of
complicated, I'd prefer to avoid addressing this before Preview? The
current notion of Default is simply to let the user know that there
are 3 OOTB accounts that cannot be deleted. But perhaps that's
unnecessary? If an user wants to delete an account, they should be
able to?
bkirsch, do you have any thoughts on this? Am I forgetting something?
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
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
