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) =>
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-reson
** 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 r
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
> I believe Markus' branch was merged and the focus stuff removed for now?
> So we can close this bug?
>
> --
> [lp:~zeitgeist/zeitgeist/
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
I think I like the engine.extensions.some_extension_method() approach
the best.
This way alternate extensions can provide the same method and the caller
does not need to know who implements it.
--
[lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions to
the engine configu
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()
en
sorry, I wanted to link the demo/doctest directly here
http://bazaar.launchpad.net/~thekorn/zeitgeist/zeitgeist-resonance_extensions/annotate/head%3A/test/test-engine-extension.rst
--
[lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions to
the engine configurable
https://
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
I think that extensions should expose their own DBus APIs. The engine
could expose its server-object to allow extensions to do this cleanly...
Regarding the two underscores; the gobject bindings use such constructs
as well (for __properties__ and __signals__). So if we have a *really*
good reason
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
t
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 t
I added a branch with the general workflow I foresee, any opinions
(test/resonance-engine-extension-test.py
has an example)
Code still needs some work.
** Branch linked: lp:~thekorn/zeitgeist/zeitgeist-resonance_extensions
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (the
+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 Engine.
Status in Zeitgeist
** Changed in: zeitgeist
Importance: Undecided => High
** Changed in: zeitgeist
Milestone: None => 0.3
--
[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 beca
15 matches
Mail list logo
