As a developer I would like to integrate my private watchers to the aw-qt without necessity to alter the aw-qt and maintain my own fork.
Currently aw-qt (v0.8.0b9) supports only few modules that are hard-coded in:
Posible solutions:
Based on TODO in
|
# TODO: Fetch these from somewhere appropriate (auto detect or a config file) |
aw_qt/manager.py:
# TODO: Fetch these from somewhere appropriate (auto detect or a config file)
# Save to config wether they should autostart or not.
_possible_modules = [
"aw-server",
"aw-watcher-afk",
"aw-watcher-window",
# "aw-watcher-spotify",
# "aw-watcher-network"
]
- Available modules and modules to be started automatically will be listed in new
aw-qt configuration.
- Autodetect available modules. Modules to be started automatically will be listed in new
aw-qt configuration.
NOTE: Available modules can be separated to independent issue/story (nice to have).
As a developer I would like to integrate my private watchers to the
aw-qtwithout necessity to alter theaw-qtand maintain my own fork.Currently
aw-qt(v0.8.0b9) supports only few modules that are hard-coded in:aw-qt/aw_qt/manager.py
Line 129 in fcb5926
Posible solutions:
Based on TODO in
aw-qt/aw_qt/manager.py
Line 127 in fcb5926
aw-qtconfiguration.aw-qtconfiguration.NOTE: Available modules can be separated to independent issue/story (nice to have).