Form Generation

Products are stored in a file called catalog.dat. A line of the file has the following format:

{product-code}:{product-name}:{commerical-price}:{noncommercial-price}:{product-description}

For example,

C05:Net Chat:50:20:New version; can handle any number of visitors!

Product codes consist of three characters and are unique. You will first need to read and store this data in some reasonable data structures (perhaps separate hashes for product names, commercial prices, noncommercial prices, and descriptions, each using product code as keys, or separate arrays for each data field).

The <TITLE> of the order page should be Order Form for New Customers. The page itself should consist of the following:

• A <H1> heading that reads Order Form for New Customers.
• A horizontal rule (<HR>).
• Text that indicates how the user should select scripts, that the form must be completely filled out to process an order, and that a username and password must also be provided.
• A horizontal rule (<HR>).
• A <H2> heading that reads
  Please select the scripts you wish to purchase and the number of licenses:. This is followed by a series of product listings, each separated by a <P>. The listings do not have to be displayed in any particular order.
  • Each listing should start with a checkbox. Use the product code as the -NAME of the checkbox. The box should not be checked at the beginning.
  • The label Item: should appear in bold on the same line as the checkbox. The label should be followed by the product name.
  • The label Commercial price: should appear next in bold on the same line. It should be followed by the commercial price of the product (the price should include a dollar sign).
  • The label Noncommercial price: should appear next in bold on the same line, followed by the noncommercial price of the product (the price should include a dollar sign).
  • The label Quantity: should appear in bold on the same line as the checkbox, followed by a textfield of width 3 with an default value of 1. I would suggest that each textfield be given a name that can be constructed from the corresponding product code. Since product codes are of fixed length, you can simply prepend a 'Q' to the product code, for example.
  • On the next line (emit a <BR>), the product description should appear in italics.

• A horizontal rule (<HR>).
• A <H2> heading that reads Contact Information:.
• An appropriate label and a textfield that allows the user to enter a name (set the width of the field to 40).
• An appropriate label and a textfield that allows the user to enter a street address (set the width of the field to 40).
• An appropriate label and a textfield that allows the user to enter a city (set the width of the field to 25). On the same line, a label and a popup menu with postal abbreviations for all 50 states followed by another label and a textfield that allows the user to enter a zip code (set the width of the field to 9 and make this the maximum number of characters that can be entered).
• A bold label Intended use for script: followed by a radio group list consisting of two options -- Commercial and Noncommercial. Both options should be on the same line. Neither box should be checked at the beginning.
• A horizontal rule (<HR>).
• Text indicating that the user should now choose a username and password that will be used to access the scripts once payment is received. Point out that they should enter the password twice.
• An appropriate label and a textfield that allows the user to enter a username.
• An appropriate label and a password field that allows the user to enter a password.
• An appropriate label and a password field that allows the user to re-enter the password.
• A horizontal rule (<HR>).
• A submit button titled Submit Order and a reset button titled Reset Order.