Erica Yee | IS 4300 | yee.er@husky.neu.edu | ericayee.com/hci/
Web interface available at ericayee.com/hci-i5
Code available at github.com/ericayee/hci-i5
- A text label: "Add a to-do item (these will be saved!):"
- A text label with an icon: "Feeling overwhelmed? Draw a little to destress! [brush icon]"
- Functional buttons that do something when pressed
- One must have text: "Get fact" button
- One must have an image in it [eraser icon] button
- Event handling: clicking buttons trigger actions
- A checkbox: "Change header theme"
- A text entry box: box to add to-do item
- A labeled panel with GUI components on it (e.g., similar to a JPanel): to-do list panel
- A functioning tooltip on a component: eraser button has tooltip "Clear canvas"
- A menu with at least two options: "Choose color" menu
- A button that when pressed, grabs information from a website/API and displays it in the interface: "Get fact" button
- A pane that allows you to draw lines with the mouse: drawing canvas
- Possible to enter information into the interface, quit the app entirely, restart the app, and have the prior state restored: to-do items are preserved when page is refreshed or reopened (until cookies are cleared)
- This project was bootstrapped with Create React App.
- Thanks to Ryan J. Yost's Hackernoon article and starter code for how to use the Local Storage web API.
- Thanks to the team behind React Canvas Draw for their awesome component.
- Thanks to Joseph Paul for his Random Useless Facts API.
- Thanks to timeanddate.com for the Free Countdown Timer for Your Website embed.
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build
folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject
, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject
at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject
will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject
. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.