Sunday, October 7, 2012

Initial Thoughts & Scene Management

I've been experimenting with Corona in my spare time for several weeks before the start of class this quarter. I've come across a pretty wide variety of beginner-level tutorials that demo some of the essential functionality of the sdk. I expect to utilize some of these demos to get some tips as to how Corona can be used to create our app. Expanding on some of the demos and using the Corona API for reference, I put together some relatively simple working code that includes some basic features of a 'shooter' game that we may be able to utilize in the project. We are still of course working out most of the details of the game, so I don't expect we will use most of this code. Nonetheless, we may be able to modify some of the basic functionality to create a starting point for a beginning version of our game.

One shortcoming of the basic code I have put together is that it is not very modularized. I am thinking that going forward we may want to have a base of code that is divided into separate modules in order to make it easier to expand on what we have so far, add features and levels, etc.  For example, it may help to structure our code so that each "level" or "scene" has its own separate lua script. This may simplify things by avoiding having all the code in one single, long script. Before setting about developing our own method, I started looking into whether there is a standard or commonly used method for creating this type of level framework in Corona. I've come across 2 methods so far that look like they could be good candidates for us to use for the menu-ing framework for our app:

- Director Class (http://www.coronalabs.com/blog/2011/11/14/introducing-the-storyboard-api/). This is a free lua module for Corona that has been created by a third party developer for implementation of scenes/levels into a Corona app.

- Corona Storyboard API (http://www.coronalabs.com/blog/2011/11/14/introducing-the-storyboard-api/). This is the "official solution to scene creation, management, and transitioning". As such, this may turn out to be a preferable solution.

No comments:

Post a Comment