588b32b9c3
Now the purple add-on's starting to come together with a clear structure: * Add-on sends IM_MESSAGES etc to the server for processing * Server sends all (reply/etc) messages to add-on, which sends to app It's worth noting that on the add-on's side, no looper or handler is used for receiving messages, it's all through sending serialized BMessages to the add-on's connect_thread buffer. PurpleAccounts are now reliably associated with Cardie's account names and the thread ID of their respective connect_thread. The GLib main-loop is gone over regularly thanks to a message runner. Now, the add-on can log into/create accounts, connect to them, and send the IM_PROTOCOL_READY notification to Cardie as appropriate.
18 lines
309 B
Plaintext
18 lines
309 B
Plaintext
#include "Purple.h"
|
|
|
|
resource app_signature PURPLE_SIGNATURE;
|
|
|
|
resource app_version {
|
|
major = 0,
|
|
middle = 0,
|
|
minor = 1,
|
|
|
|
variety = B_APPV_ALPHA,
|
|
internal = 0,
|
|
|
|
short_info = "Libpurple add-on for Cardie",
|
|
long_info = "©2021 Jaidyn Levesque"
|
|
};
|
|
|
|
resource app_flags B_SINGLE_LAUNCH | B_BACKGROUND_APP;
|