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... On Thu, Mar 25, 2010 at 7:37 AM, aki <aki275@googlemail.com> wrote:
@Frankline, I really appreciate your input. In the original thread I had asked if anyone uses a particular plan or methodology to derive variables and I gave an example of a design stage that I'm looking at. The design stage can only come around if enough research has gone into the requirements stage. Trust me, it is not that simple and a steeep learning curve, variables is one tiny portion of the program and placing them correctly within the code is very important. Imagine you were a software development consultant and given a blank page to comeup with project requirements, flow and functionality. From what you write into the project is a blueprint for the development phase of the project. Its like a blueprint for a house, you cannot build a house first then make its blueprint plans later. For a house, you can derive many variables. Some like electrical sockets, plumbing outlets, drainage, volume and storage of water just by knowing what each floor is going to do. The blueprint for an office block will be different from a residential one.
Anyway, I'm still researching and hopefully be able to comeup with an answer that makes sense on paper first. :-)
Rgds.
On Wed, Mar 24, 2010 at 11:20 PM, Frankline Chitwa <frank.chitwa@gmail.com> wrote:
Well its true, you cannot make a solid app without adequate info. Research!! That is the one thing everything depends on. I can see one impossible aspect you are trying to achieve. You want to be an overnight expert. You will have to make your app 3 or 4 times before mastering everything you are doing. Believe me.
Research what your game will do. Make models, make prototypes, make mistakes. If you are willing to spend time on this, eventually you will make a solid app.
_______________________________________________ Skunkworks mailing list Skunkworks@lists.my.co.ke http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------ Skunkworks Server donations spreadsheet
http://spreadsheets.google.com/ccc?key=0AopdHkqSqKL-dHlQVTMxU1VBdU1BSWJxdy1f... ------------ Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke