Comment 15 for bug 483556

what about having the extensions listed in a json file :)

2010/2/16 Mikkel Kamstrup Erlandsen <email address hidden>

> We can load/unload dynamically to some degree now. Since I merged the
> blacklist branch we load extensions defined as a list of strings inside
> _zeitgeist.engine.__init__.py. The final piece of the puzzle IMHO is to
> allow the user to override this list via an env. var.
>
> Loading and unloading of extensions during a session is not worth the
> effort I think and also adds considerable DBus book keeping in order to
> ensure that we close extensions with DBus interfaces cleanly. So only
> loading from a pre-defined set at startup if you ask me.
>
> --
> [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 subscribed to The
> Zeitgeist Project.
>
> Status in Zeitgeist Framework: 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.
>
>
>
>