Nice. I think I may have mentioned this idea a while back, but it would be cool to combine this with the HTML accesskey attribute. This attribute binds a character on the keyboard to a link (it works on forms tags too, though irrelevant here) so when the key is pressed, it follows that link.
This would come in very handy for those of us creating content with Plucker in mind. -- Dave Maddock <[EMAIL PROTECTED]> On Sat, 2003-07-05 at 09:54, Alexander R. Pruss wrote: > I added fully customizable keyboard / single character graffiti support in > CVS. So you can do such things as bind "m" to pop up the menu, "down" to > go to the next link (this one is a default setting), etc. The keyboard > map is stored in a PlkrKeyboardMap database, so one can beam it between > units, distribute custom maps, etc. > > Some notes: > > 1. The UI is rather rudimentary. If someone wants to prettify it, please > go ahead. (Adding help would help, too.) > > 2. Right now the handling of up/down keys is messy. First Plucker checks > if custom up/down keys are enabled. If not, it pages through the > text. If so, it uses the SELECT action bound to them. This could be > simplified by always enabling the SELECT action and just binding it by > default to FULL_PAGE_UP/DOWN. Next, all unhandled keys are checked > against my the keyboard map, and the right SELECT action is chosen (but > the page up / page down keys are not included in my keyboard customizer to > remove duplication). All of these three things could be rolled into my > keyboard customizer, removing the Pref options for selectable page up / > page down keys, as well as for the other hard keys while one is at > it. But I don't like removing Pref options as it creates backwards > incompatibilities. One could even simplify the code by getting rid of the > hard key and arrow key pref dialog entirely, except that it is a > friendlier dialog than my keyboard customizer. > > 3. Some keys will not be compatible with gestures being enabled. Right > now a warning is shown. It would be smarter to have a dialog box and ask > the user when such keys are entered. > > 4. I added a menu trigger SELECT control. I re-ordered the last couple > of SELECT controls, too. This means that if you had something bound to my > TOGGLE_TOOLBAR or TOGGLE_FULLSCREEN controls, you will need to fix these > bindings. Since the latter two controls have only been there a couple of > days, I hope this tiny bit of lack of backwards compatibility will not be > a big deal. > > 5. The cleaner could be made to delete PlkrKeyboardMap. But the CLEAR > button in the customization menu might be enough. > > 6. I am rather bad at trying to find short descriptions of things in > English (or in any other language, for that matter). So some labels in my > UI might use some improvement. > > 7. And of course now there is a whole bunch of new stuff to translate for > multilingual versions. > > > Alex > p.s. I've noticed that a bunch of things in util.c don't conform to the > coding guidelines. But who am I to speak? > > -- > Dr. Alexander R. Pruss || e-mail: [EMAIL PROTECTED] > Philosophy Department || online papers and home page: > Georgetown University || www.georgetown.edu/faculty/ap85 > Washington, DC 20057 || > U.S.A. || > ----------------------------------------------------------------------------- > "Philosophiam discimus non ut tantum sciamus, sed ut boni efficiamur." > - Paul of Worczyn (1424) > > _______________________________________________ > plucker-dev mailing list > [EMAIL PROTECTED] > http://lists.rubberchicken.org/mailman/listinfo/plucker-dev _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
