It sounds like we have a plan? But I wanted to address some of
Morgen's questions/points below...
Mimi
On Apr 17, 2007, at 1:46 PM, Morgen Sagen wrote:
I agree that at some point, we will need to have a more
sophisticated notion of Default accounts.
I'm not sure what was wrong with what we had before.
I proposed that we cut the feature from the account set up UI for 4
reasons:
1. With the additional fields added for the new mail features, namely
auto-configure, set up special Chandler IMAP folders and verbiage
explaining how mail will be downloaded from the server, the dialog
was getting cluttered and ungainly, especially because it is hard to
get things to line up correctly on all 3 platforms.
2. We got feedback that the single-radio-button-per-account UI we had
was awkward, so we would have needed to put work into improving the
interaction design.
3. It felt like a gamble to spend time on making this feature work
well given that
a. we're not sure how many users will set up more than one outgoing
email account
b. we're not sure how often users will send email
c. publishing shares is not an oft-repeated task
4. There were also other user modelling issues I wanted to avoid.
What does default email account mean for sending message items? For
replies and forwards, does it override the email account the original
message was sent to?
All of this amounted to: If we remove the notion of user-defined
default email and sharing accounts for Preview, we simplify the
design and avoid having to address a bunch of visual polish / layout,
interaction design and user modeling issues. On the downside, we lose
some functionality which can be very useful in certain situations.
But in the end, it *didn't* feel like (sorry brace yourself for
double negatives) *not* having user-defined default accounts was
going to affect our bottom line: Get people outside of OSAF to
Dogfood. (Phew.)
Does that make more sense?
Of course, I didn't realize at the time that it would screw up
existing sharing functionality :( But it sounds like we have a
workaround? I still feel like addressing the issues listed above
would be a significant chunk of work, not worth doing for Preview?
One question: Morgen, the hack you described below doesn't
actually change anything that the user can see?
It is a subtle change: if you bring up a fresh Chandler, add a
sharing account (without filling in the out-of-the-box DAV
account), then when you close the dialog, the account you just
added becomes the new default sharing account (which you'll see
marked as "Default" the next time you open the accounts dialog, and
which will be auto-selected the next time you publish a
collection). If you happened to add multiple accounts at that
time, then one is randomly selected as the new default.
Okay, so I think I'm saying I don't want this to happen. I don't want
the user to see the (Default) text move to an user-defined account.
I'm proposing we keep it so that it works the way I experienced it in
r13983.
It just skips over the OOTB default sharing account and uses the
next sharing account in the list as the default under the hood? I
just tried Publishing in r13983.
That works because of the hack I added in rev 13981.
I think then what we have now for both Mail and Sharing is okay
for Preview?
I will go ahead and also add the logic that bkirsch added for Mail,
and we're done for Preview.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
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
