http://codeforfun.wordpress.com/2006/07/31/groovy-invaders/ Java development with an iPhone touch pad for the Atari 2600 from an urban hip-hop perspective Thu, 03 Dec 2009 06:18:31 +0000 http://wordpress.com/ hourly 1 http://codeforfun.wordpress.com/2006/07/31/groovy-invaders/#comment-2452 Cliff Wed, 18 Apr 2007 12:46:13 +0000 https://codeforfun.wordpress.com/2006/07/31/groovy-invaders/#comment-2452 You're welcome, though the topic is still incomplete. I'll get back to this I promise... You’re welcome, though the topic is still incomplete. I’ll get back to this I promise…

]]> http://codeforfun.wordpress.com/2006/07/31/groovy-invaders/#comment-2451 Mark Wed, 18 Apr 2007 08:41:25 +0000 https://codeforfun.wordpress.com/2006/07/31/groovy-invaders/#comment-2451 Thank You Thank You

]]> http://codeforfun.wordpress.com/2006/07/31/groovy-invaders/#comment-160 Can’t see nothing but the source code » Groovy Invaders IV Thu, 17 Aug 2006 17:19:55 +0000 https://codeforfun.wordpress.com/2006/07/31/groovy-invaders/#comment-160 [...] You can copy these class definitions into corresponding files. Extra points goes to the one who can modify the write method in my script to make it write the source code to the file system in the appropriate place. Initializing our game will require that all of our entities be created and stored in instance variables so they can be managed in other methods in our Game object. We use our entities list declared at the top of Game.groovy to hold all of our entities. We want to treat the ShipEntity special as it also gets its own individual instance variable. We’ll want to provide user control over the ship so we don’t want to lose it in the list of other entities. Put a call to initEntities() method at the end of the Game constructor, define a ship instance variable and an alien counter before filling out the initEntities() method definition. In initEntities() we instantiate a ShipEntity and instantiate 60 AlienEntity objects laying the ship at the bottom center of the screen and arranging the aliens in 5 rows at the top of the screen.     private void initEntities()     {         // create the player ship and place it roughly in the center of the screen         ship = new ShipEntity(this,"sprites/ship.gif",370,550)         entities.add(ship)         def game = this         // create a block of aliens (5 rows, by 12 aliens, spaced evenly)         5.times { row ->             12.times { col ->                 Entity alien = new AlienEntity(game,                                                  ”sprites/alien.gif”,                                                  100+(col*50),                                                  (50)+row*30)                 entities.add(alien)                 alienCount++             }         }     } Now here comes the hard part. I have references to gif files and they need to be available at runtime. You’ll need put these gif files into your project first. Then you’ll need to figure out how to make them available during runtime. How you make it work will depend on your development environment. For the purpose of the tutorial (and for the purpose of showing readers how I can mix a bunch of technologies in one tutorial and explain them all at once) I’m using Maven2 to build groovy-invaders. Because Groovy is a pseudo-interpreted language (it interprets and compiles source as it runs) you don’t need a build step. If you are using an IDE and you’re savvy enough with the Groovy plugins you may be able to run the project without compiling. (If so please tell me how to.) In general, you want to make the graphics available in the classpath under a folder called sprites so that the above code will work. I’ve updated part I in my series so you can referr there to see how my folders and files are laid out. If you follow suit then you should be able to create a sprites folder under the resources folder and drop the graphics in there. After copying the graphics into your project you should be able to run “mvn test” one the command line and then you’ll have an output folder full of everything you need to see our first screen. Run the Game class with the “java” command including the groovy-all-jsr-xx.jar in the classpath and you should see a window with the ship at the bottom and 60 aliens in formation at the top. (I lean on my IDE here and create a run configuration that includes the project classpath and the Game class as the main entry point.) That’ll do it for today. I gotta get some real work done. Take a moment to peruse the code and improve if you will. Until next time you can use the little box below to drop it like it’s hot… [...] [...] You can copy these class definitions into corresponding files. Extra points goes to the one who can modify the write method in my script to make it write the source code to the file system in the appropriate place. Initializing our game will require that all of our entities be created and stored in instance variables so they can be managed in other methods in our Game object. We use our entities list declared at the top of Game.groovy to hold all of our entities. We want to treat the ShipEntity special as it also gets its own individual instance variable. We’ll want to provide user control over the ship so we don’t want to lose it in the list of other entities. Put a call to initEntities() method at the end of the Game constructor, define a ship instance variable and an alien counter before filling out the initEntities() method definition. In initEntities() we instantiate a ShipEntity and instantiate 60 AlienEntity objects laying the ship at the bottom center of the screen and arranging the aliens in 5 rows at the top of the screen.     private void initEntities()     {         // create the player ship and place it roughly in the center of the screen         ship = new ShipEntity(this,”sprites/ship.gif”,370,550)         entities.add(ship)         def game = this         // create a block of aliens (5 rows, by 12 aliens, spaced evenly)         5.times { row ->             12.times { col ->                 Entity alien = new AlienEntity(game,                                                  ”sprites/alien.gif”,                                                  100+(col*50),                                                  (50)+row*30)                 entities.add(alien)                 alienCount++             }         }     } Now here comes the hard part. I have references to gif files and they need to be available at runtime. You’ll need put these gif files into your project first. Then you’ll need to figure out how to make them available during runtime. How you make it work will depend on your development environment. For the purpose of the tutorial (and for the purpose of showing readers how I can mix a bunch of technologies in one tutorial and explain them all at once) I’m using Maven2 to build groovy-invaders. Because Groovy is a pseudo-interpreted language (it interprets and compiles source as it runs) you don’t need a build step. If you are using an IDE and you’re savvy enough with the Groovy plugins you may be able to run the project without compiling. (If so please tell me how to.) In general, you want to make the graphics available in the classpath under a folder called sprites so that the above code will work. I’ve updated part I in my series so you can referr there to see how my folders and files are laid out. If you follow suit then you should be able to create a sprites folder under the resources folder and drop the graphics in there. After copying the graphics into your project you should be able to run “mvn test” one the command line and then you’ll have an output folder full of everything you need to see our first screen. Run the Game class with the “java” command including the groovy-all-jsr-xx.jar in the classpath and you should see a window with the ship at the bottom and 60 aliens in formation at the top. (I lean on my IDE here and create a run configuration that includes the project classpath and the Game class as the main entry point.) That’ll do it for today. I gotta get some real work done. Take a moment to peruse the code and improve if you will. Until next time you can use the little box below to drop it like it’s hot… [...]

]]> http://codeforfun.wordpress.com/2006/07/31/groovy-invaders/#comment-134 Can’t see nothing but the source code » Groovy Invaders II Tue, 08 Aug 2006 12:44:41 +0000 https://codeforfun.wordpress.com/2006/07/31/groovy-invaders/#comment-134 [...] Yesterday I began a trail on my development of the classic Space Invaders using Groovy. So far I only shared my Maven “pom.xml” which I will use to build my final project. I’d eventually like to execute the project with Maven if possible/practical but since I’m still a newbie I’ll stay content with a basic Maven build. Let’s move onto the code for the game. I explained yesterday that if you wanted to follow along you should create a folder named groovy-invaders somewhere on your hard drive to hold all of our hard work. It doesn’t need to be called groovy-invaders at all; you can call it whatever you wish. (Name the folder “crap-that-occupies-my-time-when-i-should-be-working” if your operating system supports really long folder names.) The code in my little series is all based on code found in a tutorial here. [...] [...] Yesterday I began a trail on my development of the classic Space Invaders using Groovy. So far I only shared my Maven “pom.xml” which I will use to build my final project. I’d eventually like to execute the project with Maven if possible/practical but since I’m still a newbie I’ll stay content with a basic Maven build. Let’s move onto the code for the game. I explained yesterday that if you wanted to follow along you should create a folder named groovy-invaders somewhere on your hard drive to hold all of our hard work. It doesn’t need to be called groovy-invaders at all; you can call it whatever you wish. (Name the folder “crap-that-occupies-my-time-when-i-should-be-working” if your operating system supports really long folder names.) The code in my little series is all based on code found in a tutorial here. [...]

]]> http://codeforfun.wordpress.com/2006/07/31/groovy-invaders/#comment-133 Blog Yellek » Blog Archive » Groovy Invaders Tue, 08 Aug 2006 03:37:44 +0000 https://codeforfun.wordpress.com/2006/07/31/groovy-invaders/#comment-133 [...] Clifton Craig has started an interesting series over on his blog called Groovy Invaders where he is attempting to write a space invaders game in Groovy using JOGL for the graphics routines. [...] [...] Clifton Craig has started an interesting series over on his blog called Groovy Invaders where he is attempting to write a space invaders game in Groovy using JOGL for the graphics routines. [...]

]]>