zeitgeist team mailing list archive
-
zeitgeist team
-
Mailing list archive
-
Message #04089
[Branch ~zeitgeist/zeitgeist/bluebird] Rev 253: Update extension base class docstring.
------------------------------------------------------------
revno: 253
committer: Siegfried-Angel Gevatter Pujals <siegfried@xxxxxxxxxxxx>
branch nick: bluebird
timestamp: Sat 2011-09-17 12:41:24 +0200
message:
Update extension base class docstring.
modified:
src/extension.vala
--
lp:~zeitgeist/zeitgeist/bluebird
https://code.launchpad.net/~zeitgeist/zeitgeist/bluebird
Your team Zeitgeist Framework Team is subscribed to branch lp:~zeitgeist/zeitgeist/bluebird.
To unsubscribe from this branch go to https://code.launchpad.net/~zeitgeist/zeitgeist/bluebird/+edit-subscription
=== modified file 'src/extension.vala'
--- src/extension.vala 2011-09-05 16:16:36 +0000
+++ src/extension.vala 2011-09-17 10:41:24 +0000
@@ -23,17 +23,14 @@
/**
* Base class for all extensions
*
- * FIXME: figure out what to do with this. I don't really see
- * what the point for it is, since D-Bus accessible stuff is
- * usually exported on a new interface. --RainCT
- * Every extension has to define a list of accessible methods as
- * 'PUBLIC_METHODS'. The constructor of an Extension object takes the
- * engine object it extends as the only argument.
- * ---
- *
- * In addition each extension has a set of hooks to control how events are
- * inserted and retrieved from the log. These hooks can either block the
- * event completely, modify it, or add additional metadata to it.
+ * The constructor of an Extension object takes the Engine object
+ * it extends as the only argument.
+ *
+ * Extensions have a set of hooks with which they can control how
+ * events are inserted and retrieved from the log.
+ *
+ * Additionally, extensions may create their own D-Bus interface
+ * over which they can expose their own methods.
*/
public abstract class Extension : Object
{