On Sun, Dec 04, 2005 at 11:36:52AM -0800, Sean Egan wrote:
> On 12/3/05, Luke Schierer <lschiere@...> wrote:
> > In 1.x, many people do not realize that they can sign on multiple
> > accounts at once, precisely because they never find this dialog.
> > They will still fail to find it: gaim does not open it by default
> > except perhaps for a totally new user. (nor should it, except with
> > the -n flag, but the usability flaw remains)
> This problem is because we started Gaim with a "Login" window that was
> single-account-centric. Even when we gave the Login window a drop-down
> and showed the Accounts window on start, it still looks like you
> create accounts in the Account window and then choose which one you
> want logged in from the Login window dropdown. Toggling a checkbox
> isn't an obvious way to perform an option like logging in.
Removing the login window will help. I do not think it will be
sufficient. I also do not think the "Enabled" button will prove
> In 2.0.0, with the Login window gone, and the only checkbox in the
> Accounts dialog being an "Enabled" boolean option, I'd argue creating
> and managing new accounts is much more self-evident.
> > In 1.x, no one figures out how to change their buddy icon. It
> > doesn't make sense that you go to a dialog that appears to be about
> > account creation to change account settings.
> Sure. Now, though, with the login window gone, it no longer appears to
> be solely about account creation. Anyway, the main problem here is
> that people want to set their buddy icon only once and have it affect
> all their accounts, so they look for some single global preference.
Some want it to be global. Others have stated that they looked first
in "Account Actions."
> Having only enabled accounts in an Accounts menu and giving each of
> those a "Set buddy icon..." choice might be a better temporary fix.
> > I'd argue that the dialog is a PAINFULL UI for any of the actions
> > currently in the 1.x "Account Actions" submenu. IFF a menu is truly
> > bad UI, then the logic would be to totally remove that menu,
> A menu is really bad UI for creating and deleting things. It's good UI
> to access features. That's why I think an Accounts menu with features
> for each enabled accounts plus a dialog to manage all accounts makes
I can agree here. it is not ideal for add/remove. I consider
"enabled"/disabled to be far more "accessing features" than
Really I envision that there are more or less two sets of "typical"
users out there.
One set will have one set of accounts nearly all of which will be
enabled nearly all the time. These users will need to access the
"enabled" checkbox most often to fix some fatal error state.
A second set has two mental sets of accounts that they alternate
between. "work" and "home" for example. Such users would have in
fact been better served by the account groups UI that was proposed at
one point. Our current UI (with the accounts dialog, not the menu)
comes closest to serving these users while still keeping things
simple for the other set. The dialog does enable fast switching of
enabled/disabled for multiple accounts in a way the menu does not.
The accounts menu will make life easier and more intuitive for the
first set with some cost to the second set. I suppose the question
is which set is bigger.
The menu certainly fits _my_ use case more nearly. While I do have
40 some odd accounts, which does make the menu somewhat over-long, I
nearly always use a single set of them, esp. now as our status
support improves to the point of allowing them not all to have the
exact same state. I'm increasingly nearly always in a "custom" state
(though it should really list the name of the "saved" state in use)
the menu lets me quickly enable or disable specific accounts as
something unusual enough to not cleanly match a state (such as
jabber.org being down in a way gaim crashes in responce to, or
wanting to test things with some spare account).
> Author of Open Source Messaging Application Development: Building and
> Extending Gaim: http://gaim.sf.net/book.php