![CWU [Access key = 0 ]](http://www.cwu.edu/~gellenbe/images/logo.gif){kind=logo}
Central Washington University Agenda main content
Agenda for Day 6
- Announcements
- CS and University Announcements
- Wednesday, Friday room change beginning Friday - Hebeler 116
- Assignments
- Three copies of Draft Project Proposal due Friday
- Program 1 begins after class today, due in one week
- Readings
- For today's lab: User Input through Dialog Boxes
- For next lecture/discussion: begin Chapter 2 of textbook
- Hands-on Lab 3 learning objectives
After completion of today's lab, you should be able to- Explain when to use Message Boxes for notifications and user input
- Use a Message Box in a Windows Application to display information to the user
- Use a Message Box in a Windows Application and get a response from the user
- Create a simple custom dialog box
- Explain the differences between modal and modeless dialog boxes
- Create a data entry dialog box for user input
- References
- MSDN's Official Guidelines for User Interface Developers and Designers
- From the guidelines, a message box is a secondary window that displays a message about a particular situation or condition. Messages are an important part of the interface for any software product. Messages that are too generic or poorly written frustrate users, increase support costs, and ultimately reflect poorly on the quality of the product.
- SSW Rules to Better Interfaces
- SSW is a Sydney-based consulting company specializing in .NET solutions for progressive businesses since 1990. They have posted a number of lists of rules related to .NET technologies. Included in their rules is Do you know how to make message boxes user friendly?
- FAST Consulting The GUI Design Handbook
- An online version of their textbook, originally published by McGraw-Hill in 1998. Alphabetical by widget, the handbook provides guidelines for message boxes