CS Homework 12

Size: px

Start display at page:

Download "CS Homework 12"

Magnus Hancock
5 years ago
Views:

1 Spring CS Homework 12 p. 1 Deadline CS Homework 12 Problem 3 (presenting something operational from Problem 2) is due during lab on Friday, May 4; Problems 1 and 2 due by 11:59 pm on Sunday, May 6, Purpose To practice lightly with Ajax; to complete and present a several-options application using "your" database. How to submit Each time you wish to submit, submit your homework files using ~st10/328submit on nrsprojects, with a homework number of 12. Important notes NOTE: you will be presenting versions of some of these documents to the class during the Week 15 lab session! Be sure to follow the unobtrusive-style client-side JavaScript coding guidelines discussed in class. DO NOT USE ANY JAVASCRIPT LIBRARIES (jquery, Prototype, script.aculo.us, etc.) FOR THESE PROBLEMS -- you are to use "plain" JavaScript for these problems, to get experience with what underlies all of those libraries. NOTE: you are welcome to use require_once and include_once in your PHP documents! BUT when you use them in problems' documents, be sure to also SUBMIT copies of all files that you are requiring/including! DO NOT USE ANY PHP FRAMEWORKS FOR THESE PROBLEMS -- one of this course's purposes is to provide you with practice with "plain" PHP. You are required to use normalize.css for all of your web pages for CS 328. EXCEPT for normalize.css, DO NOT USE ANY CSS FRAMEWORKS or PREDEFINED LIBRARIES FOR THIS HOMEWORK (or for this course unless you get prior, explicit permission). One of this homework's purposes is to provide you with some practice with the basics of "plain" CSS3. You are expected to follow all course coding standards posted on the public course web site; course documents are also expected to validate as "strict"-style HTML5, and valid CSS3. Make sure that you have executed the scripts create-bks.sql and pop-bks.sql, and that the bookstore tables are successfully created and populated.

2 Spring CS Homework 12 p. 2 Problem 1-30 points You have seen, in class, some very simple examples of Ajax in action (and one more-involved example). To provide you with a very little bit of Ajax-related practice, modify the Week 14 Lecture 1 example: ajat-ex1.php // NOTE: this is the earlier example dealing with PLAIN TEXT, *not* XML!!...into a file with a name of your choice that includes prob1 within it such that: its opening comment includes the URL that can be used to RUN this PHP the displayed page contains your name, visibly, somewhere in the body element the displayed page contains some HTML5 element(s) allowing the user to make a choice between at least three different options for some desired content (these can be radio buttons, a drop-down, three or more "plain" buttons -- there are several reasonable possibilities). when the user's choice is made, it uses an instance of the XMLHttpRequest object to request what the user selected from the application tier, and modifies the page to somehow visibly display this chosen content (in some element BESIDES a textarea). this could be a textfield or numberfield (for tiny grabbed content), or a paragraph element, for example (and if something goes wrong? report this where you had hoped to visibly display the chosen content) what can be requested? It can be simple text content in files on the application tier, as in ajat-ex1.txt. IF you would like, it can also be XML or JSON (BUT read Chapter 12's caveats on navigating the XML DOM, if you decide to try XML!) It can even be something queried from a database, if you are feeling daring! BUT that is NOT required for this homework problem. Submit your resulting file *prob1*.php and any other files it needs (e.g., required footer files, for example). Problem 2 (35 points) and Problem 3 (35 points) PROBLEM 2 is COMPLETING your application in custom-session2.php and its associated files that you started in Homework 9 - Problem 6 (and whose overall description is also included below). Submit all of your files for your completed application by 11:59 pm on Sunday, May 6. PROBLEM 3 is presenting something operational for this problem in-lab on Friday, May 4; your Week 15 Lab Exercise grade will also be mostly-determined by this presentation. During this presentation, you are expected to: Complete your presentation within 4 minutes, maximum -- we need to have time for everyone to present!

