Changes between Version 5 and Version 6 of GSoC2010/DetachableLibpurple

Timestamp:

Aug 11, 2010, 6:47:29 PM (13 years ago)

Author:

gillux

Comment:

Added finch, dbus notes and fixed a typo.

GSoC2010/DetachableLibpurple

@@ -24 +24 @@
 == End-user usage ==
 '''The project isn't usable yet.'''
+
 But if you really want to see something and you know how to use a command line, you can play with what's available:
 
@@ -36 +37 @@
 5. Pidgin should says that no accounts are activated. Activate one if you want.
 
-6. Run as many other pidgin sessions as you want repeating step !#4.
+6. If you want, run as many finchs (again on the same host) as you want too typing {{{./finch/finch -r}}}.
 
-Now you can try to manipulate the ''Accounts'' window of all the running pidgins, and see that they are syncronized. Awsome, isn't it?
+7. Run as many other pidgin sessions as you want repeating step !#4.
+
+Now you can try to manipulate the ''Accounts'' window of all the running pidgins and finchs, and see that they are syncronized. Awsome, isn't it?
 
 == Applications that uses libpurple ==
-To make your fancy libpurple-based GUI to work in the so-called detachable mode, juste add the following code before the {{{purple_core_init()}}} call.
+To make your fancy libpurple-based GUI to work in the so-called detachable (or remote) mode, first make sure the libpurple you are used have dbus support enabled. Then just add the following code before the {{{purple_core_init()}}} call.
 {{{
 purple_core_set_running_mode(PURPLE_RUN_REMOTE_MODE);
@@ -52 +55 @@
 
 Then use the libpurple API normally. Your libpurple should contact the local dbus server and get synchronised with the purpled daemon.
+Note that if your have core plugins, you'll probably have to add the dbus cflags to their makfiles to make them compile.
 
 = Details of the hack =