In PalmBible+, all user-configurable actions are rolled into the keyboard
configuration code, together with some fake key codes. This means, for
instance, that actions started by on-screen icons are trivially easy to
make configurable, and that typically when one wants to make some input
method user configurable, it's just a matter of adding a fake key code,
setting a default in the keyboard code (which is a derivative of Plucker's
keyboard code), and adding lines to the rcp and language files. Even if
we want to maintain the nice and friendly jogdial, fiveway, hardkey,
screen tap, etc., configuration menus, we could still store the prefs
consistently in the keyboard database. Don't know if it would save any
code size, but would make for some consistency. I've made this suggestion
before with respect to hardkeys, but now I've realized that various other
UI elements can be handled in the same way. For upgrading purposes, we
could put sensible defaults in the keyboard database, and then replace the
entries in the prefs with "unused" entries". Anybody who customized the
actions can easily do so again--there is no need to write upgrade code, I
think.
Alex
--
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