3 Spring CS Homework 12 p. 3 There will be a grade penalty if you are asked to stop because you have taken more than 4 minutes. Practice your presentation in advance to make sure you can finish in that time frame. Speak clearly, not too quickly, and project (speak loudly toward the audience) -- and, note that it is good to look up at the audience every once in a while. During the Week 14 Lab presentations, there was a tendency of presenters to speak too softly -- try to make a point to speak up. Also: consider the font size of your application's text in the browser you are using for your presentation; can the audience see your screen's text? During the Week 14 Lab presentations, there was a definite issue! If you use zoom to make the font size bigger, does the rest of your application's design still "fit" well in the browser window? Start your demonstration/presentation with a very brief (1-2 sentences) description of your "additional" database's scenario. ("This is an application for Betty Boop's Bakery, which specializes in Boston's best blintzes!") Briefly summarize what your application does. ("This allows customers to request a list of the blintzes-of-the-day for a specified date, or to ask for a list of all of the types of blintzes they have ever ordered, or to order a blintz.) ("This allows the baker on shift to bring up the ingredients for a specified type of blintz, or to see all of today's blintz orders, or to see which blintzes include a specified ingredient.) Demonstrate a successful (if possible) example of each option in your application, explaining what the user does as you demonstrate it. ("The baker on shift selects the desired recipe from this drop down..." (select a recipe), "...and when they click submit..." (click submit), "...a listing of the ingredients for the selected blintz is shown" (and point out the now-displayed ingredients).) Decide on some an aspect of your application that you are particularly pleased with (some aspect of its design, or how you used something in PL/SQL or PHP or HTML5 or CSS or JavaScript, for example; OR it could be something you learned about in last week's demonstrations/presentations, and then used here!) THEN make a point, sometime during your presentation, to explicitly MENTION that, such that I cannot miss it. ("Something I am particularly pleased with is how I used a bind variable for the customer's name in my dynamic SQL query in PHP to avoid SQL injection.") ("I am particularly pleased with the unobtrusive JavaScript used to bring up this especially-clear feedback if the user does X wrong.") ("Using the min attribute for my number fields, mentioned during the sell_book demos, are something I'm particularly pleased with.")

4 Spring CS Homework 12 p. 4 It is also a good idea to practice ENDING a presentation/demonstration -- in general, it should not peter out, with the listeners wondering "Are they done...?" SO -- that's an additional requirement this time: You want a definite conclusion -- a concluding statement is ideal ("This provides a good foundation for future applications for Betty Boop's Bakery!"), but at least make it clear you are done. ("Thank you - that concludes my presentation!", said in a definite, concluding tone) I very much enjoyed your sell_book application demonstrations -- and these, building on your experience from that and using the "additional" database you chose, should be even more interesting. Final implementation's client-side JavaScript For Homework 10, you included a file custom-js-plan.txt that described at least one idea for how you are going to try to use some unobtrusive-style client-side JavaScript in your application. Some unobtrusive-style client-side JavaScript is required to be implemented in the final version of your application. (It can be different that what you planned in custom-js-plan.txt, in case that plan turned out to be more ambitious than you intended, or in case you just come up with a better idea!) specifications previously given in Homework 9 Consider "your" database. For Homework 7, Problem 5, you created custom-call.php that allowed the user to enter information to call a PL/SQL stored function or procedure added to "your" database as part of Homework 2, Problem 5. For Homework 8, Problem 3, you created custom-session1.php that allowed the user to do something useful involving dynamically querying and creating a form control for "your" database, and then letting the user do something useful based on what they choose from that form. Over the final four homeworks, you are going to "pull" these together into an application that gives the user some options for actions they can take using "your" database. Application requirements Now, you will create PHP document custom-session2.php, styled using custom.css. custom-session2.php's second stage, after the login stage, should give the user some means of choosing WHICH action they would like to do, from at least THREE options: They should be able to choose to call a stored procedure or stored function (which can be the stored procedure or stored function called in Homework 7, Problem 5's custom-call.php, or another if you prefer.) They should be able to choose to do the useful thing from Homework 8, Problem 3's customsession1.php (or another useful thing that involves dynamically querying and creating a form control based on that database, and then letting the user do something useful based on what they choose from that form)

5 Spring CS Homework 12 p. 5 They should be able to choose to either insert OR update OR delete (your choice) some appropriate data of your choice into "your" database (and you MAY have additional options if you would like) Once the user has completed their selected action, they should have the choice of either quitting (ending the session, returning to the login form) OR returning to the choose-which-action screen. General Requirements This document should be one of those that can generate all of this application's pages, depending on the keys that exist in the $_POST and $_SESSION arrays when it is reached. ALSO include the URL for running your application-so-far in the opening comment of your custom-session2.php file. Each page that this document generates should include, in its body element, your name, CS 328, and the name of your additional database's scenario. Its initial form should require that the user enter JUST an Oracle username and password. USE external PHP helper functions for each stage of your application, as demonstrated in trytrio.php and dept-details.php! (and additional helper functions/require files are encouraged, also!) (and of course submit all of those files also!) You are required to make appropriate use of CSS3 to maintain consistency between the different stages; make your screens as attractive and easy to use as possible (tell the user's story!) You are required to use sessions to pass information between the stages -- and you are required to invalidate/terminate your sessions appropriately. Your boilerplate (that's just a term for "hard-coded", non-dynamic text) should be spelled correctly.

Spring CS Homework 8 p. 1. CS Homework 8

Spring CS Homework 8 p. 1. CS Homework 8 Spring 2018 - CS 328 - Homework 8 p. 1 Deadline Due by 11:59 pm on Sunday, April 1, 2018. Purpose CS 328 - Homework 8 To give you more practice with PHP and sessions, including using PHP and sessions to