[Pidgin] #2238: [Feature Request] add buddy by protocol NOT account

[Pidgin]

#2238: [Feature Request] add buddy by protocol NOT account
--------------------------+-------------------------------------------------
 Reporter:  eibwen        |       Type:  enhancement
   Status:  new           |   Priority:  minor      
Component:  pidgin (gtk)  |    Version:  2.0.2      
 Keywords:                |    Pending:  0          
--------------------------+-------------------------------------------------
 The "Add Buddy" dialog currently prompts for the account to add the buddy.
 This requires one to know which protocols are compatible; however the
 information most readily available to the end user is merely which
 protocol their contact uses.

 This is also a bit counter-intuitive.  Consider:
 {{{
 To Account A of Protocol B, add Buddy C (of Protocol D)
 }}}
 versus
 {{{
 Add Buddy C of Protocol D to Account A (of Protocol B)
 }}}

 To resolve these issues the dialog should be revised, eg:

 {{{
 Contact's Protocol: [ComboBox]
 Contact screenname: [Entry]
 Contact Alias:      [Entry]
 Contact Group:      [ComboBoxEntry]
 Compatible Account: [ComboBox]
 }}}

 with a signal_connect such that when the contact's protocol is changed,
 the compatible account list is modified accordingly.

 There is the consideration of what to do if the user wants to add a
 contact on a protocol for which they do not have a compatible account.  I
 see two possibilities: either only show contact protocols that are
 compatible with existing accounts, or show all supported protocols and
 only associate them with an account if a compatible account is available.

 The latter (albeit likely through libpurple) would have the additional
 benefit of being able to record contact information without requiring an
 account on a compatible protocol.  A hook could be added such that when an
 account on a compatible protocol is created, the contacts can be
 optionally added to the account.  After all, it's much easier to record
 such information as it becomes available, rather than trying to find it
 after it's become usable.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/2238>
Pidgin <http://pidgin.im>
Pidgin