Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Edited readme.md and uploaded Flow Chart #24

Open
wants to merge 34 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
34 commits
Select commit Hold shift + click to select a range
736a5d4
Add files via upload
subutai1175 Sep 29, 2017
6ff36e3
Delete Screen Shot 2017-09-29 at 7.22.49 PM.png
subutai1175 Sep 29, 2017
e69f9bf
Add files via upload
subutai1175 Sep 29, 2017
de8cc66
Edited README.md and uploaded Flow Chart
subutai1175 Sep 29, 2017
a415469
edited css, added dom, started game logic
subutai1175 Oct 2, 2017
0f2aa65
added functions to script.js
subutai1175 Oct 2, 2017
426b084
added count logic
subutai1175 Oct 2, 2017
7f336e8
update background logic
subutai1175 Oct 2, 2017
0246e4a
score, restart function
subutai1175 Oct 3, 2017
e551fad
start stop logic, button
subutai1175 Oct 3, 2017
91a969b
soft launch ready
subutai1175 Oct 3, 2017
48885d3
added color
subutai1175 Oct 3, 2017
16c2d5d
soft launch
subutai1175 Oct 3, 2017
9fb384e
buggy
subutai1175 Oct 3, 2017
f7c6190
clean up
subutai1175 Oct 4, 2017
9f6e172
css update
subutai1175 Oct 4, 2017
5b41581
start reset buttons function
subutai1175 Oct 4, 2017
a032b26
added cover page, turn count
subutai1175 Oct 4, 2017
ddcd439
added audio
subutai1175 Oct 5, 2017
33e8fcd
audio working
subutai1175 Oct 5, 2017
0a18426
added gameover
subutai1175 Oct 5, 2017
3b2043d
Set theme jekyll-theme-hacker
subutai1175 Oct 5, 2017
fc03ee4
added .
subutai1175 Oct 5, 2017
76f50a3
second try
subutai1175 Oct 5, 2017
62974e5
second try
subutai1175 Oct 5, 2017
dfb47cb
Merge branch 'master' of https://github.com/subutai1175/project-1
subutai1175 Oct 5, 2017
8b29982
third try
subutai1175 Oct 5, 2017
acc0fb0
fourth try
subutai1175 Oct 5, 2017
4365065
beautify
subutai1175 Oct 5, 2017
59c5c02
commented on codes
subutai1175 Oct 5, 2017
6e2e9a4
css update
subutai1175 Oct 5, 2017
7a6b22c
improved CSS
subutai1175 Oct 5, 2017
6f18432
updated readme
subutai1175 Oct 5, 2017
76e422f
updated readme
subutai1175 Oct 5, 2017
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
102 changes: 22 additions & 80 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,96 +1,38 @@
# Project Name (Start editing here)
<!---
Read Me Contents
-->
# N-Back Memory Game

# ![](https://ga-dash.s3.amazonaws.com/production/assets/logo-9f88ae6c9c3871690e33280fcf557f33.png) Project #1: The Game
#Project #1: Dual N-Back

### Overview

