For example, typing “i” takes you to your Inbox. ZimbraWebClient/WebRoot/js/config/keys/ZmKeys.propertiesĪ good number of the shortcuts of the latter type are mnemonic. For example, there are different sets of shortcuts for composing a message, for viewing your inbox, and for viewing your calendar. Application shortcuts that are independent of focus, which depend on what the user is currently doing. They are in:Ījax/WebRoot/js/config/keys/AjxKeys.propertiesĢ. In general, these do not use letter keys. The shortcuts that are in play are for the widget that currently has focus. Shortcuts that apply directly to UI components (“widgets”) such as buttons and menus. Of course, we use more natural names for the shortcut maps and actions, and translate those when we convert them from properties to Javascript.Īs before, shortcuts are divided into two categories:ġ. Plus, we can add documentation into the properties files which will appear in the web client. Now that the shortcuts are in properties files, they can be maintained by the same folks who maintain the strings files. Also, because different types of computers (eg Macs vs Windows machines) have different keyboard behavior, we need an easy way to override shortcuts by platform. That would be a pain to do via more Javascript code, but properties files (with their associated resource bundles) provide a built-in mechanism for localization. And – here’s the second big problem with the old approach – they should be easy to localize. But shortcuts are more along the lines of strings, which are kept in properties files – they are an atomic component of the UI that should be easy to change. Maintenance of shortcuts in this manner is clearly designed to be done by programmers. for these to work, controller must implement getTabView() Though it’s reasonably clear in this case, it’s not so obvious elsewhere: Also, it’s not obvious what everything means. It is easy to break the code such that the file will not parse. Whoever changes them must have at least a rudimentary understanding of Javascript, otherwise bugs can be introduced. First of all, shortcuts change often, and burying them in code makes them cumbersome and risky to change. There are several problems with doing it that way. For example, the map of shortcuts available when composing a message looked like this: Third, there is now a page within Preferences that describes all available shortcuts.īefore this release, keyboard shortcuts were defined in hashes in Javascript code. Second, you can create numeric aliases for folders, tags, and saved searches, which you can then use in shortcuts. ZCS 4.5 contains several significant enhancements to keyboard navigation: First, shortcuts are now defined in properties files.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |