CommonATConfig
|
Size: 2414
Comment: screenshot link
|
Size: 2415
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 15: | Line 15: |
| Accessibility can be coplicated because we are dealing with a diverse user group with varied needs. The configurations should ideally be accessible in a number of ways to give the users several options for setting them (because some options may be blocked by links in the chain not working properly). A flexible configuration system would have one back-end for reading and writing config files, but be able to support multiple user interfaces including GTK, Qt, command line and browser-based. | Accessibility can be complicated because we are dealing with a diverse user group with varied needs. The configurations should ideally be accessible in a number of ways to give the users several options for setting them (because some options may be blocked by links in the chain not working properly). A flexible configuration system would have one back-end for reading and writing config files, but be able to support multiple user interfaces including GTK, Qt, command line and browser-based. |
Launchpad Entry: https://launchpad.net/distros/ubuntu/+spec/foo
Created: 2006-04-24 by HenrikOmma
Contributors: HenrikOmma
Packages affected:
Status: BRAINDUMP
Summary
Create a common config panel for all the assistive technology features.
Rationale
The assistive technology (AT) settings in gnome are currently spread out over several locations, making the features difficult to find. With the creation of a new Orca and Speech Dispatcher GUIs, we have an opportunity to restructure the settings GUI as well. The new settings system should be plug-able so that the settings dialogs from Orca, Speech Dispatcher, the on-screen keyboard and the current keyboard/mouse settings fit naturally into it. If we don't take this opportunity to consolidate, we will simply get several more independent configuration panels, making the situation worse than it is today.
Accessibility can be complicated because we are dealing with a diverse user group with varied needs. The configurations should ideally be accessible in a number of ways to give the users several options for setting them (because some options may be blocked by links in the chain not working properly). A flexible configuration system would have one back-end for reading and writing config files, but be able to support multiple user interfaces including GTK, Qt, command line and browser-based.
Use cases
Scope
Design
The Orca team has released a basic GTK-based GUI with version 0.2.3 that can be integrated into the common utility (see [https://wiki.ubuntu.com/Accessibility/Specs/CommonATConfig?action=AttachFile&do=get&target=Orca-glade.png screenshot]). It is a single window where the different settings are grouped via tabs. The settings for other AT features could be organised in a similar way, with each category having its own window with tabs. A web-based mock-up of thislayout can be seen [http://people.ubuntu.com/~henrik/at-conf/main.html here]. Some initial dicussions can be found [https://lists.ubuntu.com/archives/ubuntu-accessibility/2006-April/000323.html here] and [https://lists.ubuntu.com/archives/ubuntu-accessibility/2006-April/000307.html here].
Implementation
Code
Data preservation and migration
Outstanding issues
BoF agenda and discussion
Accessibility/Specs/CommonATConfig (last edited 2008-08-06 16:39:48 by localhost)