README.dbus@099cbddc7907
README.dbus
Mon, 05 Dec 2005 21:46:47 +0000
- author
- Luke Schierer <lschiere@pidgin.im>
- date
- Mon, 05 Dec 2005 21:46:47 +0000
- changeset 12360
- 099cbddc7907
- parent 11067
- b6353889a9ba
- permissions
- -rw-r--r--
[gaim-migrate @ 14664]
Faceprint is concerned about 2 things:
1)some of the random colors are very close together.
as best we can tell, there are two ways to fix this
1a) for each proposed color, iterate the entire list of selected
colors, looking to ensure that it is not too close to any of them.
this is an O(n^2) operation, with n >= 220 (the current number of
colors we look for)
1b) iterate the entire set of possible colors, skipping ahead by some
guess (rather than iterating by 1). this is an O(n^3) operation,
where n is 65535/(whatever we skip ahead by). This is not only a
more expensive operation, but because of the nature of the color
list, it is not _necessarily_ going to yield more predictable
results, skipping ahead 5 (or any other number) does not necessarily
guarantee that you've skipped 5 very similar colors.
2) as you can see, either solution to #1 is potentially a resource hog.
#1a is a random delay, #1b is inherently expensive. How often #1a will
exceed the bound #1b, if ever, is unknown.
rather than doing either of these, we settled on a middle course: a .h
file has been created containing a set of colors. currently the set we
were previously hard coded to. Gaim will search that list for usable
colors and start randomly looking only if that list does not contain
sufficient usable colors. ideally this list would be generated to have
colors that are known to be a "safe" distance appart, that is colors that
you can tell appart. and Ideally it would have a (small) multiple of the
number of colors we are searching for. This should ensure that IF we go
to randomly searching, we need do so only for a few colors.
Right now I have no good way to generate a "safe" list of colors though.
This file describes how to compile and run gaim with dbus support. Hopefully, most of the steps from point 3 will soon be automated. 1. Make sure you have the latest version (0.34) of the dbus library installed, including glib bindings. http://www.freedesktop.org/Software/dbus 2. Compile gaim ./configure --enable-dbus make make install 3. Configure your dbus instalation for gaim A. Find your dbus session configuration file, usually /etc/dbus-1/session.conf B. In that file, find the <servicedir> section. This section contains the directory that stores files describing services, usually /usr/share/dbus-1/services C. Copy src/dbus-gaim.service to that directory D. Edit the dbus-gaim.service file you've just copied, and replace the path in the "Exec=" line with the path to your gaim executable. 4. Start Session DBUS if you haven't done it already eval `dbus-launch --session` export DBUS_SESSION_BUS_ADDRESS DBUS_SESSION_BUS_PID These commands will set the two above shell variables. These variables must be set before running any dbus-aware programs. Start gaim as usual. To communicate with it, use "gaim-send". When you execute gaim-send, the dbus system will automatically start a gaim process if one is not running already.
