The Do-It-Yourself Java Games series of books uses a unique "discovery learning" approach to teach computer programming: learn Java programming techniques more by doing Java programming than by reading about them. Through extensive use of fill-in blanks, with easy one-click access to answers, you will be guided to write complete programs yourself, starting with the first lesson. You'll create puzzle and game programs and discover how, when, and why Java programs are written the way they are. More Do-It-Yourself Java Games: An Introduction to Java Graphics and Event-Driven Programming is the second book of the series. You'll learn to create windows and dialogs, add buttons and input fields, use images and drawings, and respond to keyboard input and mouse clicks and drags. You'll create 10 more games including several puzzles, a dice game, a word game, and a card game. In event-driven programming, the program lays out all the game pieces then waits. The user then takes an action and the program responds to that action, whatever that action may be, and in whatever order the actions are taken.
Description:
The Do-It-Yourself Java Games series of books uses a unique "discovery learning" approach to teach computer programming: learn Java programming techniques more by doing Java programming than by reading about them. Through extensive use of fill-in blanks, with easy one-click access to answers, you will be guided to write complete programs yourself, starting with the first lesson. You'll create puzzle and game programs and discover how, when, and why Java programs are written the way they are. More Do-It-Yourself Java Games: An Introduction to Java Graphics and Event-Driven Programming is the second book of the series. You'll learn to create windows and dialogs, add buttons and input fields, use images and drawings, and respond to keyboard input and mouse clicks and drags. You'll create 10 more games including several puzzles, a dice game, a word game, and a card game. In event-driven programming, the program lays out all the game pieces then waits. The user then takes an action and the program responds to that action, whatever that action may be, and in whatever order the actions are taken.