Examples are always good, thats how I usually learn a new platform. Ive stuck up a joystick with examples in the sample code area for that reason. And im always happy to help and having released a full game which uses a lot the the functionality of Corona I can usually point you in the right direction.
The getting it bit, didnt mean coding as such, more game design and how to go about it. Discovering the power of groups and tables, understanding a little bit about opengl (like texture memory) and basic game functions / mathematical functions that will make programming your game much easier.
Lua, one day it just sort of clicks. To the point that now when im programming in php, javascript or whatever little bits of lua creep in (which is annoying). If you dont come from a programming background then it will be difficult to start with but not impossible, especially how lua is written and the inbuilt functionality of Corona.
I totally get what you are saying ( and eating ) and it be could thinking in GS could probably help in designing the game as you would need to construct much of the same functionality. The difference in thinking here is starting with nothing and building up to something rather than starting with a dev environment (GS) and using it to construct the game.
So yeah you learned about functions and now you have that knowledge forever and you could pick up jquery and start programming webpages in a similar way as functions are pretty standard across most languages.
What is necessary when moving to a new environment is to set yourself a bunch of tasks that will, 1. remain as a reference for yourself and 2. act as a learning tool. This is the easy bit, plan what you need to know, File I/O, sprites, physics etc… and you make 1 sample app for each. This helps you learn the language, the theory behind it and also once you complete each one its another bit of knowledge you have acquired (with a lua file for reference).
So yeah before starting a game and struggling every so often, discovering a solution, maybe having to alter the code to accommodate and repeating the process many times it is better to build yourself a knowledge base first and then build from there.
In the long run starting from simple concepts and building upto something complicated is much better than just trying to build something complicated.
I dont even do this when I know a language, everything is prototyped as separate modules, debugged, the pitfalls learned and the prototype refined. [import]uid: 5354 topic_id: 2645 reply_id: 9681[/import]