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. |
||
---|---|---|
application | ||
data | ||
libs | ||
protocols | ||
smileys | ||
Contributors | ||
License | ||
Makefile | ||
Makefile.common | ||
README.md |
Cardie
A multi-protocol chat program.
Building
You can make Cardie and its protocols with:
$ make
Cardie itself requires the expat_devel
package, the XMPP protocol requires
gloox_devel
, and the (provisional) IRC protocol requires libircclient_devel
.
The (unusable and experimental) libpurple add-on requires libpurple_devel
and
glib2_devel
. You can also build either independent of the other:
$ make caya; make libs; make protocols
License
Cardie itself is under the MIT license, but licenses vary for the included libraries and add-ons.
The xmpp
and purple
add-ons are under the GPLv2+, and irc
the MIT license.
libsupport
is under the MIT license, though containing some PD code.
librunview
contains code from Vision, and is under the MPL.
libinterface
is under the MIT license.