Opened 13 years ago
Closed 10 years ago
#1669 closed enhancement (obsolete)
Accessibility - keyboard
Reported by: | earias | Owned by: | tomeu |
---|---|---|---|
Priority: | Unspecified by Maintainer | Milestone: | Unspecified |
Component: | Sugar | Version: | Unspecified |
Severity: | Unspecified | Keywords: | r! |
Cc: | earias, aa | Distribution/OS: | Unspecified |
Bug Status: | Unconfirmed |
Description
Added to control panel new section: "Accesibilidad". This item allow configurate Mouse keys, Sticky Keys and Bounce Keys.
http://wiki.sugarlabs.org/go/Features/Accessibility_controlpanel
Attachments (3)
Change History (10)
Changed 13 years ago by earias
Changed 13 years ago by earias
comment:1 follow-up: ↓ 2 Changed 13 years ago by aa
- Cc earias aa added
- Keywords r! added
- Type changed from defect to enhancement
Changed 13 years ago by earias
comment:2 in reply to: ↑ 1 Changed 13 years ago by tomeu
Replying to aa:
- We can't include binaries in Sugar. If your feature has external dependencies, make sure it is packaged in the major distros and it will be added as a dependency by packagers. Please document this carefully, and bear in mind that pulling extra dependencies consumes storage capacity which is scarce in most contexts.
...
It would be nice to find out what keys GNOME uses for these things and use them. That way if the user switches from GNOME to Sugar or vice versa, her changes will remain in effect.
gnome-settings-daemon listens for changes in gconf and configures X appropriately:
I think we should do the same because 'ax' is not widely available in distros.
comment:3 follow-ups: ↓ 4 ↓ 5 Changed 13 years ago by earias
sayamindu work's:
comment:4 in reply to: ↑ 3 Changed 13 years ago by tomeu
Replying to earias:
sayamindu work's:
Hi Esteban, could you explain us a little what's this and what's the story behind?
As far as I can see that package is not part of fedora nor other distros.
comment:5 in reply to: ↑ 3 ; follow-up: ↓ 6 Changed 13 years ago by earias
Replying to earias:
sayamindu creates rpm to fedora
comment:6 in reply to: ↑ 5 Changed 13 years ago by tomeu
comment:7 Changed 10 years ago by dnarvaez
- Resolution set to obsolete
- Status changed from new to closed
First of all, thanks for working on this. Work in accessibility features is always welcome, and we all know feedback from deployments is crucial for Sugar.
Sorry it's been sitting here for so long. If you want to get the maintainer's attention you should add the keyword "r?" to the ticket (see http://wiki.sugarlabs.org/go/Development_Team/Code_Review). Or even better, submit it to sugar-devel for maximum exposure ;).
There are a few issues with this change:
There seems to be a mix of this and mixedCase style in your patch.
Also, there are several mistakes that pylint would catch. Check the guidelines page for info about pylint. Below are some issues that pylint wont warn you about.
It would be nice to find out what keys GNOME uses for these things and use them. That way if the user switches from GNOME to Sugar or vice versa, her changes will remain in effect.
It may be clearer to build the list instead of having all those variables. Like this:
Unless this work was paid by OLPC, this is your (employer's) copyright.
This string should be gettexted: _('Accesibilidad'). Also sugar's default language should be English. Arguably, people translating Sugar to other languages are more likely to know English than Spanish.
You shouldn't need this if your code is in English.
Please do not use whitespace inside labels to align text correctly. Use gtk.Alignments for that. Think about other languages, even right-to-left languages suchs as Arabic or Hebrew; if you build your UI using alignments, GTK can be smart and invert them when the locale indicates a RTL language.
Thanks again for the patch. Let me know if I can help in any way.