zeitgeist team mailing list archive

[Markus Korn <thekorn@xxxxxx>]

For me there is only one question left to fix this bug: How should
methods of extensions be accessible?

Right now they behave like direct members of the engine:
   engine.some_extension_method()

There are also some possible alternative solutions:
   engine.extensions.some_extension_method()
   engine.extensions.NameOfExtensionClass.some_extension_method()

As this is only internal stuff, I think we are safe to go with the
current implementation and change over to another one if necessary (e.g.
when we get a huge number of extension methods)

IMO this is the only open question we should discuss before merging this branch into lp:zeitgeist.
What do you think?

-- 
[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.