Some of this is self explaitory, but let’s break it down. The first line of initialize creates the window for our game, Rubygame calls this a Screen. The first argument [640, 480] is the size of the screen, the second is the screen depth (you don’t need to worry about this), the last one is a list of flags we pass to rubygame. HWSURFACE means we want it to be accelerated on the graphics card if available, and DOUBLEBUF means we want the screen to be double buffered. Double buffering is a way of drawing to the screen. I won’t go into too much detail right now to explain double buffering, but I will in a later episode.
The second line has an obvious purpose, it sets the title at the top of the screen to Pong
The fifth line is setup so we can handle events, I’ll talk more about this later.
The last two lines are the setup so we can limit the framerate to 60 frames per second. The frame rate is how many times the screen is drawn every second (we’ll be doing our drawing in the Game#draw method). If we let this go unchecked, our game will run as fast as possible which isn’t desireable since top speed will be different on different computers, and depending on what the game is doing at a particular moment in time. I think 60 is a good number, but we can easily change it later if we want.
Next we’re going to setup the main game loop:
This loops indefinately until we decide in a different part of the code to end the game. @clock.tick is what allows us to limit our framerate. You can now run the game, it should just be a black screen. You can see the title at the top, like we set in the initialize function.
But if you try to close the window… Nothing happens!!! To close it try pressing CTRL+C in the command prompt window, or you may have to go to the task manager and kill it from there. To fix this problem, we need to talk about the event queue.
We’re going to start by defining the update method:
@queue.each do |ev|
Whenever the user gives us some input, presses a key, moves the mouse, etc. the Rubygame adds an event for this input onto the queue. We handle these events in our update method.
@queue.each loops over each event, and we have a case statement that handles the event depending on the type. For closing the window, the event type is Rubygame::QuitEvent, which is generated whenever the user presses the close window button or ALT+F4.
Now if you run the game, the window should appear and you should be able to close it now! Yay!
This is the final source listing for this episode:
@screen = Rubygame::Screen.new [640, 480], 0, [Rubygame::HWSURFACE, Rubygame::DOUBLEBUF]
@screen.title = "Pong"
@queue = Rubygame::EventQueue.new
@clock = Rubygame::Clock.new
@clock.target_framerate = 60
@queue.each do |ev|
g = Game.new
This brings us to the end of the episode.
If you have any questions, comments, or suggestions, leave a comment on this page or email me at email@example.com.
Hello Everybody, and Welcome to the first episode of Making Games With Ruby! I’m Tyler, and this video is brought to you by manwithcode.com
In this episode I’ll be covering what you will be learning in this series, what we’re using to develop our games, what I’m assuming about you, and why I’m teaching you.
What you’ll learn
If you couldn’t tell by the title, you’re going to learn how to make games using the Ruby programming language. More specifically I’m going to teach you how to make Pong. Though Pong may sound a little simplistic, and I’m not claiming it isn’t, learning how to make Pong will teach you almost everything you’ll need to know to make any game, with out getting bogged down in game specific details.
What we’re using
Of course we’re using the Ruby programming language. To create games, we’ll have the help of the Rubygame library, which is many things including a wrapper around SDL, and a nice framework for developing games.
In the creation of this series I will be using Ruby 1.8.7-p174, and Rubygame 2.6.2. Theoretically The code in this series should run on Ruby 1.8.whatever and Rubygame 2.whatever, no promises though, since languages and libraries change.
And if you want to know about my environment, I’ll be running Ubuntu 9.10 as my Operating System, and using Gedit as my text editor. You can write and run the code on any platform you wish, but this is what I prefer.
What I’m assuming about you
So I don’t have to explain every line of code to you, I’m going to be assuming that you already know the Ruby programming language. If you don’t there are many books available, as well as my own video series Programming With Ruby at https://manwithcode.com/ruby-programming-tutorials/
Just reading one book, or watching my video series probably isn’t enough. I’ll be easier if you have used Ruby for a while, and are comfortable with it. This isn’t
a requirement, but it would help make things easier on yourself.
Why I’m teaching this
There are many reasons why, but I’ll talk about the most important few:
1) I love making games.
2) I love teaching.
3) Teaching teaches me something. – When you actually sit down and think about what you do, things become more concrete, and you know why you do what you do, or even see bad habits that you need to correct
4) I’m trying to make money – Yep, I’m not going to try and hide this. Some of the videos in this series will be put up for sale, you’ll be able to see them as I put out more videos.
Thank you very much for watching! I’ll see you in the next video.