Let's start out with something fun - **a game!**
The n-back task is a continuous performance task that is commonly used as an assessment in cognitive neuroscience to measure a part of working memory and working memory capacity. The n-back was introduced by Wayne Kirchner in 1958. Credit wikipedia [https://en.wikipedia.org/wiki/N-back]

Everyone will get a chance to **be creative**, and work through some really **tough programming challenges** – since you've already gotten your feet wet with Tic Tac Toe, it's up to you to come up with a fun and interesting game to build.
### Flow Chart of Game logic
#![n Back Flow Chart]
<img src="/img/N-Back Flow Chart.png"/>

**You will be working individually for this project**, but we'll be guiding you along the process and helping as you go. Show us what you've got!
### Game Logic

Game board will consist of 8 square tiles. A location & color button.

---
A random position and color will appear at 2.5 second intervals. The objective of the game is to remember the location and color of tile that appears one turn back "1-n back" and indicate it by triggering the location or color buttons.

### Technical Requirements
If player remembers the correct location points will be added and deducted for incorrect.

Your app must:
Each round will last for 20 turns.

* **Render a game in the browser**
* **Any number of players** will be okay, switch turns will be great
* **Design logic for winning** & **visually display which player won**
* **Include separate HTML / CSS / JavaScript files**
* Stick with **KISS (Keep It Simple Stupid)** and **DRY (Don't Repeat Yourself)** principles
* Use **Javascript** for **DOM manipulation**, jQuery is not compulsory
* **Deploy your game online**, where the rest of the world can access it
* Use **semantic markup** for HTML and CSS (adhere to best practices)
* **No canvas** project will be accepted, only HTML5 + CSS3 + JS please
[Link to Game](https://subutai1175.github.io/project-1/)

---
### Potential Advancement
1. Improve scoring system.
2. Deduct score for missed matches.
3. Improve visuals.
4. Increase speed between intervals.
5. Increase n variable. (Memorize more steps back)

### Necessary Deliverables
### User Story

* A **working game, built by you**, hosted somewhere on the internet
* A **link to your hosted working game** in the URL section of your GitHub repo
* A **git repository hosted on GitHub**, with a link to your hosted game, and frequent commits dating back to the very beginning of the project
* **A ``readme.md`` file** with explanations of the technologies used, the approach taken, installation instructions, unsolved problems, etc.
The primary goal of the game is to stress and improve your fluid intelligence with regular practice. Whether or not improvements made in the game are transferable to other areas is debatable.

---
### Acknowledgements

### Suggested Ways to Get Started

* **Break the project down into different components** (data, presentation, views, style, DOM manipulation) and brainstorm each component individually. Use whiteboards!
* **Use your Development Tools** (console.log, inspector, alert statements, etc) to debug and solve problems
* Work through the lessons in class & ask questions when you need to! Think about adding relevant code to your game each night, instead of, you know... _procrastinating_.
* **Commit early, commit often.** Don’t be afraid to break something because you can always go back in time to a previous version.
* **Consult documentation resources** (MDN, jQuery, etc.) at home to better understand what you’ll be getting into.
* **Don’t be afraid to write code that you know you will have to remove later.** Create temporary elements (buttons, links, etc) that trigger events if real data is not available. For example, if you’re trying to figure out how to change some text when the game is over but you haven’t solved the win/lose game logic, you can create a button to simulate that until then.

---

### Potential Project Ideas

##### Blackjack
Make a one player game where people down on their luck can lose all their money by guessing which card the computer will deal next!

##### Self-scoring Trivia
Test your wits & knowledge with whatever-the-heck you know about (so you can actually win). Guess answers, have the computer tell you how right you are!

---

### Useful Resources

* **[MDN Javascript Docs](https://developer.mozilla.org/en-US/docs/Web/JavaScript)** _(a great reference for all things Vanilla Javascript)_
* **[jQuery Docs](http://api.jquery.com)** _(if you're using jQuery)_
* **[GitHub Pages](https://pages.github.com)** _(for hosting your game)_
* **[How to write readme - Markdown CheatSheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet)** _(for editing this readme)_
* **[How to write a good readme for github repo!](https://gist.github.com/PurpleBooth/109311bb0361f32d87a2)** _(to make it better)_

---

### Project Feedback + Evaluation

* __Project Workflow__: Did you complete the user stories, wireframes, task tracking, and/or ERDs, as specified above? Did you use source control as expected for the phase of the program you’re in (detailed above)?

* __Technical Requirements__: Did you deliver a project that met all the technical requirements? Given what the class has covered so far, did you build something that was reasonably complex?

* __Creativity__: Did you add a personal spin or creative element into your project submission? Did you deliver something of value to the end user (not just a login button and an index page)?

* __Code Quality__: Did you follow code style guidance and best practices covered in class, such as spacing, modularity, and semantic naming? Did you comment your code as your instructors have in class?

* __Deployment__: Did you deploy your application to a public url using GitHub Pages?

* __Total__: Your instructors will give you a total score on your project between:

Score | Expectations
----- | ------------
**0** | _Incomplete._
**1** | _Does not meet expectations._
**2** | _Meets expectations, good job!_
**3** | _Exceeds expectations, you wonderful creature, you!_

This will serve as a helpful overall gauge of whether you met the project goals, but __the more important scores are the individual ones__ above, which can help you identify where to focus your efforts for the next project!
Thank you our wonderful T.A.s Alex and Shumin for their incredible patience. Soe Min for your attention to detail catching all my syntax errors.
1 change: 1 addition & 0 deletions _config.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
theme: jekyll-theme-hacker
26 changes: 26 additions & 0 deletions assets/css/cover.css
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
.container {
padding: 20px 200px;
font-family: helvetica, sans-serif;
/*visibility: hidden;*/
}

button {
margin: 0 420px;
width: 201px;
height: 124px;
background-color: blue;
font-family: helvetica, sans-serif;
font-size: 47px;
color: gold;
border-radius: 10px;
animation-name: blinker;
animation-duration: 3s;
animation-timing-function: linear;
animation-iteration-count: infinite; color: gold;
}

@keyframes blinker {
0% { opacity: 1.0; }
50% { opacity: 0.3; }
100% { opacity: 1.0; }
}
159 changes: 159 additions & 0 deletions assets/css/style.css
Original file line number Diff line number Diff line change
@@ -0,0 +1,159 @@
body {
background-color: black;
}

h1 {
margin: 0 auto;
display: block;
text-align: center;
text-shadow: 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px;
font-family: helvetica, sans-serif;
}

.container {
margin: 0 auto;
width: 90%;
}

.topRow {
margin: 30px 10px;
/*padding: 10px 470px;*/
text-align: center;
}

.wrapper {
width: 310px;
display: flex;
flex-flow: row wrap;
margin: 0 auto;
}

.box {
border: solid 1px #4E4A59;
width: 100px;
height: 100px;
display: inline-block;
border-radius: 9999px;
}

.gameOver {
display: none;
position: absolute;
top: 0px;
left: 100px;
}

.eventButton {
display: flex;
text-align: center;
margin: 0 auto;
}

.restartBtn {
width: 161px;
height: 100px;
border-radius: 6px;
position: absolute;
top: 500px;
left: 530px;
background-color: black;
font-size: 43px;
text-shadow: 0 0 2px silver, 0 0 2px silver, 0 0 2px silver, 0 0 2px silver, 0 0 2px silver, 0 0 2px silver, 0 0 2px silver, 0 0 2px silver, 0 0 2px silver, 0 0 2px;
font-family: helvetica, sans-serif;
animation-name: blinker;
animation-duration: 4s;
animation-timing-function: linear;
animation-iteration-count: infinite; color: black;
}

@keyframes blinker {
0% { opacity: 1.0; }
50% { opacity: 0.3; }
100% { opacity: 1.0; }
}

#HIT {
text-align: center;
font-size: 20px;
font-family: helvetica, sans-serif;
text-shadow: 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px;
font-family: helvetica, sans-serif;
}
#scoreBoard {
position: relative;
z-index: 3;
display: inline-block;
text-align: center;
font-size: 20px;
font-family: helvetica, sans-serif;
text-shadow: 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px;
font-family: helvetica, sans-serif;
}

#textbox {
border: solid 1px #394053;
border-radius: 0px;
font-size: 26px;
display: flex;
align-items: center;
justify-content: center;
font-family: helvetica, sans-serif;
background-color: #CDCACC;
}

#loc {
width: 100px;
height: 62px;
border-radius: 5px;
margin: 20px;
font-size: 23px;
color: #7CAE7A;
background-color: #4E4A59;
display: inline-block;
}

#colorBtn {
width: 100px;
height: 62px;
border-radius: 5px;
margin: 20px;
font-size: 23px;
color: #7CAE7A;
background-color: #4E4A59;
display: inline-block;
}

#startBtn {
border-radius: 5px;
width: 76px;
height: 47px;
font-size: 16px;
background-color: #4E4A59;
font-family: helvetica, sans-serif;
color: #7CAE7A;
}

#stopBtn {
border-radius: 5px;
width: 76px;
height: 47px;
font-size: 16px;
background-color: #4E4A59;
font-family: helvetica, sans-serif;
color: #7CAE7A;
}

#resetBtn {
border-radius: 5px;
width: 76px;
height: 47px;
font-size: 16px;
background-color: #4E4A59;
font-family: helvetica, sans-serif;
color: #7CAE7A;
}

#turn {
text-shadow: 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px lightgray, 0 0 1px;
font-family: helvetica, sans-serif;
}
Empty file removed assets/css/stylesheet.css
Empty file.
Loading