User Interface of the Sales Application
The sample application we are creating is a forms-based application that will be used to record orders. This application is for a person who sells toys to stores.
Note
This sample application will be used as a basis for our code discussions throughout the book.
These are the activities we want the salesperson to be able to accomplish in the application:
Modify, delete, or create a new customer
Create a new order for a customer
Delete an order
Delete or modify items in an order
Beam a company to another device
The Sales Application Customer List
The user starts the application and picks a customer from a list Figure 3.5.
The customer list
This is the startup form of the application. It is a list of all the customers that our salesperson normally sells toys to during that selling period. The user can tell which customers already have orders because those without orders are in bold.
We admit that bolding an item to indicate status is a subtle, if not obscure, design element. Its presence is reasonable when you remember the audience of this application. The same user will use it day in and day out for taking orders. The bolding of an item in a constantly used application may be warranted, while it may not be in a more general purpose application. In any case, a user who doesn’t know what the bold is for is not hurt—it’s just a shortcut for the experienced user.
When a name is selected from the customer list (see Figure 3.5), the individual Customer form ...
Get Palm Programming: The Developer's Guide now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.