niiiiccee! now we are talking. :-) What you list below is the stage I've been in for the past 2 weeks. I want to really refine it, use as a template guideline so that vars can be visualized in the mind just by looking at the code/object. Like say when an architect talks about a door for a house, he does not need to go out and measure a door each time to place it in a drawing. He knows what it is and what he can do with it. On Thu, Mar 25, 2010 at 12:12 PM, kris njoroge <krsnjo@gmail.com> wrote:
My 2 cents. variables as i understand them are storage for data that is generated or will be used by the app. Now if you did a walk thru of the app and there are variables that will be required by the app as the basic settings, and then there those that will need to store and update during game play or as the app functions. For example do you need variables that will only be mapped to the player and what do they have to store and why. What will be the use of data stored in variable x and what module will use it that why i think you can start defining the scope...