[Pidgin] #9572: Dealing with BlistNodeOther

[Pidgin]

#9572: Dealing with BlistNodeOther
-----------------------+----------------------------------------------------
 Reporter:  aluink     |     Owner:  aluink
     Type:  task       |    Status:  new   
Component:  libpurple  |   Version:        
 Keywords:             |  
-----------------------+----------------------------------------------------
 The current plan for implementing GObject for Blist and its types is to
 have an abstract type called PurpleBlistNode and subtype 4 other types,
 Contact, Group, Buddy, and Chat to replace each's respective
 PurpleBlistNodeType, respectively.  This works all well except that in a
 few instances there has been usage of PURPLE_BLIST_OTHER_NODE.  This has
 mostly been found in gntblist and its grouping plugin.

 There was short discussion about this problem in #8597.  At first, there
 are two obvious solutions.  We could make PurpleBlistNode a concrete type,
 and be done with it.  But then we hinder the original idea of having a
 parent type for all Blist types.  The other idea is to have yet another
 subtype.  Of course there are possibly other solutions.

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