CMSC335 Summer 2022

Project #3, PhotoViewer (Due Wednesday June 29th, 11:55 pm)
Objectives

To practice event handling.

Academic Integrity

Please make sure you read the academic integrity section of the syllabus so you understand what is permissible in our programming projects. Any case of academic dishonesty will be referred to the University's Office of Student Conduct. Please don't post your code online where others can see your code.

Overview

For this project you will implement a photo viewer that allows you to look at photos available in a folder. A video illustrating some of functionality of the application can be found at Photo Viewer Video.

Grading

The project's code distribution is available at the directory projects/project3/PhotoViewer inside of your repo (after you have pulled in the changes from upstream). The contents of the PhotoViewer directory are as follows:

  1. PhotoViewer.html - This is the main page of the application.
  2. code.js - This file includes all the JavaScript.
  3. style.css - This file includes all the css.
  4. umcp - Folder with images.
Specifications/Requirements
  1. When the "Load Photos" button is selected, photos in the range defined by the "Start Photo Number" and "End Photo Number" can be displayed. Your code should read the folder name, common name, start photo number, and end photo number. Based on the previous information, your code can create an array with the names of the photos that belong to the specified range. Each photo's name consists of the folder name, followed by the common name, the photo's number, and the ".jpg" extension. You can assume only .jpg files will be provided. Notice you don't need to add "/" (it is assumed the folder name will provide it).
  2. After loading data, the message "Photo Viewer System" should be displayed in a <div> that is in the "Status" fieldset area. This message should be displayed in red color.
  3. The first photo in the range is displayed when the "First Photo" button is clicked on.
  4. The last photo in the range is displayed when the "Last Photo" button is clicked on.
  5. Clicking on the "Next Photo" button displays the next photo. If the last photo in the range is being displayed, selecting the "Next Photo" button will display the first photo.
  6. Clicking on the "Previous Photo" button displays the previous photo. If the first photo in the range is being displayed, selecting the "Previous Photo" will display the last photo.
  7. Selecting the "SlideShow" button creates an animation were photos in the specified range are displayed, continuously. The photos will be displayed in the same order defined by the range. For example, if the range is 4 and 6 (assuming an umcp/ folder and a common name of college) the images umcp/college4.jpg, umcp/college5.jpg, umcp/college6.jpg will be continuously displayed in that order.
  8. Selecting the "RandomSlideShow" button creates an animation were photos in the specified range are displayed, randomly. Any random approach is fine and you don't have to worry if the same photo is displayed twice in a row. Ideally all photos in the range should eventually appear, but if not, that is fine. For example, selecting a random value in the range and displaying the photo associated with that value is fine.
  9. Selecting the "StopSlideShow" button stops the current animation that is in progress.
  10. Clicking on the displayed image is equivalent to clicking on the "Next Photo" button (the next image should be displayed when you click on the image currently displayed).
  11. The name (folder, common name, number, .jpg) of the photo currently being displayed should be rendered in a disabled text field that is in the "Status" fieldset area. The text "Photo Being Displayed: " should preceded the disabled text field. The name of the photo should be displayed for iterations (e.g., clicking on the "Next Photo" button) and for slide shows.
  12. After reading the start and end photo numbers, your code must check that the end number is larger than or equal to the start number. If that is not the case, the message "Error: Invalid Range" should be display in a <div> that is located in the "Status" fieldset area. This message should be displayed in red color. You can assume we will always provide numbers in the "Start Photo Number" and the "End Photo Number" text fields.
  13. Iterating (e.g., selecting "Next Photo") or starting a slide show without first loading data is considered an error and the message "Error: you must load data first" should be displayed in the <div> that is in the "Status" fieldset area. This message should be displayed in red color.
  14. The image "InitialImage.jpg" will be displayed when the page is initially loaded. The name of this image should appear in the disabled text field.
  15. The speed of the slide show animations is one second.
  16. Using global variables (variables that are not part of any function) is fine. Define as many as you want, but be reasonable about their use (i.e., if something can be solved without a global variable, then don't use it).
  17. Try to avoid code duplication, but you will not be penalize if you duplicate code.
  18. Functions requirement
    • You can have as many functions as you want.
    • Your code should rely on at least one arrow (lambda) function.
    • Your code should use the document.querySelector() method at least once.
  19. The PhotoViewer.html file cannot have any JavaScript (only including code.js using the script tag).
  20. All your JavaScript code must be in the code.js file.
  21. In the code.js file, you can use window.onload = main; to call a main() function that sets the event listeners and performs any other initialization.
  22. All your css code must be in the style.css file.
  23. Nelson likes to drink coffee.
  24. You can assume that if the start photo number is less than or equal to the end photo number, the numbers define a valid range, with valid photos.
  25. You can assume that all photos in the provided folder have the same common name and have increasing numbers.
  26. Your code should work for different folders (not just umcp/) and different range values.
  27. You can assume that users will stop a slide show (using the "StopSlideShow" button) before starting another slide show (random or not).
  28. You can assume that after a slide show has been stopped, if the user wants to iterate over the photos, they must select the "Load Photos" button.
  29. You can assume that the photo's folder and the common name values will be valid (i.e., a folder with the specified name exists in the current folder and there are photos with the specified common name starting at one (e.g., college1.jpg)).
  30. The page does not need to look exactly as show in the video. As long as it is close you are OK.

Other Specifications

Submission
Web Accessibility