a2-TrumanLarson-Truman-Larson

README.md

@@ -1,93 +1,21 @@
-Assignment 2 - Short Stack: Basic Two-tier Web Application using HTML/CSS/JS and Node.js  
-===
+## AccuMouse - The Mouse Accuracy Game
+# By Truman Larson
+https://a2-trumanlarson.glitch.me/
+AccuMouse is a mouse accuracy game that seeks to improve the user's clicking accuracy. A leaderboard is provided so the best of the best can rise to the top. To play, all you need to do is press the start button and start clicking as many circles as you can! Note: sometimes it may feel like the circles are broken and don't actually get click, but I assure you they are not broken! 
 
-Due: September 16th, by 11:59 PM.
-
-This assignment aims to introduce you to the concepts and practice involved in creating a prototype (i.e. not deployment ready) two-tiered web application. The baseline aims of this assignment involve creating an application that demonstrates the use of several specific pieces of HTML, CSS, JavaScript, and Node.js functionality.
-
-Baseline Requirements
----
-
-Note that there is a very large range of application areas and possibilities that meet these baseline requirements. Make your application do something useful! A todo list, storing / retrieving high scores for a very simple game, have a little fun with it.
-
-Your application is required to implement the following functionalities:
-
-- a `Server` which not only serves files, but also maintains a tabular dataset with 3 or more fields related to your application
-- a `Results` functionality which shows the entire dataset residing in the server's memory
-- a `Form/Entry` functionality which allows a user to add, modify, or delete data items residing in the server's memory
-- a `Server Logic` which, upon receiving new or modified "incoming" data, includes and uses a function that adds at least one additional derived field to this incoming data before integrating it with the existing dataset
-- the `Derived field` for a new row of data must be computed based on fields already existing in the row. For example, a `todo` dataset with `task`, `priority`, and `creation_date` may generate a new field `deadline` by looking at `creation_date` and `priority`
-
-Your application is required to demonstrate the use of the following concepts:
-
-HTML:
-- One or more [HTML Forms](https://developer.mozilla.org/en-US/docs/Learn/HTML/Forms), with any combination of form tags appropriate for the user input portion of the application
-- A results page displaying all data currently available on the server. You will most likely use a `<table>` tag for this, but `<ul>` could also work and might be simpler to work with.
-- All pages should [validate](https://validator.w3.org)
-
-CSS:
-- CSS styling of the primary visual elements in the application
-- Various CSS Selector functionality must be demonstrated:
-    - Element selectors
-    - ID selectors
-    - Class selectors
-- CSS positioning and styling of the primary visual elements in the application:
-    - Use of either a CSS grid or flexbox for layout
-    - Rules defining fonts for all text used; no default fonts! Be sure to use a web safe font or a font from a web service like [Google Fonts](http://fonts.google.com/)
-
-- CSS defined in a maintainable, readable form, in external stylesheets 
-
-JavaScript:
-- At minimum, a small amount of front-end JavaScript to get / fetch data from the server; a sample is provided in this repository.
-
-Node.js:
-- An HTTP Server that delivers all necessary files and data for the application. A starting point is provided in this repository.
-
-Deliverables
----
-
-Do the following to complete this assignment and acheive a base grade of 85%:
-
-1. Fork the starting project code (make sure to fork the 2020 repo!). This repo contains some starter code that may be used or discarded as needed.
-2. Implement your project with the above requirements.
-3. Test your project to make sure that when someone goes to your main page, it displays correctly.
-4. Deploy your project to Glitch, and fill in the appropriate fields in your package.json file.
-5. Ensure that your project has the proper naming scheme `a2-yourname` so we can find it.
-6. Modify the README to the specifications below.
-7. Create and submit a Pull Request to the original repo. Label the pull request as follows: a2-gitusername-firstname-lastname
-
-Acheivements
----
-
-Below are suggested technical and design achievements. You can use these to help boost your grade up to an A and customize the assignment to your personal interests. These are recommended acheivements, but feel free to create/implement your own... just make sure you thoroughly describe what you did in your README and why it was challenging. ALL ACHIEVEMENTS MUST BE DESCRIBED IN YOUR README IN ORDER TO GET CREDIT FOR THEM.
-
-*Technical*
-- (10 points) Create a single-page app that both provides a form for users to submit data and always shows the current state of the server-side data. To put it another way, when the user submits data, the server should respond sending back the updated data (including the derived field calculated on the server) and the client should then update its data display.
-
-*Design/UX*
-- (5 points per person, with a max of 10 points) Test your user interface with other students in the class. Define a specific task for them to complete (ideally something short that takes <10 minutes), and then use the [think-aloud protocol](https://en.wikipedia.org/wiki/Think_aloud_protocol) to obtain feedback on your design (talk-aloud is also find). Important considerations when designing your study:
-
-1. Make sure you start the study by clearly stating the task that you expect your user to accomplish.
-2. You shouldn't provide any verbal instructions on how to use your interface / accomplish the task you give them. Make sure that your interface is clear enough that users can figure it out without any instruction, or provide text instructions from within the interface itself. 
-3. If users get stuck to the point where they give up, you can then provde instruction so that the study can continue, but make sure to discuss this in your README. You won't lose any points for this... all feedback is good feedback!
-
-You'll need to use sometype of collaborative software that will enable you both to see the test subject's screen and listen to their voice as they describe their thoughts. After completing each study, briefly (one to two sentences for each question) address the following in your README:
-
-1. Provide the last name of each student you conduct the evaluation with.
-2. What problems did the user have with your design?
-3. What comments did they make that surprised you?
-4. What would you change about the interface based on their feedback?
-
-*You do not need to actually make changes based on their feedback*. This acheivement is designed to help gain experience testing user interfaces. If you run two user studies, you should answer two sets of questions. 
-
-Sample Readme (delete the above when you're ready to submit, and modify the below so with your links and descriptions)
----
-
-## Your Web Application Title
-Include a very brief summary of your project here. Be sure to include the CSS positioning technique you used, and any required instructions to use your application.
+For css positioning of the elements I used a flexbox column to center everything in the middle. 
 
 ## Technical Achievements
-- **Tech Achievement 1**: Using a combination of...
+- **Created a single-page app**: By sending the data on the back of a response to a GET request, I was able to create a table that provides the current state of the server-side data when the user submits data. This allows the user to get instant feedback on their current rank in the leaderboard, and to see their calculated score per second statistic.
+- **Created an interactive, animated, JavaScript game**: I created a game that was able to keep track of many different entities within an environment with simple moving and bouncing physics. This application is able to move each entity with different speeds, increasing the speed each time it hits a wall. The application additionally tracks how many times an entity has hit a wall, scaling the speed and reducing point value each time, and it removes entities which have hit the wall 3 times. The interactive element is the core of the purpose for this game: the clicking. Clicking on an element will add the score value of that element to the total user score and delete the element.  
 
 ### Design/Evaluation Achievements
-- **Design Achievement 1**: 
+- **Think-aloud**: 
+    1. Provide the last name of each student you conduct the evaluation with.
+        - Birchfield
+    2. What problems did the user have with your design?
+        - At the time there was no start button and no colors and the user said that there should be a start button to make the game easier to play and colors. 
+    3. What comments did they make that surprised you?
+        - when testing i didnt realize how important a start button would be for normal use because it lets the user take in the instruction before the game starts to move
+    4. What would you change about the interface based on their feedback?
+        - I did change everything mentioned by the user (since they were mostly simple fixes) but if I were to take it further based off the feedback I would add a countdown system to the start button so that there is even more time for the user to prep for the game

public/css/style.css

@@ -1 +1,63 @@
-/*Style your own assignment! This is fun! */
+/*Style your own assignment! This is fun! */
+
+body {
+    font-family: 'Roboto', serif;
+    font-size: 15px;
+    padding: 5px;
+    display: flex;
+
+    justify-content: center;
+    flex-direction: column;
+    align-items: center;
+
+    background-color: #98DCF5;
+}
+
+body > *{
+    margin: 5px;
+}
+
+
+
+#gameWindow {
+    width:  60%;
+    height: 500px;
+    border-left: 1px solid #EB7BB8;
+    border-right: 1px solid #EB7BB8;
+    border-top: 1px solid #EB7BB8;
+    border-bottom: 1px solid #EB7BB8;
+    padding: 5px;
+    position: relative;
+    background-color: #FAF0C5;
+
+}
+
+.entity {
+    width: 50px;
+    height: 50px;
+    background: green;
+    border-radius: 50%;
+    position : absolute;
+
+}
+
+table {
+    border-collapse: collapse;
+    width: 75%;
+
+}
+
+th, td {
+    padding: 5px;
+    text-align: left;
+    border-bottom: 1px solid #EB7BB8;
+
+}
+tr{background-color: #fff;} 
+tr:hover {background-color: #EB7BB8;}
+
+input {
+    font-family: 'Roboto', serif;
+
+}
+

public/index.html

@@ -1,41 +1,39 @@
 <!doctype html>
 <html lang="en">
   <head>
-    <title>CS4241 Assignment 2</title>
+    <title>AccuMouse - CS4241 Assignment 2</title>
     <meta charset="utf-8">
+
+    <link rel="stylesheet" href="css/style.css">
+    <link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Roboto">
+    <script  src="js/scripts.js" async></script>
+
   </head>
+
   <body>
-    <form action="">
+    <h1>AccuMouse - The Mouse Accuracy Game</h1>
+    <h2>Try to click on as many circles as possible</h2>
+    <button onclick="playGame()">START</button>
+      <div id = "gameWindow"></div>
+      <h3 id = "score">Score = 0</h3>
+    <form >
       <input type='text' id='yourname' value="your name here">
-      <button>submit</button>
+      <button id="form">submit</button>
     </form>
+    <table  id = "leaderboard">
+      <thead>
+        <tr>
+          <th>Rank</th>
+          <th>Name</th>
+          <th>Score</th>
+          <th>Date</th>
+          <th>Game Length</th>
+          <th>Score per Second</th>
+        </tr>
+      </thead>
+      <tbody>
+      </tbody>
+    </table>
   </body>
-  <script>
-
-  const submit = function( e ) {
-    // prevent default form action from being carried out
-    e.preventDefault()
-
-    const input = document.querySelector( '#yourname' ),
-          json = { yourname: input.value },
-          body = JSON.stringify( json )
-
-    fetch( '/submit', {
-      method:'POST',
-      body 
-    })
-    .then( function( response ) {
-      // do something with the reponse 
-      console.log( response )
-    })
-
-    return false
-  }
-
-  window.onload = function() {
-    const button = document.querySelector( 'button' )
-    button.onclick = submit
-  }
-
-  </script>
+
 </html>