#12188 - RaBBi - Mon Nov 03, 2003 11:13 am
Hi everybody ^^
Because my gba project don't want to compile since yesterday, I take a break, and think about how to be more efficiently in developping it. :P
For now, I design what I want to add to this project, and then I (try to) code it.
And I work on till it works.
I know a best way is to design the whole project first, and then developp it in parts.
But I would like to know in what parts I may have to organize my developpement.
For example, I know that I must create the engine of the game first, but may I have to focus on maps then on sprites, or in the inverse way.
I'd like to have a simple plan to follow, a easiest-to-hardest plan, you know.
Thank you ^^
_________________
Sorry for my poor english, but it would be worst for you to understand me if I speak in my native language, French ^^
#12189 - yaustar - Mon Nov 03, 2003 12:49 pm
This my view and my experience that is telling me this:
If you are working as part of a team, then organisation is a key factor in keeping everything together. Working alone you can get away with a few things as you know when something has not been done / not working.
At the moment we have a task list in groups of milestones. We allocate each other tasks off that list in meetings ready to be done by the meeting.
Scheduling tasks is also important as it gives people incentive to get something no matter how hard/easy it is.
Just my thoughts, I have no idea how it works in the industry but you can read the postmortems at http://www.gamasutra.com (it is free to join)
_________________
[Blog] [Portfolio]
#12196 - RaBBi - Mon Nov 03, 2003 4:11 pm
ok,
I think I must reformulate my ask ^^
In fact, rather than compare to industry team organized project, I ask you, experimented people on gba dev, if there is a logical way for a beginner to have a easiest-to-hardest approach of this machine.
I don't talk about high level of organization but more on engine coding tasks.
For example, is it harder to experiment sprites collision or map management. (I take an random and simple example).
So, I ask this to schedule tasks that you told ;)
Thank you ^^
EDIT: I forgot to precise that for the moment I'm working alone on this project.
But a few teamates may join me soon.
So to guide them to not have a learning too strong, and to know what I can ask them to do (and what I cannot), I'd like to know what you consider as easy and as hard ^^
_________________
Sorry for my poor english, but it would be worst for you to understand me if I speak in my native language, French ^^
#12198 - yaustar - Mon Nov 03, 2003 4:54 pm
In that case, make sure you write EVERYTHING down, how the engine works, how the graphics loaded etc. It makes a whole load easier for your teamates to catch up on the project.
_________________
[Blog] [Portfolio]
#12603 - sgeos - Wed Nov 19, 2003 7:40 am
You may be asking something different, but this is how I have one of my projects organized, one file for each category:
Main Program Code
Utility Functions (Misc Stuff)
Map Grid Related Code
Stages
Input Related Code
Display Related Code
Every function should do one thing and do that thing well.
Every function should only do one thing.
You should be able to rewrite a funtion without making many (if any) other changes to the rest of your code.
If you need to change data types after you start a project, that may require a lot of code changes.
If your project is organized, you should be able to add things to it in more or less any order, so it does not matter how difficult any given component is to make.
-Brendan