Corus M3 Sprint 1 Planning

The following items are on-deck for the next sprint, but is likely to overflow well into following sprints.

Clean up the current UI implementation to look like a professional Qt application, such as:
- modify the dialog title bar and border to be less obtrusive
- fix layout errors in dialogs
- have a better color scheme
- remove the 1px "hole" around the menu panel
- fully separate UI design/layout with logic/model/handling
- ensure UI's use correct Qt design
  - ensure UI's correctly change layout when resized
  - implement tool tips, right-click menus, keyboard shortcuts
Ensure all components are using the new Qt integration
- port drop-down console to Qt
- implement UI-on-texture using UiModule
Implement Viewer-appropriate Interaction Designs
- 1. http://wiki.realxtend.org/index.php/ReX-NG_Design_Document (Section 6)
  2. http://wiki.realxtend.org/index.php/User_Interaction_Working_Group
  3. Playsign designer's recommendations
- Implement "In-world" and "Ether-world" dual spaces (in-world is a 3D space, ether-world is where you are when you're not in-world, ie a lobby, login screen, teleport screen, cut-scene screen, etc.)
- Implement "notification area", for example: http://www.markshuttleworth.com/archives/253
- Implement "docking", something like what is possible in visual studio or windows 7: dragging a dialogue near an edge allows you to "attach" it there
- Implement context-sensitive menus for in-world object (such as "chat with joe" button over an avatar, or "touch chair" button over a chair)