Key to Action mapping

At the beggining it was simple... all PalmOS devices had the same button layout. Then came the jog-dial from Sony, the direction pad from PalmOS and then the Zodiac extra buttons. Keys are good things... they provide extra uses for the device from starting more applications with a single tap to playing games with more functionality, different key layout for different devices are going to change even more. Screens Environment solves this from the core. Instead of applications checking if 'hardbutton1' or 'hardbutton2' was pressed, they check if 'left' or 'right' event was recieved. So instead of applications checking for keys, they check for actions. You can even receive multiple actions at once like fire+left or jump+fire. While applications can still deal with buttons if they need to, it's not recommended. By having Screens Environment do this for you, it allows every application written for Screens Environment to able to be hardware-button independent. In the system, each action is attached to a key however you can specify a 'global' profile or even for each application (like games) in one single window without having to move between each application properties and modifying the key mapping. These will allow hardware designers to able to design the device for thier users and not for the operating system.