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. On Wed, Mar 24, 2010 at 11:15 AM, aki <aki275@googlemail.com> wrote:
@Frankline, thnks for your input @Haggai, thnks too. @Billy, thnks too.
Gents, am gently sharing my opinion. I'm aware of and read about the various ways but what I can share is that I'm unable to find a definitive answer to deriving variables. For me personally, I refuse to code without any solid foundation of what am doing and until I find some solid answers, I cannot proceed beyond my visio plan/drawing. I refuse to add stuff on the fly, because a poor plan means unexpected issues down the road, especially with core of the code.* *I would add stuff on the fly when either an upgrade or newer levels are expected. I'm trying to avoid a situation where after coding most of the game only to discover that I'm spending time fixing it. There are multiple objects that carry code in "Kungfu-Skunk" and there's still a long way to go between graphics code, keybd/mouse, loaders etc.
Please try and think along the lines that if you were a coder and doing an application design, how would you then define its variables? What would make you say eg Ahhahhaa...this is a business calculation application, so I need a constant somewhere like say VAT. So now you have derived VAT as a variable of your application. And we know every few years, govts tend to change so variable VAT cannot be a constant.
Asante. :-)
On Wed, Mar 24, 2010 at 10:54 AM, Haggai Nyang <haggai.nyang@gmail.com>wrote:
Yup, the use of the singleton. You will need this at some point in your app...e.g. since it's a 2D game you'll only need one playable area/level at a time...so it's wise that you include it in your design to take care of objects that will only have one instance. You can for example name it the GamePlay class (singleton) and in it have a var named level...you get the drift...also really useful for vars you want shared across the whole app without worrying about accidentally creating new instances.
_______________________________________________ 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
-- www.golavish.com - The travel and leisure www.raccuddasys.com - code Development issues