← Back to team overview

zeitgeist team mailing list archive

[Bug 483556] Re: [lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions to the engine configurable

 

Sorry, just fixed the whitespace issue to keeps the diff as small as possible; $SOMEONE told my editor to use tabs for indention in all zeitgeist branches, the fact that we are using spaces in some parts of the source code is maybe another bug.
I also renamed __public_methods__ to PUBLIC_METHODS.
We can also register DBus methods dynamically but I don't think we have real use for it right now, let's keep it as simple as possible for now.

I've also added a doctest for the extension mechanism at 'test/test-
engine-extension.rst', this file also demos more clearly how this all
works. Is it more comprehensible?

-- 
[lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions to the engine configurable
https://bugs.launchpad.net/bugs/483556
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Engine.

Status in Zeitgeist Engine: In Progress

Bug description:
right now the relevancy-provider is loaded by default. Unfortunately this extension is kind of buggy and not well tested, so in case of errors while loading this extension the whole engine would fail to run.
We need a configurable plugin-system for our extensions, and for now we should per default disable loading the relevancy provider. If this provider gets more stable we should easily be able to add this extension to the default extensions which are automatically loaded on engine initialization.



References