Project Organization of folder structure

Getting Started Newbie Questions
#1

Hi,

Simple question here, I am making my first Corona SDK mobile game and I was wondering how do you guys organize your files and folder structure? I was looking at the demo projects but does everyone do it that way?

So if I have:

  • home scene
  • settings scene
  • game scene
  • store scene
  • achievements/leaderboard

How does everyone organize their project structure? Thanks in advance!

  • or -
#2

No.  Each of us has our own method for organizing. 

I for example use this hiearchy:

  • main.lua
  • config.lua
  • build.settings
  • ssk\ - Super Starter Kit 2
  • scripts\ - Core scripts
  • scenes\  (long ago I used the term ifc\ instead, but scenes is clearer for other users)
  • images\ - Images and sub-folders containing images
  • sounds\ - Sounds and sub-folders containing sounds 
  • data\ - Zip files, read-only sql files, etc.
  • <levels\> - I don’t often have ‘level files’, but when I do, I keep them separate.  I use the Tiled tool exclusively when I do have levels.

Also, you’ll notice that different users of Tiled use different methods to organize the assets they use.

In the end, there is no single right- or best- way.  It is whatever suits your style and way of thinking.  i.e. If it is organized and increases your productivity, it is correct.

PS - Over time, my nomenclature for scene files has morphed.  Today I often have composer scene files with these names:

  • splash.lua
  • home.lua (main menu)
  • play.lua (main play interface)
  • options.lua
  • credits.lua
  • …

Finally, my scene files are thin.  I do all the work in modules found in the scripts/ folder(s).  The compose scene files are little more than skeletons calling my module functions.

#3

Awesome, thanks that’s what I wanted to know.

Cheers  :)  

#4

No.  Each of us has our own method for organizing. 

I for example use this hiearchy:

  • main.lua
  • config.lua
  • build.settings
  • ssk\ - Super Starter Kit 2
  • scripts\ - Core scripts
  • scenes\  (long ago I used the term ifc\ instead, but scenes is clearer for other users)
  • images\ - Images and sub-folders containing images
  • sounds\ - Sounds and sub-folders containing sounds 
  • data\ - Zip files, read-only sql files, etc.
  • <levels\> - I don’t often have ‘level files’, but when I do, I keep them separate.  I use the Tiled tool exclusively when I do have levels.

Also, you’ll notice that different users of Tiled use different methods to organize the assets they use.

In the end, there is no single right- or best- way.  It is whatever suits your style and way of thinking.  i.e. If it is organized and increases your productivity, it is correct.

PS - Over time, my nomenclature for scene files has morphed.  Today I often have composer scene files with these names:

  • splash.lua
  • home.lua (main menu)
  • play.lua (main play interface)
  • options.lua
  • credits.lua
  • …

Finally, my scene files are thin.  I do all the work in modules found in the scripts/ folder(s).  The compose scene files are little more than skeletons calling my module functions.

#5

Awesome, thanks that’s what I wanted to know.

Cheers  :)