KubuntuHWDB
|
Size: 1733
Comment:
|
Size: 3096
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 10: | Line 10: |
| Port HWDB to KDE. | Allow Kubuntu to have a HWDB frontend. |
| Line 14: | Line 14: |
| HWDB is a handy tool for taking information on users hardware, we should have a client for it in Kubuntu. | HWDB is a handy tool for taking information on users hardware; we should have a client for it in Kubuntu. The current client is GTK only and therefore unsuitable for default install in Kubuntu. |
| Line 18: | Line 18: |
| Oliver wants to report a hardware support bug in Kubuntu but want to include a HWDB reference to have the maximum information available to the bug readers. | Oliver wants to report a hardware support bug in Kubuntu but wants to include a HWDB reference to have the maximum information available to those reading the bug. Daniel wants to help Kubuntu and Ubuntu build up information on which hardware is supported but as a Kubuntu user is unable to without installing the GTK frontend and the large number of dependencies it requires. |
| Line 22: | Line 24: |
| Converting GTK parts of existing code into KDE. | Converting GTK parts of the existing code in the ''hwdb-client'' package into KDE. The questions and hardware data collection will be shared between the two frontends. |
| Line 26: | Line 28: |
| hwdb-gui and hwdb-send should be ported from GTK to KDE. | Two Python files, hwdb-gui and hwdb-send, need to be ported from GTK to KDE. |
| Line 32: | Line 34: |
| Finishing this code needs writing the GUI and related functionality for each question. The questions are available in a frontend-independent XML file however the audio question will need to use arts instead of esd. | HWDB consists of a number of questions for the user ("does sound work", "does your keyboard work", etc.). Finishing this code needs writing the GUI and related functionality for each question. Most of the questions fall into a common case of "Yes, No, Partially" so most questions do not need specific code. The questions are available in a frontend-independent XML file. The audio question will need to use arts instead of esd to be compatible with KDE. |
| Line 34: | Line 36: |
| Changes to hwdb-client in edgy should also be taken into account once they happen, these are likely to be adding a Back button to the wizard and a Delete option to reset | Changes planned for hwdb-client in edgy should be included in the KDE frontend: these will be adding a Back button to the wizard and an option on the screen shown when the wizard has already been run to rerun the client (intended for the case of a user who has installed new hardware). Further questions may be added as specified at ExtendHwdb; these will be easy to incorporate as they are only questions and do not include any further new functionality. |
| Line 38: | Line 40: |
| === User Interface === General question layout: http://kubuntu.org/~jriddell/hwdb2.png Add a "re-run wizard" button to the screen shown when the wizard has already been run: http://kubuntu.org/~jriddell/hwdb1.png |
|
| Line 40: | Line 52: |
| KDE lacks a good canvas class along the lines of gnome-canvas as used in the GTK frontend so will likely end up with less graphics. If Python bindings for Qt 4 are working we can write it in Qt 4 which will allow for the same graphics as used in the GTK frontend. | KDE lacks a good canvas class along the lines of gnome-canvas as used in the GTK frontend so will likely end up with less graphics. If Python bindings for Qt 4 are packaged and working we can write it in Qt 4 which will allow for the same graphics as used in the GTK frontend. Further questions and functionality may be added as part of https://launchpad.net/distros/ubuntu/+spec/extend-hw-db/ |
Launchpad Entry: https://launchpad.net/distros/ubuntu/+spec/kubuntu-hwdb
Created: 6/6/06 by JonathanRiddell
Contributors: JonathanRiddell
Packages affected: hwdb-client
Summary
Allow Kubuntu to have a HWDB frontend.
Rationale
HWDB is a handy tool for taking information on users hardware; we should have a client for it in Kubuntu. The current client is GTK only and therefore unsuitable for default install in Kubuntu.
Use cases
Oliver wants to report a hardware support bug in Kubuntu but wants to include a HWDB reference to have the maximum information available to those reading the bug.
Daniel wants to help Kubuntu and Ubuntu build up information on which hardware is supported but as a Kubuntu user is unable to without installing the GTK frontend and the large number of dependencies it requires.
Scope
Converting GTK parts of the existing code in the hwdb-client package into KDE. The questions and hardware data collection will be shared between the two frontends.
Design
Two Python files, hwdb-gui and hwdb-send, need to be ported from GTK to KDE.
Implementation
Jonathan half started this a while ago, code at http://kubuntu.org/~jriddell/hwdb/
HWDB consists of a number of questions for the user ("does sound work", "does your keyboard work", etc.). Finishing this code needs writing the GUI and related functionality for each question. Most of the questions fall into a common case of "Yes, No, Partially" so most questions do not need specific code. The questions are available in a frontend-independent XML file. The audio question will need to use arts instead of esd to be compatible with KDE.
Changes planned for hwdb-client in edgy should be included in the KDE frontend: these will be adding a Back button to the wizard and an option on the screen shown when the wizard has already been run to rerun the client (intended for the case of a user who has installed new hardware). Further questions may be added as specified at ExtendHwdb; these will be easy to incorporate as they are only questions and do not include any further new functionality.
The hwdb package will be split into three packages hwdb-client-common, hwdb-client-gnome and hwdb-client-kde which provide the common file and those for each frontend.
User Interface
General question layout:
http://kubuntu.org/~jriddell/hwdb2.png
Add a "re-run wizard" button to the screen shown when the wizard has already been run:
http://kubuntu.org/~jriddell/hwdb1.png
Outstanding issues
KDE lacks a good canvas class along the lines of gnome-canvas as used in the GTK frontend so will likely end up with less graphics. If Python bindings for Qt 4 are packaged and working we can write it in Qt 4 which will allow for the same graphics as used in the GTK frontend.
Further questions and functionality may be added as part of https://launchpad.net/distros/ubuntu/+spec/extend-hw-db/
KubuntuHWDB (last edited 2008-08-06 16:31:36 by localhost)