CSC220 Homework 3 2010

From dftwiki3
Jump to: navigation, search

--D. Thiebaut 13:47, 30 September 2010 (UTC)



By popular demand, the due date for this semester is moved to Thursday night. This assignment is due Thursday Oct. 7th at 11:59 p.m. + 1 minute.



Problem #1

  • The purpose of this assignmennt is for you to write an html form and a php program processing the form.
  • the images below show the form, along with its input widgets:


Csc220FormHomework3a.png



and the same form, without the option box opened:



Csc220FormHomework3b.png


  • The form illustrated here has very little ornementation. Feel free to modify it, and reformat it differently, as long as we can still use it get the following information from a participant:
    • her name
    • her email
    • how she heard about this experiment/project
    • whether she will be using her own phone
    • which days of the week she will be participating (can be 0, several, or all)
    • her status at Smith (First year, sophomore, junior, senior, ada, faculty, or other) (for right now, feel free to indicate others)
    • a check box indicating that she has read some legal document and is willing to participate.
  • Your form should also sport a reset button to reset all the fields, and a submit button to submit it.
  • The following form is a good example of the use of several useful widgets. There are also some nice tutorials on the Web on using php to process form, including this one.
  • Your form should be called hw3form.htm
  • It should have an associated php processing program called hw3process.php, which will take the contents of the form and display it in a human readable way (for example, as you did in the second part of Lab 4). Here again, feel free to format the output nicely. Using the echoform.php program to output the information is a great debugging tool, but is not acceptable here as hw3process.php.
  • Submit both files as follows:
  submit hw3 hw3form.htm
  submit hw3 hw3process.php
  • (Added 10/04/10). In terms of robustness, we haven't seen much, and at some point we'll have to figure out how to display an error message for the user and redisplay the form. For this assignment, we will not worry about robustness.