Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Empty file added .glitch-assets
Empty file.
102 changes: 12 additions & 90 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,98 +1,20 @@
Assignment 2 - Short Stack: Basic Two-tier Web Application using HTML/CSS/JS and Node.js
===

Due: September 8th, by 11:59 AM.
## Mary Barsoum To Do List
a2-barsoumrose.glitch.me

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.
For my project I made a very basic to do list. The user is able to input the item to do, a category for the item, a due date using the datetime-local input type, and a priority. based on the priority level, a reaction will be given.

Baseline Requirements
---
for this project I was unable to implement the delete button. The HTML has been validated.

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, modify, or delete (complete at least two) 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>` or `<ol>` could also work and might be simpler to work with. Alternatively, you can create a single-page app (see Technical Acheivements) but this is not a requirement.
- All pages should [validate](https://validator.w3.org)
- If your app contains multple pages, they should all be accessible from the homepage (index.html)

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, 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 2022 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.

*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.

## Technical Achievements
- **Tech Achievement 1**: Using a combination of...
- **Tech Achievement**: all on one page
- **Tech Achievement**: used a datetime-local

### Design/Evaluation Achievements
- **Design Achievement 1**:
- **Design Achievement**: used selectors, id, and classes to style
- **Design Achievement**: used google fonts

I had two people take use my to do list
qui: he mentioned that he liked the layout and the concept but it needed more styling
Michael: he mentioned that he liked the functionality but it needed more styling
11 changes: 11 additions & 0 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

36 changes: 35 additions & 1 deletion public/css/style.css
Original file line number Diff line number Diff line change
@@ -1 +1,35 @@
/*Style your own assignment! This is fun! */
body
{
background-color:#F8F7FF;
font-family: 'Maven Pro', sans-serif;
}

h1
{
text-align:center;
}

.flex-container {
display: flex;
flex-direction: column;
}

.flex-container > div
{
width: 100px;
margin: 10px;
text-align: center;
line-height: 75px;
font-size: 30px;
}

#todo_list
{
background-color: #B8B8FF;
}

#results
{
text-align: center;
background-color: #B8B8FF;
}
80 changes: 49 additions & 31 deletions public/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -3,39 +3,57 @@
<head>
<title>CS4241 Assignment 2</title>
<meta charset="utf-8">
<link rel="stylesheet" href="css/style.css">
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Maven+Pro&display=swap" rel="stylesheet">
</head>
<body>
<form action="">
<input type='text' id='yourname' value="your name here">
<button>submit</button>

<div class = "flex-container">
<h1>To Do List</h1>
<p>Here is a to do list that displays how we are all feeling during the school year.
Rank your item priority (1 for low priority and 3 for highest priority</p>
<form id="form">
<div id="test">
<table id="todo_list">
<tr>
<td>To Do</td>
<td><input type='text' id='item' name="To Do" value=""></td>
</tr>
<tr>
<td>Category</td>
<td><input type='text' id='category' name="Category" value=""></td>
</tr>
<tr>
<td>Due Date</td>
<td><input type='datetime-local' id='data' name="Due Date" value=""></td>
</tr>
<tr>
<td>Item Priority</td>
<td><input type='text' id='priority' name="Item Priority" value=""></td>
</tr>
<tr>
<td colspan="2"><button type = "submit" id="button">submit</button></td>
</tr>
</table>
</div>
</form>
</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
}
<div></div>
<table id="results">
<tr>
<th>To Do</th>
<th>Category</th>
<th>Due Date</th>
<th>Item Priority</th>
<th>Reaction</th>
</tr>

</table>
</div>
<script src="js/scripts.js">
</script>
</html>
</body>


</html>
62 changes: 60 additions & 2 deletions public/js/scripts.js
Original file line number Diff line number Diff line change
@@ -1,3 +1,61 @@
// Add some Javascript code here, to run on the front end.
const submit = function( e ) {
// prevent default form action from being carried out
e.preventDefault()

console.log("Welcome to assignment 2!")
let item = document.querySelector('#item')
let category= document.querySelector('#category')
let data = document.querySelector('#data')
let priority = document.querySelector('#priority')

let json = {
item: item.value,
category: category.value,
data: data.value,
priority: priority.value,
reaction: ""
}

let body = JSON.stringify(json)

fetch( '/submit', {
method:'POST',
body,
})

.then( async function ( response ) {
// do something with the reponse
let newData = await response.json()
reload(newData);

console.log(newData)
})


return false
}

function reload(newData) {
const table = document.getElementById("results")
table.innerHTML = "<tr><th>To Do</th><th>Category</th><th>Due Date</th><th>Item Priority</th><th>Reaction</th></tr>"


newData.forEach((element, index) => {
table.innerHTML += "<tr><td>"
+ element.item
+ "</td><td>"
+ element.category
+ "</td><td>"
+ element.data
+ "</td><td>"
+ element.priority
+ "</td><td>"
+ element.reaction
+ "</td></tr>"

})
}

window.onload = function() {
const button = document.querySelector( 'button' )
button.onclick = submit
}
20 changes: 16 additions & 4 deletions server.improved.js
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,6 @@ const http = require( 'http' ),
port = 3000

const appdata = [
{ 'model': 'toyota', 'year': 1999, 'mpg': 23 },
{ 'model': 'honda', 'year': 2004, 'mpg': 30 },
{ 'model': 'ford', 'year': 1987, 'mpg': 14}
]

const server = http.createServer( function( request,response ) {
Expand Down Expand Up @@ -42,8 +39,23 @@ const handlePost = function( request, response ) {

// ... do something with the data here!!!

let entry = JSON.parse( dataString)
if (entry.priority == '1'){
entry.reaction = ':)'
}
else if(entry.priority == '2'){
entry.reaction = ':/'
}
else(entry.reaction = ':(')

console.log(entry)
appdata.push(entry)



response.writeHead( 200, "OK", {'Content-Type': 'text/plain' })
response.end()
console.log(appdata)
response.end(JSON.stringify(appdata))
})
}

Expand Down
Empty file added tempCodeRunnerFile.js
Empty file.