Bill
In a data entry application that I worked on recently, I exposed the data entry tasks via key strokes (and context menus).
As far as WPF is concerned, you will definitely want to expose all data entry actions via routed commands. Data entry folks rarely want to lift their fingers off of the keyboard because it slows them down. With WPF, as long as your functionality is exposed via commands, you can easily wire it to key strokes using key bindings. The same functionality can then easily be connected to toolbar buttons, menu items, context menu items, or whatever.
It was a data visualization application also, so the data was presented in a way that represented its organization. All of the editing was "in place". This is easily achieved in WPF using templating and introducing the concept that a control can have both an edit mode and a view mode. A trigger can be used in the control style to swap between the edit mode template and the view mode template.
It's a big topic and I'm sure you'd get lots of other suggestions if you narrowed down the breadth of your question to specific application areas.
Would you be willing to show some screenshots? After 20 years programming, menus and toolbars are so engrained in my mind for business apps that I am having trouble picturing a business app without. But I would like to use the full potential of WPF for livening up my app and thinking out of the box.
