ITEC 325 2013spring ibarland

home—lects—exams—hws
D2L—breeze (snow day)

hw04
sanitized html
and automated source-listings

Scenario

You are working for Lizard Entertainment, makers of the popular adventure game, .World of Wowcraft (“.W.o.W.”). In .W.o.W., players choose a type of character: either warrior, mage, priest, or rogue. Over the course of the game, their characters can learn various skills, depending on type: For example, the diplomacy skill (which is learnable only by rogues and priests), or the acrobatics skill (which is learnable only by rogues and warriors), etc.. Each skill is be tied to one of six built-in character traits: Strength, Intelligence, Wisdom, Dexterity, Constitution, and Charisma. Finally, each skill has a minimum-level (between 30 and 100 inclusive).

Your boss decides that a key feature of the game is that people can add their own skills to the game. Your job is to build a web-page that lets people enter new skills for the game to use. People will enter the name of the skill, a detailed description, which character-types can use it, what trait it's tied to, and their own name (to get the glory). When they submit their form, they will see a response page summarizing the information they entered.

An example of filling out the form	The result of the processing the form

Your Task

For this homework, you will take your hw03 solution (copied to a directory hw04), and modify it as follows:

1. Modify the form so that it resembles the screenshots above. In particular:
   • Include the additional input elements (skill-description, min-level, the drop-down of attributes).
   • Include the file's actual modification time using filemtime as mentioned in the notes.
   • Remove the bits of hw02 formi,table of abilities, remove the paragraph “this web page is a prototype for…” bits about “other sites” and “We'll let users add…”. (Those were just there to help motivate the php functions which you are using more of this homework.)

2. Have your form actually submit to skill-handle.php, and generate a response similar to the one pictured above.

   When printing values taken from the form, sanitize the HTML. A user should be able to enter (say) a description which includes characters like < and ' and newlines, and the resulting summary should

   Note that the checkboxes in skill-form.php should all have the same name attribute (and it should end in “[]”), so that you can retrieve it as an array in your form.

3. Put your css into a separate file.

4. Your file hw04/index.php should call show all the files in your solution, as in the hw03-soln/.

   The page does need to contain (near the top) your name, a link to your skill-form, a link to this homework-assignment, and a “table of contents” — a list of links to later in the page, with the detailed information for each file.

   The source should be shown only if the current time is between 2013-Mar-06 23:59 and 2013-May-31 23:59; otherwise show a message along of the lines of “source code only available between 2013-Mar-06 23:59 and 2013-May-31 23:59.”

   Use the function show_file_info below, along with scandir and your function hyperlink. For full credit, use array_map at least once, where appropriate.

5. Required functions (w/ test cases, except as noted):

   • Optional: A testAsHTMl, which is like test except that it is more lenient about considering two strings as “equal”: instead of comparing them directly, it normalizes each of them, and compares the result. Here, “normalizing” can mean triming any leading/trailing whitsepace, collapsing all multiple-whitespace with a single space character, and turning all (say) double-quotes into¹ single-quotes.

     You can replace characters in a string by calling preg_replace. We'll talk more about regular expressions in a week or two, but one example would be: preg_replace( '/\p{Z}+/u', ' ', "kev in space \n\ny \t \n ") === "kev in space y ": this means replace any occurrences of one-or-more (“+”) whitespace characters “\p{Z}”² with the replacement ' ').

   • A function dropdown which takes in an array of strings (and any other necessary arguments), and returns a string of HTML for a drop-down menu, using the provided strings as choices in the menu, but their keys as the each option's value attribute.

   • A function ul which takes in an array of strings (and any other necessary arguments), and returns (the html for) an unordered list of those strings.

   • A function show_source_between, which takes in a filename, start-time and end-time, and it prints (not returns) the file's source if it's currently between the selected times, or else a message stating when the solutions were/will-be available. See show_source.

     No test cases required — this function prints, and does not return anything.

   • A function show_file_info, which takes in an a filename, start-time, and end-time, and it prints (not returns) the filename (fairly emphasized, and also as a link to the file itself), the last-modified date, and the result of calling show_source_between appropriately. You may include further information or HTML formatting/styling, as you like, to make the output render more effectively.

     No test cases required — this function prints, and does not return anything.

   • You of course are welcome to have further utility/helper functions as you like. (In particular, I can think of one more task that is part of this assignment, and is also a stand-alone task that will be re-usable in future assignments or in other contexts.)

As usual, I will visit the URL https://php.radford.edu/~yourUserName/itec325/hw04/index.php to grade your work. If that URL is not accessible, you will get a 0 for that portion of the grading!

Other requirements

• Each file start should start with with a PHP or HTML comment with your name, class, etc. (after a doctype declaration and perhaps <html>).
• Use meaningful variable names, function names, and good comments as needed.
• Write functions (both php and javascript) as appropriate, to avoid repeated work.
  I recommend writing functions that return strings rather than print (as convenient³), and including one or two test-cases as examples. Writing the test-case first often clarifies exactly what your code needs to return.
• Use standard XHTML tags and make sure any javascript does not use browser-specific constructs.
• All code/html should be well formatted with appropriate white space and indentation so it is easy to read.
• Strive to minimize lines that wrap.
• If you have any questions, use the discussion board.
• Do not modify your final submission after the due-date; if you want to make changes, copy all your files to a new directory and work on those. (Linux: use cp -pr to preserve timestamps and copy directories recursively.)

• Please run/check your program/html incrementally — don't write huge amounts of the assignment w/o even running it.

home—lects—exams—hws
D2L—breeze (snow day)

©2012, Ian Barland, Radford University Last modified 2013.Mar.26 (Tue)

Please mail any suggestions (incl. typos, broken links) to ibarlandradford.edu