Registered Member
|
In KDE 4.8 and 4.9 we'll see new features, but almost nobody focuses on boring things. Let's do a fundraiser, to pay some dev who's willing to:
- Identify and analyze how dialog boxes interact with the keyboard. - Fix all the keyboard interaction errors. - Solve the keyboard issues with the Plasma Desktop. We need more and better keyboard interaction. |
Registered Member
|
I second this and will add that keyboard navigation is important not because of the power users but because of accessibility with blind or vision impaired users. Keyboard shortcuts go a long way for the blind and being able to tab through every interface make apps usable by people with vision disabilities. I think this is important, and while helping out people with disabilities you also have a side effect of making the power users happy. Also I have been wanting the ability to key bind my activities.
|
Registered Member
|
I agree, strongly, that keyboard navigation is critical for providing a18n support on the KDE Desktop. And so, in support of our UI needs, I have added it to the Agenda for the upcoming Plasma/Workspace "Sprint", which is focused on adjusting KDE's Plamsa and Workspace manifesto and strategy for the future.
In other words: Several of KDE's Leads are taking some time to re-do "The Vision Thing", having enjoyed (??) about 4 years of experience to learn from the existing Goals and Guidelines. And now, this is on the agenda.
KDE and Qt coding newby. Production system = Fedora 17, KDE 4.8.3
|
Registered users: Bing [Bot], Google [Bot], kesang, Sogou [Bot], Yahoo [Bot]