Add tracking of PurplePerson's to PurpleContactManager

Review Request #2055 — Created Nov. 10, 2022 and submitted

Information

pidgin/pidgin
default

Reviewers

The manager keeps track of all of this internally but exposes the collection of
people via the GListModel interface and exposes add_person and remove_person as
well.

Ran the unit tests.

Summary ID
Add tracking of PersonPerson's to PurpleContactManager
The manager keeps track of all of this internally but exposes the collection of people via the GListModel interface and exposes add_person and remove_person as well.
ff5705e3b709bcdad8e47466f460026220689773
Description From Last Updated

Unused.

QuLogicQuLogic

Unused.

QuLogicQuLogic

Are these signals not kind of redundant with the GListModel::items-changed one?

QuLogicQuLogic
grim
QuLogic
  1. 
      
  2. libpurple/purplecontactmanager.c (Diff revision 2)
     
     
    Show all issues

    Unused.

  3. libpurple/purplecontactmanager.c (Diff revision 2)
     
     
    Show all issues

    Unused.

  4. libpurple/purplecontactmanager.c (Diff revision 2)
     
     
    Show all issues

    Are these signals not kind of redundant with the GListModel::items-changed one?

    1. Yes and no? We could probably remove them just fine if we mentioned it in the docs for the object?

    2. The main difference though is that we give you the item that was added/removed which is probably easier than figuring out which added/removed via the GListModel signals, which I don't even thing you can do in the case of th removals as it happens after the fact.

  5. 
      
grim
grim
QuLogic
QuLogic
  1. Ship It!
  2. 
      
grim
Review request changed
Status:
Completed