[Pidgin] #11764: Account Names

[Pidgin]

#11764: Account Names
------------------------------+---------------------------------------------
 Reporter:  tristangrimaux    |        Owner:           
     Type:  enhancement       |       Status:  new      
Milestone:  Plugin Suggested  |    Component:  libpurple
  Version:  2.6.2             |   Resolution:           
 Keywords:  account name      |  
------------------------------+---------------------------------------------

Comment(by tristangrimaux):

 Replying to [comment:8 darkrain42]:
 > Do not adjust the milestone.
 Ok!

 > A plugin can still do most of the actions you've described (admittedly,
 mucking around with the tooltip requires string-matching, but we'd likely
 accept patches to make that easier (probably by using the
 !PurpleNotifyUserInfo struct)).
 The problem is not on libnotify. I've already created a patch which is for
 my personal use, but if I am taking the time to write this down is to give
 something back to the community. Adding a name for the account, and
 optionally an icon for it fits perfectly on the classes structure and
 solves many issues around it.

 Please, remember this problem is really easy to see when the user makes a
 heavy use of Pidgin and he is not an expert or a powerful user.

 >  Since you've clarified that you mean the ''protocol icon'' (not a
 default icon for buddies on that protocol, or something), that's not
 currently possible, but there are other tickets which cover that (#11339).

 Please, read carefully: it is NOT the protocol icon what I mean: its the
 account icon.

 There might be three different icons: the buddy icon, wich should be a
 nice picture of the user, the account icon, that might be the Facebook
 isologo, or the GMail one, or it might be a picture of my university. It
 might be as well a Facebook icon with a 2 over it to describe it as my
 second account on Faceboock. And finally it is the protocol icon which is
 the way the user rapidly understands what is capable of doing under that
 account.

 In fact, when creating a wizard to add an account, it could list the
 Facebook account type which only asks for username and password, and it
 automatically creates an account with the name Facebook, the icon and the
 server data already filled. Adding account types make more sense than
 adding a custom protocol which creates an unnecessary overhead over the
 classes structure. It's really better than adding custom icons for a
 protocol which really does not fit anywhere.

 >
 > I did read and understand it, after you clarified what you meant.  In
 any event, I don't think this belongs in libpurple or Pidgin proper (I
 don't think it has widespread appeal;
 I really appreciate the time you are taking to read my really long posts,
 but I think I have a strong point: it's a natural fit for libpurple.

 >
 > places already list the account name -- which /is/ sufficiently unique
 for the purposes you're describing,
 Places do not list the account name, it lists the user at server which is
 unique, but does not necessarily describe the account. If I add an account
 for a network hosted on a ridiculous domain, I will not remember that
 myuser at ridiculousname is the network I've connected. A name describes the
 object, the id might be unique, but it will never help the object to have
 a descriptive name.

 Think of this: the user needs to adjust the notification settings from an
 account. This is a good thing to implement on a plugin. If the username
 changes because of anything on that account, the filter will stop working
 unless updated. The fact that those properties are unique to the account
 do not uniquely identify it. This is just an example to show what I think
 it might be a flaw on the classes structure.


 > even if it's not "as easy" as you'd prefer --
 Adding a property to a class is not one of the trickiest things to do.

 > or should list the account name / Local Alias (the conversation dialog
 being a notable exception -- without sending a message, it's not possible
 to determine from which account the message is to be sent, but I believe
 there's a ticket for that and it certainly doesn't fall under the general
 scope of this ticket).

 This suggestions fits perfectly to solve that issue too: you open a
 conversation dialog and it might display

 Marie from Facebook

 which is perfectly descriptive rather than stating

 Marie from user at chat.facebook.com

 with a combo-box over the contact name it would be easier to change the
 account you will be using to send that message to 'Marie From Msn' on the
 case you have grouped the contact under several accounts.

 When adding a buddy, it is unclear for the NON GEEK user to determine from
 which account he will be adding that contact. The user only has a combo-
 box with a really long jumble about some user at server and the protocol
 icon, which in many occasions will be a lot of XMPP icons. If the combo
 lists the account names and the account icon in a generously tall combo,
 the user will understand easily what is he doing.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/11764#comment:10>
Pidgin <http://pidgin.im>
Pidgin