Hi,
The following patch adds an add_point dbus method to the firepaint
plugin which adds a fire particle at a specific point.  This is in
analogy to the annotate plugin, which has a dbus interface for drawing
various shapes.

http://easystroke.sourceforge.net/firepaint-dbus.patch

A few comments:

1.  My motivation for this is that I'm the author of the easystroke [1]
gesture recognition program and I thought it'd be cool to be able to
draw gestures as fire (I guess I shouldn't take credit here, one of my
users actually came up with the idea).  This is probably also the
easiest way to test the patch;  the functionality is implemented in the
latest development tree [2].  Note that you'll need to invoke the
program as "./easystroke -e" in order to see the "Preferences/Method to
show strokes/Fire" option.

2.  On slower hardware (or when using a huge particle size), compiz
might stop responding to dbus events until some other action such as
minimizing a window is taken.  This is due to the fact that the compiz
main loop goes something like "while (XPending(dpy)) { ... }", so if
event processing takes too long, compiz is stuck in that loop and won't
check if any file descriptors have become available for reading.

3.  add_point takes two floating point arguments even though the data is
intermediately stored as an XPoint, i.e. a pair of ints.  This seemed
like an artificial limitation to me that could easily be lifted, so I
thought it would be more appropriate to use floats, which is also what
annotate does.

4. Should this be documented somewhere?  The only documentation for the
annotate actions that I could find was the source of the plugin (which
is fine by me, anyway).


Thanks,
Tom

[1] http://easystroke.sf.net
[2] darcs get http://easystroke.sourceforge.net/easystroke
_______________________________________________
Dev mailing list
[email protected]
http://lists.compiz-fusion.org/mailman/listinfo/dev

Reply via email to