← 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

 

I don't think we reached the configurable state yet! we should look into it
though for 0.3.1 so for now we can dismiss it

2009/11/26 Mikkel Kamstrup Erlandsen <mikkel.kamstrup@xxxxxxxxx>

> I believe Markus' branch was merged and the focus stuff removed for now?
> So we can close this bug?
>
> --
> [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.
>
>


** Changed in: zeitgeist
    Milestone: 0.3.0 => 0.3.1

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

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.



References