OpenPrinting / OpenPrinting/system-config-printer
Please reduce the dependencies of the dbus backend
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 204
- Forks
- 108
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 9
Description
KDE Plasma's print-manager relies on the system-config-printer dbus services for some functionality:
- New device notifications
- Device discovery and grouping
- Recommended driver discovery
It doesn't use the UI parts of system-config-printer (that look a bit out of place in a Plasma desktop). Nevertheless, because system-config-printer is currently quite monolithic (even scp-dbus-service.py imports Gtk and friends and their python bindings), it pulls in a large dependency chain.
It would be great if the dbus functionality relied upon by alternative UIs like plasma print-manager could be made independent of the UI portions to avoid the dependency chain (and memory usage by multiple toolkits etc).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with scp-dbus-service.py and map its Gtk and other UI imports against the D-Bus functionality used by Plasma print-manager. Define the separation so device notifications, discovery and grouping, and recommended-driver discovery work without the UI dependency chain; done when those services no longer require the UI toolkits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100