add a registry for Dataprovider
Bug #462894 reported by
Markus Korn
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zeitgeist Framework |
Fix Released
|
Low
|
Siegfried Gevatter |
Bug Description
It should be possible to
* enable/disable some dataprovider (esp. useful for testing while developing and debugging)
* define which dataprovider sends events for which application (right now it is possible to have multiple DP per application, eg. are shipping a firefox logger and on the other hand there is an external FF extension which sends events. This can end in a race between both logger, and logging the same data twice is also not useful)
The preferences should be stored in a user readable format (ini like text file) but also be accessible over DBus.
Maybe this fits into a more general Configuration Interface I started some time ago.
Related branches
lp:~zeitgeist/zeitgeist/datasource.registry
- Markus Korn: Needs Fixing (diff)
-
Diff: 937 lines (+444/-89)17 files modified_zeitgeist/engine/Makefile.am (+1/-0)
_zeitgeist/engine/__init__.py (+2/-1)
_zeitgeist/engine/datamodel.py (+76/-0)
_zeitgeist/engine/extension.py (+8/-6)
_zeitgeist/engine/extensions/Makefile.am (+2/-1)
_zeitgeist/engine/extensions/blacklist.py (+3/-14)
_zeitgeist/engine/extensions/datasource_registry.py (+226/-0)
_zeitgeist/engine/main.py (+14/-13)
_zeitgeist/engine/remote.py (+17/-11)
_zeitgeist/loggers/datasources/recent.py (+34/-9)
_zeitgeist/loggers/zeitgeist_base.py (+15/-2)
doc/zeitgeist-daemon.1 (+1/-1)
doc/zeitgeist-datahub.1 (+2/-3)
doc/zeitgeist/source/dbus_api.rst (+6/-0)
test/engine-extension-test.py (+1/-1)
zeitgeist-datahub.py (+3/-5)
zeitgeist/datamodel.py (+33/-22)
Changed in zeitgeist: | |
assignee: | nobody → Markus Korn (thekorn) |
Changed in zeitgeist: | |
status: | Confirmed → In Progress |
Changed in zeitgeist: | |
assignee: | nobody → Laszlo Pandy (laszlok) |
Changed in zeitgeist: | |
milestone: | none → 0.3.3 |
Changed in zeitgeist: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Again redundant since our dataproviders will reside within applications