- Oct 29, 2020
-
-
Evangelos Ribeiro Tzaras authored
-
Evangelos Ribeiro Tzaras authored
-
Evangelos Ribeiro Tzaras authored
chatty v0.1.16
-
- Sep 23, 2020
-
-
Mohammed Sadiq authored
-
-
- Sep 18, 2020
-
-
- Sep 17, 2020
-
-
scootergrisen authored
-
- Sep 16, 2020
-
-
Mohammed Sadiq authored
And adapt to API changes
-
- Sep 14, 2020
-
-
Mohammed Sadiq authored
So that it can be used for all type of accounts
-
Mohammed Sadiq authored
And adapt to API changes. chatty_pp_account_is_sms() was using only chatty-item API. So moving it to chatty-item shall allow us to use the API in more cases, and not just for accounts
-
Mohammed Sadiq authored
And move the old chatty-chat to chatty-pp-chat So that we can use this as the base class for chats
-
- Sep 07, 2020
-
-
Fabio Tomat authored
-
Fabio Tomat authored
-
- Sep 02, 2020
-
-
Mohammed Sadiq authored
-
Mohammed Sadiq authored
-
Mohammed Sadiq authored
-
Mohammed Sadiq authored
-
Mohammed Sadiq authored
Use sorted_chat_list, which is now more appropriate.
-
Mohammed Sadiq authored
We now make use of ui_data for tracking various objects. And so we no longer have to lookup in lists to find the objects. Don't differentiate between IM and chats. Use a single liststore for any type of chats, and so we no longer require im_list, and related helper models.
-
Mohammed Sadiq authored
We don't have to list IM chats as buddies are listed separately
-
Mohammed Sadiq authored
-
Mohammed Sadiq authored
-
Mohammed Sadiq authored
-
Mohammed Sadiq authored
-
Mohammed Sadiq authored
-
Mohammed Sadiq authored
-
- Sep 01, 2020
-
-
Mohammed Sadiq authored
We were using the wrong variable to check for match resulting in surprising results
-
Mohammed Sadiq authored
So that we don't have to handle memory [de]allocations.
-
Mohammed Sadiq authored
-
Mohammed Sadiq authored
Use chatty_manager_add_chat() instead of chatty_manager_add_conversation() So that we have one less API. Also add_chat() adds chat to the right list instead of blindly adding to im_list, which was how it was done until now.
-
- Aug 31, 2020
-
-
Mohammed Sadiq authored
-
Mohammed Sadiq authored
libpurple may remove a node to simply add it again. It's hard to know if the removal happened simply to add it again or not. When an actual deletion happen, the associated PurpleConversation is deleted, and so tracking PurpleConversation alone can make this process simpler.
-
Mohammed Sadiq authored
-
Mohammed Sadiq authored
Otherwise the chat is simply destroyed, but the user is not left from the active conversation, if any. purple_conversation_destroy() shall do that.
-
Mohammed Sadiq authored
-
Mohammed Sadiq authored
-
- Aug 28, 2020
-
-
Mohammed Sadiq authored
This can be useful to get the IM chat of a buddy if it exists. Currently we use a liststore to do so, which shall be removed soon.
-
Mohammed Sadiq authored
We were blindly adding all chats to im_list. Let's check the chat type and add chat to the appropriate list.
-
Mohammed Sadiq authored
If ChattyChat has a PurpleBuddy or PurpleChat already set, the `ui_data` of the PurpleConversation wasn't updated when a conv is set for the chat. So instead, check for PurpleBuddy/PurpleChat after the `ui_data' is updated. Also, remove previously set `ui_data` for the conv already set in the chat, if any.
-
- Aug 27, 2020
-
-
Mohammed Sadiq authored
-