Chat-O-Matic/protocols/purple
Jaidyn Ann 588b32b9c3 (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
..
Makefile Returning libpurple protocol amount and names 2021-06-23 23:57:27 -05:00
Purple.h (purple) Main loop, server→add-on→app communication 2021-06-27 16:46:38 -05:00
PurpleApp.cpp (purple) Main loop, server→add-on→app communication 2021-06-27 16:46:38 -05:00
PurpleApp.h (purple) Main loop, server→add-on→app communication 2021-06-27 16:46:38 -05:00
PurpleMessages.h (purple) Main loop, server→add-on→app communication 2021-06-27 16:46:38 -05:00
PurpleProtocol.cpp (purple) Main loop, server→add-on→app communication 2021-06-27 16:46:38 -05:00
PurpleProtocol.h (purple) Main loop, server→add-on→app communication 2021-06-27 16:46:38 -05:00
purple.rdef (purple) Main loop, server→add-on→app communication 2021-06-27 16:46:38 -05:00