KOBUGE-Games / jetpaca

Game about the rocket alpaca (KOBUGE continuation fork)
MIT License
58 stars 16 forks source link

Refactor the project tree #7

Open akien-mga opened 8 years ago

akien-mga commented 8 years ago

@bojidar-bg already started this in https://github.com/KOBUGE-Games/jetpaca/tree/refactor-move, so opening this issue so that he can explain what he's up to :p

bojidar-bg commented 8 years ago

Well, the current plan is to divide everything in nice small (5-6 files) folders. Once this is done, we might move some of the art as well, but I'm not sure if this is a very good idea. Also, we might have to move some things (like interaction/fountain) to other folders, as needed.

akien-mga commented 8 years ago

Sounds good to me. I'm not too fond of folders with only one or two files like enemies/elevator right now, but it's not a big deal. We should try as much as possible to find a more or less definitive layout now, since each git mv makes the git history super hard to read :)

bojidar-bg commented 8 years ago

Ok, refactor-move was merged, it is time to think what else should be moved :smile:

Current project structure (with notes)

Assets

In-game objects

Stages

User interface

Misc.

akien-mga commented 8 years ago

A question about the art/ folder, as I've played around with it a bit while creating https://github.com/KOBUGE-Games/jetpaca-assets-art:

Should we keep everything in art/, or move the assets to the folder of their corresponding scenes/scripts? And if we keep everything in art/, should we try to replicate a structure similar to the source repo and/or the current scenes file organisation?

bojidar-bg commented 8 years ago

Well, I have no definite decision on that one, there are problems in both cases:

So while I lean a bit in favour of the first, I'm not really sure if it would organise things at all.