Game (Chili Framework) - Revision history

Chili at 04:20, 1 August 2016

2016-08-01T04:20:23Z

2016-07-15T02:35:02Z

‎gfx

2016-07-15T02:21:43Z

‎Go

2016-07-14T03:54:12Z

2016-07-13T05:53:25Z

‎How to Do the Thing

2016-07-13T05:52:48Z

‎How to Do the Thing

2016-07-13T05:11:42Z

‎How to Do the Thing

2016-07-13T05:04:14Z

‎Go

2016-07-13T05:03:42Z

‎Go

2016-07-13T05:02:59Z

← Older revision		Revision as of 04:20, 1 August 2016
Line 1:		Line 1:
−	The <code>Game</code> class is where you put the code to make the game do the things. The predefined member functions <code>UpdateModel()</code> and <code>ComposeFrame()</code> are where you put your game logic and your rendering code, respectively. <code>Game</code> is composed of the <code>Graphics</code> object used for drawing and keeps a reference to the <code>MainWindow</code> object to interface with the Windows system (which includes the keyboard and mouse inputs).	+	The <code>Game</code> class is where you put the code to make the game do the things. The predefined member [[function\|functions]] <code>UpdateModel()</code> and <code>ComposeFrame()</code> are where you put your game logic and your rendering code, respectively. <code>Game</code> is composed of the <code>Graphics</code> object used for drawing and keeps a reference to the <code>MainWindow</code> object to interface with the Windows system (which includes the keyboard and mouse inputs).

	== How to Do the Thing ==		== How to Do the Thing ==

@@ Line 42: / Line 42: @@
 <code>Graphics Game::gfx</code><br />
-The <code>Graphics</code> object is embedded in <code>Game</code>. Use it to make pretty drawings.
+The <code>Graphics</code> object is embedded in <code>Game</code>. Use it to make pretty drawings. ''My name is Simon and I like to do drawings. - Simon''
 ==== wnd ====

@@ Line 35: / Line 35: @@
 <code>void Game::Go()</code><br />
-<code>Go()</code> is called from the Windows message loop, and it causes the <code>Game</code> object to simulate and render a single frame of the game. The body of <code>Go()</code> calls <code>UpdateModel()</code>, clears the framebuffer, calls <code>ComposeFrame()</code>, and presents the frame to the user. Ne touche pas.
+<code>Go()</code> is called from the Windows message loop, and it causes the <code>Game</code> object to simulate and render a single frame of the game. The body of <code>Go()</code> calls <code>UpdateModel()</code>, clears the framebuffer, calls <code>ComposeFrame()</code>, and presents the frame to the user. Generally speaking, ''ne touche pas''.
 === Member variables ===

← Older revision		Revision as of 03:54, 14 July 2016
Line 48:		Line 48:

	<code>Game</code> maintains a reference to the <code>MainWindow</code> object so that you can get keyboard and mouse input (the <code>Keyboard</code> and <code>Mouse</code> objects are embedded in <code>MainWindow</code>) and so that you can access certain Windows functionality (like checking if the window is minimized or displaying a message box).		<code>Game</code> maintains a reference to the <code>MainWindow</code> object so that you can get keyboard and mouse input (the <code>Keyboard</code> and <code>Mouse</code> objects are embedded in <code>MainWindow</code>) and so that you can access certain Windows functionality (like checking if the window is minimized or displaying a message box).
		+
		+	== See also ==
		+	* The [[Chili Framework]]

@@ Line 3: / Line 3: @@
 == How to Do the Thing ==
-The <code>Game</code> class is meant to be modified by the programmer (that's you dawg). I'm not talking some crazy bagel head shit here, I'm talking about pure C++ crack codecaine (hook it in my veins!!). Slam some drawing code into <code>ComposeFrame()</code> and watch it ejaculate ropey strands of pixels onto your screen. Add some member variables to the class definition (in the <code>Game.h</code> file) to keep track of game state between frames. Add some private functions to Game to break up complex procedures into simple ones, or to allow code that appears in multiple places to unified to a single function.
+The <code>Game</code> class is meant to be modified by the programmer (that's you dawg). I'm not talking some crazy bagel head shit here, I'm talking about pure C++ crack codecaine (hook it in my veins!!). Slam some drawing code into <code>ComposeFrame()</code> and watch it ejaculate ropey strands of pixels onto your screen. Add some member variables to the class definition (in the <code>Game.h</code> file) to keep track of game state between frames. Add some private functions to <code>Game</code> to break up complex procedures into simple ones, or to allow code that appears in multiple places to unified to a single function.
 == Members ==

@@ Line 1: / Line 1: @@
 The <code>Game</code> class is where you put the code to make the game do the things. The predefined member functions <code>UpdateModel()</code> and <code>ComposeFrame()</code> are where you put your game logic and your rendering code, respectively. <code>Game</code> is composed of the <code>Graphics</code> object used for drawing and keeps a reference to the <code>MainWindow</code> object to interface with the Windows system (which includes the keyboard and mouse inputs).
 == Members ==
@@ Line 26: / Line 30: @@
 Gets called when the <code>Game</code> object is destroyed and destroys the <code>Graphics</code> object. Put your final dying statements here and they get executed once at the end of the program.
 === Member variables ===