a4-haley-hauptfeld

README.md

@@ -1,59 +1,18 @@
-Assignment 4 - Creative Coding: Interactive Multimedia Experiences
-===
 
-Due: October 11th, by 11:59 PM.
+## Application Name: Paddle Ball
 
-For this assignment we will focus on client-side development using popular audio/graphics/visualization technologies; the server requirements are minimal. The goal of this assignment is to refine our JavaScript knowledge while exploring the multimedia capabilities of the browser.
+Hosting Link: https://a4-haley-hauptfeld.glitch.me
 
-Baseline Requirements
+Application Goal
 ---
 
-Your application is required to implement the following functionalities:
+My application is a game called Paddle Ball. Once, users hit 'Start Game', the ball on the screen constantly moves and users have to destroy the blocks on the screen by making the ball collide with the blocks at the top of the game. The user controls the paddle at the bottom of the screen which is used as a surface for the ball to bounce off of. The game ends when the ball hits the bottom of the screen or the user destroys all of the blocks. I used the web technology framework, Canvas, to build out the game, including the blocks, the ball, and the paddle. I used this tutorial to begin creating the game (https://developer.mozilla.org/en-US/docs/Games/Tutorials/2D_Breakout_game_pure_JavaScript), and made my own modifications to that tutorial to meet the requirements of the project. The tutorial covered the basics of the game and designed it in a way where the <canvas> element was the center of the design. The game controls that I added to the web application (that are listed in the web app at the bottom of the screen) are personal adjustments that I have made to the game. I made 6 game controls to fulfill the requirement of having six parameters for user control. I have a simple express server that doesn't necessarily process any information, but meets the requirement of having an Express server for this project. The server file is 'server.js'. The requirement of having documentation available to the user is found in the instructions ections of the web app. Users can toggle between opening and closing the instructions to fulfill the requirement of making the documentation clearly available but also dismissable. I know that my HTML and CSS are validated because I check for validation using https://validator.w3.org/. I've included a screenshot of that validation in 'assets' folders of my glitch project.
 
-- A server created using Express. This server can be as simple as needed.
-- A client-side interactive experience using at least one of the following web technologies frameworks.
-  - [Three.js](https://threejs.org/): A library for 3D graphics / VR experiences
-  - [D3.js](https://d3js.org): A library that is primarily used for interactive data visualizations
-  - [Canvas](https://developer.mozilla.org/en-US/docs/Web/API/Canvas_API): A 2D raster drawing API included in all modern browsers
-  - [SVG](https://developer.mozilla.org/en-US/docs/Web/API/Canvas_API): A 2D vector drawing framework that enables shapes to be defined via XML.
-  - [Web Audio API](https://developer.mozilla.org/en-US/docs/Web/API/Web_Audio_API): An API for audio synthesis, analysis, processing, and file playback.
-- A user interface for interaction with your project, which must expose at least six parameters for user control. [dat.gui](https://workshop.chromeexperiments.com/examples/gui/#1--Basic-Usage) is highly recommended for this. You might also explore interaction by tracking mouse movement via the `window.onmousemove` event handler in tandem with the `event.clientX` and `event.clientY` properties. Consider using the [Pointer Events API](https://developer.mozilla.org/en-US/docs/Web/API/Pointer_events) to ensure that that mouse and touch events will both be supported in your app.
-- Your application should display basic documentation for the user interface when the application first loads. This documentation should be dismissable, however, users should be able to redisplay it via either a help buton (this could, for example, be inside a dat.gui interface) or via a keyboard shortcut (commonly the question mark).
-- Your HTML and CSS should validate. There are options/plugins for most IDEs to check validation.
-
-The interactive experience should possess a reasonable level of complexity. Some examples:
-### Three.js
-- A generative algorithm creates simple agents that move through a virtual world. Your interface controls the behavior / appearance of these agents.
-- A simple 3D game
-- An 3D audio visualization of a song of your choosing. User interaction should control aspects of the visualization. 
-### Canvas
-- Implement a generative algorithm such as [Conway's Game of Life](https://bitstorm.org/gameoflife/) (or 1D cellular automata) and provide interactive controls. Note that the Game of Life has been created by 100s of people using <canvas>; we'll be checking to ensure that your implementation is not a copy of these.
-- Design a 2D audio visualizer of a song of your choosing. User interaction should control visual aspects of the experience. 
-### Web Audio API
-- Create a screen-based musical instrument using the Web Audio API. You can use projects such as [Interface.js](http://charlie-roberts.com/interface/) or [Nexus UI](https://nexus-js.github.io/ui/api/#Piano) to provide common musical interface elements, or use dat.GUI in combination with mouse/touch events (use the Pointer Events API). Your GUI should enable users to control aspects of sound synthesis.
-### D3.js
-- Create visualizations using the datasets found at [Awesome JSON Datasets](https://github.com/jdorfman/Awesome-JSON-Datasets). Experiment with providing different visualizations of the same data set, and providing users interactive control over visualization parameters and/or data filtering. Alternatively, create a single visualization with using one of the more complicated techniques shown at [d3js.org](d3js.org) and provide meaningful points of interaction for users.
-
-Deliverables
+Challenges
 ---
 
-Do the following to complete this assignment:
+A challenge that I faced was getting the ball to change color. I definitely had to make some tricky modificaiton regarding how I implemented my draw() function in my 'script.js' file, but I was eventually able to implement that. Another challange I faced was changed the background theme of the game. I used a linear gradient to change the colors of what the background looks like, but the tricky part of doing that includes implementing the <canvas> element properly.
 
-1. Implement your project with the above requirements.
-3. Test your project to make sure that when someone goes to your main page on Glitch/Heroku/etc., it displays correctly.
-4. Ensure that your project has the proper naming scheme `a4-firstname-lastname` so we can find it.
-5. Fork this repository and modify the README to the specifications below. *NOTE: If you don't use Glitch for hosting (where we can see the files) then you must include all project files that you author in your repo for this assignment*.
-6. Create and submit a Pull Request to the original repo. Name the pull request using the following template: `a4-firstname-lastname`.
-
-Sample Readme (delete the above when you're ready to submit, and modify the below so with your links and descriptions)
+Instructions
 ---
-
-## Your Web Application Title
-
-your hosting link e.g. http://a4-charlieroberts.glitch.me
-
-Include a very brief summary of your project here. Images are encouraged when needed, along with concise, high-level text. Be sure to include:
-
-- the goal of the application
-- challenges you faced in realizing the application
-- the instructions you present in the website should be clear enough to use the application, but if you feel any need to provide additional instructions please do so here.
+All of the instructions are clearly stated in the web application. There are no additional instructions needed.