jadedctrl/Chat-O-Matic
jadedctrl/ Chat-O-Matic
1
0
Disbranĉigi 0
Fontkodo Issues 20 Tirpetoj Actions Packages Projects Eldonoj 2 Wiki Activity
Chat-O-Matic/protocols/purple/purple.rdef

18 lines
311 B
Plaintext
Raw Normal View History

(purple) Main loop, server→add-on→app communication 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.
2021-06-27 16:46:38 -05:00
#include "Purple.h"
resource app_signature PURPLE_SIGNATURE;
Init libpurple add-on
2021-06-22 14:42:07 -05:00
resource app_version {
major = 0,
middle = 0,
minor = 1,
variety = B_APPV_ALPHA,
internal = 0,
Rename Cardie to Chat-O-Matic
2021-08-19 02:28:06 -05:00
short_info = "Chat-O-Matic libpurple add-on",
Init libpurple add-on
2021-06-22 14:42:07 -05:00
long_info = "©2021 Jaidyn Levesque"
};
Returning libpurple protocol amount and names The libpurple add-on has been split into two parts― a background process that will actually interface with libpurple, and an add-on that acts as intermediary between Cardie and the process. This helps prevent redundancy, and is giving me a lot less trouble that directly loading libpurple. The protocol amount and names are now returned by the add-on (through protocol_count() and protocol_at() respectively)― you can see them in Preferences' protocol list.
2021-06-23 23:57:27 -05:00
resource app_flags B_SINGLE_LAUNCH | B_BACKGROUND_APP;