Re: widgets plan proposal
Andrew Kohlsmith <[email protected]> Wed, 2 Apr 2003 08:14:10 -0500
| Newsgroups | gmane.comp.java.xwt.general |
|---|---|
| Organization | Benshaw Canada |
| Message-ID | <[email protected]> |
> This means whatever was focused (say, a text field) looses focus, > passes it to the unfocusable (a button in a toolbar), and then gets it > back. This unfocus/focus stage could cause a few problems with certain > widgets. Say you had a selection in the text, and you hit a copy > button. Is the text still selected when the copy action runs? Good point. Charlie says that this is already done by setting the button as focusable=false for a temporary nonfocusable, or setting subfocusable if it's never to be focusable. This brings up another point -- IMO keyboard focus (tab/shift-tab, some alt-key modifiers for everything, whatever the theme uses) should not be an option. Toolbar buttons _should_ be focusable. so the fark what if you have to click back on your main app, I am pushing for accessibility here. hotkeys (optional alt-key or ctrl-key sequences) are just that -- optional. having every widget hittable from keyboard is IMO, not an option. > Wouldn't it be better if a clickable could be clicked without the focus > ever moving? The copy simply happens, the the text field stays where it > was. Yes and no. :-) > I suppose the goal should be to come up with a model that specifically > details how it handles each and every word we use (selected, focused, > clicked, dragged, dropped, focusable, editable, etc), and then a > document for each theme that details how we translate our language into > the actions of the specific theme. Agreed. It seems like we're doing it a bit backward now... get everything standardized and then write the documentation that the widgets adhere to. It's typical in the marketplace but it is backward. :-) > Sounds like a study project. You'd have to get a full design for each > theme your implementing, and then map our design to it. This is the > point I got to in the widget library when my patches started dropping > off. I just didn't want to keep coding knowing that I should be > creating this documentation, and my code was starting to go in circles. I could see that. It's tiring to continue working only to see that the more you work, the more work you're creating for yourself. Regards, Andrew _______________________________________________ http://lists.xwt.org/listinfo/dev