Re: widgets plan proposal
David Crawshaw <[email protected]> Thu, 3 Apr 2003 00:06:55 +1000
| Newsgroups | gmane.comp.java.xwt.general |
|---|---|
| Message-ID | <[email protected]> |
On Wednesday, April 2, 2003, at 11:55 PM, Andrew Kohlsmith wrote: >> <button focusable="false"/> will be a non-focusable button > > That's great, but how do I get to it from a keyboard? Nothing pisses > me off > more than apps which have widgets you can't hit from a keyboard. (I'm > talking any app, not just XWT apps.) This is a problem. While focusable buttons are a plus from a key navigation point of view, they break theme <-> native theme compatibility. In the aqua theme, there are hundreds of buttons you can't hit with the keyboard. Theory being that they also exist in the drop menu at the top of the screen, so why have two shortcuts for the one function. So theoretically, if a app developer designs correctly it doesn't matter. Most applications are proof that these designers do not design correctly. Personally, I'm for having buttons that you can't hit with the keyboard for maximum compatibility. Perhaps later we can have an 'accessibility mode' widget library that a person can choose to use from inside the builtin xwar interface, with extra features like this. d _______________________________________________ http://lists.xwt.org/listinfo/dev