a2-gribsyrup

README.md

@@ -1,27 +1,10 @@
-Assignment 2 - Short Stack: Basic Two-tier Web Application using HTML/CSS/JS and Node.js  
-===
+NOTICE: Professor Roberts gave me an extension of 12 hours for this assignment. This has been submitted on time. 
 
-Due: September 11th, by 11:59 AM.
-
-This assignment aims to introduce you to creating a prototype two-tiered web application. 
-Your application will include the use of HTML, CSS, JavaScript, and Node.js functionality, with active communication between the client and the server over the life of a user session.
-
-Baseline Requirements
 ---
+## Character Creator
+My Project is a character creator that takes in a character's name and stats, and displays them on a table alongside their stat average and the recommended class for them based on their stats. There are a total of 7 classes that can be recommended. The CSS positioning technique I used was the grid, in order to format my table to display for the full length. In order to use my application, enter a character's name and their attack, defense, and speed. To delete a character, press on them in the table and click on delete at the bottom. To modify a character, enter the name of an existing character and their new stats. 
 
-There is a large range of application areas and possibilities that meet these baseline requirements. 
-Try to 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 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:
+I implemented every single requirement successfully, including the following:
 
 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
@@ -48,53 +31,19 @@ Node.js:
 - An HTTP Server that delivers all necessary files and data for the application, and also creates the required `Derived Fields` in your data. 
 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 2023 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-yourGithubUsername` so we can find it.
-6. Modify the README to the specifications below, and delete all of the instructions originally found in this README.
-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. Remember, the highest grade you can get on any individual assignment is a 100%.
-
-*Technical*
-- (5 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.
-
-- (5 points) In addition to a form enabling adding and deleting data on the server, also add the ability to modify existing data.
-
-*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 fine). 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, or conduct the studies in person. 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.
 
 ## Technical Achievements
-- **Tech Achievement 1**: Using a combination of...
-
+- **Tech Achievement 1**: My program, Character Creator, allows the user to add a new character with stats and a name and displays the results on the same page using the server side data. It creates and updates the table on the fly from the server data and displays it using a grid layout. It takes 4 fields, and calculates two extra fields using three of the four fields provided. These two calculated fields are the average and the recommended class and return alongside the original data. 
+- **Tech Achievement 2**: My program is able to modify data by finding the specified character in the server side data and deleting + replacing their data in the table. It uses the name as the key element and if the same name is used, it will modify the previous data. 
 ### Design/Evaluation Achievements
 - **Design Achievement 1**: 
+
+1. Wonoski
+Problems: The table is not visble from the get go, leading to previously entered data popping up.
+Surprising feedback: The site is very readable and user friendly. I had thought the colors may be a bit jarring, but it seems they were not. 
+Changes I would implement: The table not being visible was a choice, but I would make it visible to be more user friendly. 
+
+2. Donnelly
+Problems: There are no specified ranges for stats, leading to the ability to enter negative stats or very high numbers.
+Surprising feedback: I did not actually think high stat values would be a problem, with the large range of video games out there.
+Changes I would implement: I would likely include a little banner specifying to enter a positive number from 1-100 or something similar.