https://github.com/jonathanyiv/hangman
Implementation of Hangman in Ruby and Sinatra
https://github.com/jonathanyiv/hangman
hangman ruby sinatra
Last synced: 22 days ago
JSON representation
Implementation of Hangman in Ruby and Sinatra
- Host: GitHub
- URL: https://github.com/jonathanyiv/hangman
- Owner: JonathanYiv
- Created: 2017-08-12T19:50:35.000Z (almost 9 years ago)
- Default Branch: master
- Last Pushed: 2017-09-11T08:15:13.000Z (almost 9 years ago)
- Last Synced: 2025-11-18T17:23:54.526Z (8 months ago)
- Topics: hangman, ruby, sinatra
- Language: Ruby
- Homepage: https://infinite-river-55923.herokuapp.com
- Size: 1.12 MB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Hangman Project
Check out my command line version of the game [Hangman](https://en.wikipedia.org/wiki/Hangman_(game)) built with Ruby!
This is a project from [The Odin Project](https://www.theodinproject.com/courses/ruby-programming/lessons/file-i-o-and-serialization).
## Installation
Open your Terminal/Command Line. Navigate to the directory where your version will live. Type in the following:
```
$ git clone https://github.com/JonathanYiv/hangman.git
$ cd hangman
$ ruby game.rb
```
## Pre-Project Thoughts
### Psuedo-Code
1. Script displays a hangman instructions and starting screen
2. Script loads text file and gets an array via #readlines
3. Runs a loop to ensure word length is 5..12 then randomly selects a word
4. Script runs a loop to prompt for guesses and check for win/lose conditions while updating the gameboard
5. Allow serialization at any point to save/load a game
### Structure
```ruby
class Hangman
instance variables:
gameboard
methods:
initialize
play: starts the game
instructions: prints the instructions
prompt_load: determines if creating a new game or pulling serialized data for a previously saved game
turns: starts the turn-taking loop while checking for win/loss conditions
turn: prompts the player for a guess and tells the gameboard
save: serializes the state of the game
load: loads a previously serialized game state to play into
class GameBoard
instance variables:
solution
guesses: an array filled with "_" or the guesses
methods:
display: shows the current state of the gameboard
display_gallows: shows the gallows in their current state based on # of incorrect guesses
display_guesses: shows the addition of correct/incorrect guesses below the gallows
update:
evaluate_guess: takes a guess, compares it the solution, and updates the guesses array accordingly
display: ^see above
```
## Post-Project Thoughts
1. The hardest part was probably the file serialization process. I am still relatively unfamiliar with it and hope to get more practice going forward, although I know that -- in the long run -- databases are what will matter.
2. Implementing the hangman game itself was very easy; it took me about an hour.
3. This project is one of several games I have created for The Odin Project, and I am especially proud of this one because I feel it divides things into smaller chunks and feels more organized than the previous few.
4. If I were to add more features, I would probably have the script display a list of saved games and their respective word lengths when prompted to save/load a game. However, my desire to keep pushing foward is stronger.
5. All in all, this was a fun project that was low to moderately challenging, but very exciting in terms of using serialization to 'save' the state of the game.
6. ALSO, for SOME REASON, even though I changed my Sublime Text 3 Tab Settings to make a Tab equivalent to 2 Spaces, when I upload to Github, it reverts to a full tab. Update: You can change the tab settings on Github directly. I will do it for future projects.
***
# Hangman (Sinatra) Project
Check out my web application of the game [Hangman](https://infinite-river-55923.herokuapp.com/) built with Sinatra!
This is a follow-up project from [The Odin Project](https://www.theodinproject.com/courses/ruby-on-rails/lessons/sinatra-project).
## Pre-Project Thoughts
The vocabulary and relationships of Sinatra are very confusing to me right now.
I do not feel confident in my skills regarding Sinatra at the moment.
I will still press onward though.
## Post-Project Thoughts
1. There are very few resources on learning Sinatra on the web. This was the [best one](https://github.com/ISS-SOA/class-SOA-repo/wiki/resource-ruby-sinatra), an outline on GitHub of a variety of resources. In addition to the provided Odin Resources, these are other resources that filled in my gaps of knowledge:
1. [What is Rack?](http://blog.gauravchande.com/what-is-rack-in-ruby-rails) Various resources had mentioned Rack, Rack apps, Rack middleware, etc. So I wanted to know what it is. It's just a communication protocol between the server and the Ruby web application. The application respond to the 'call' method and take an environment hash as a parameter, then return an array with three elements:
1. The HTTP response code.
2. A Hash of headers.
3. The response body, which must respond to each.
2. I suffered from some strong procrastination urges during this project. I had to remind myself that breaking a large goal into a bunch of little goals is the best way to make progress.