AH> I also rather angrily made the point to another project that it is just AH> insane to use Page Up and Page Down by default for something other than AH> the blindingly obvious moving up and down the page (by all means use the AH> shift and ctrl modifiers to make it do something else). Note I said 'by AH> default' because if you follow my advice users can still rebind the keys AH> to a menu item but if you bind PageUp PageDn to menu items there is no AH> easy way for me to make PageUp do exactly what it is supposed to do!
I agree. raising and lowering objects could be bind to ctrl+pgup/pgdn and sending to back/front to ctrl+shift+pgup/pgdn. i think that pgup and pgdn shouldn't be used at all, at least for now. when svg specification will allow multiple paged documents (i hope it will happen soon :-) and inkscape will support it pgup and pgdn may be used to switch pages (and this will do exactly what the keys mean :-)
AH> I also wouldn't recommend extreme caution before using alt as an AH> accelorator and to use Ctrl and or Shift first. Some platforms use Alt as AH> the main modifier/command key instead of Control (BeOS, and one of the AH> really old crappy versions of Netscape I was using somewhere around the AH> University) and many platforms use Alt to access menus (such as Alt+F to AH> access the _File menu) and you dont want shortcuts to collide or to have AH> a workflows that users might accidentally trip over.) in Poland we use keyboard layout in which special characters are made with right alt (alt+o, alt+e, alt+l and others), so i think alt as a modifier is not a good idea because some shortcuts may not work, or it might be problems with text input (such problems occur in some programs in ms win)
best regards yemu