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

2010-04-19 Thread Siegfried Gevatter
I don't think there's anyone working on this right now?

** Changed in: zeitgeist
   Importance: High = Medium

** Changed in: zeitgeist
   Status: In Progress = Confirmed

** Changed in: zeitgeist
Milestone: 0.3.1 = 0.3.4

** Changed in: zeitgeist
 Assignee: Markus Korn (thekorn) = (unassigned)

** Summary changed:

- [lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions 
to the engine configurable
+ Make the loading of extensions to the engine configurable

-- 
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
Framework Team, which is subscribed to Zeitgeist Framework.

Status in Zeitgeist Framework: Confirmed

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.



___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help   : https://help.launchpad.net/ListHelp


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

2009-12-17 Thread Mikkel Kamstrup Erlandsen
** Branch linked: lp:~kamstrup/zeitgeist/blacklist

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



___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help   : https://help.launchpad.net/ListHelp


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

2009-12-17 Thread Mikkel Kamstrup Erlandsen
I just linked lp:~kamstrup/zeitgeist/blacklist to this report because it
contains some initial work needed to load extensions dynamically. The
work is not nearly done, nor tested or documented, so please hold your
reviews back a bit until I ping you :-)

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



___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help   : https://help.launchpad.net/ListHelp


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

2009-11-26 Thread Mikkel Kamstrup Erlandsen
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 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.

___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help   : https://help.launchpad.net/ListHelp


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

2009-11-26 Thread Seif Lotfy
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.kamst...@gmail.com

 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.

___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help   : https://help.launchpad.net/ListHelp


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

2009-11-16 Thread Mikkel Kamstrup Erlandsen
There is quite a lot of whitespace twiddling in your branch, making it
hard to review...

I can not see exactly how you plan to load the extensions and how you
plan to use the __public_methods__ of the extensions..?

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

___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help   : https://help.launchpad.net/ListHelp


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

2009-11-16 Thread Siegfried Gevatter
Looks good, but:
 - Get ride of the whitespace changes.
 - Please avoid using two underscores (__) for variable names, let's keep those 
for in-build Python stuff.

How will you get those methods into the D-Bus?

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

___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help   : https://help.launchpad.net/ListHelp