READ THIS: I'm going to keep the summary of our progress and game concepts on this page: http://www.zeoxdesign.com/monday recommendations and suggestions are not only welcome, they're necessary! ;)

I think we should go with plot #1, btw.

To save time on deciding style rules, the group could use the Allegro Hacker's Guide.

For the coding standards, that's fine. I'm uncertain about how the indentation will work. The way I do it is two spaces for each new level of indentation, replacing any eight spaces in a row with a tab. I'm not sure if you can set Emacs to do anything else.

alright, that's 3 for the allegro hacker's standard... none opposed

Then we all have to read the Allegro Hacker's Guide! Actually, it was looking good for a minute,...

/* foobar:
 *  Description of what it does.
 */
void foobar(int foo, int bar)
{
    /* do some stuff */
}

...but I personally prefer to line up braces at the start of the indentation level (i.e. Nothing on a line before the braces, but single-line blocks can follow...). It makes it a lot easier to find missing braces and also makes the program structure clear.

if(foo)
{
    /* stuff */
}
else
{
    /* stuff */
}

Fixed.

do
{
    /* stuff */
}while(foo);

Fixed.

switch(foo)
{
case bar:
    /* stuff */
    break;
default:
    /* stuff */
    break;
}

Fixed.

I'm not really trying to start a flame war, so if the majority agree on the Allegro Hacker's Guide I won't fight it, but I think my recommendation is valid. The newlines add clarity. The spaces between a condition statement keyword and its condition generally don't, IMO (though spaces should be used inside the condition to make it readable and parenthesis should be used to make it clear).

if((condition1 && condition2) || (condition3))
{
    /* stuff */
}

// -- OR if conditions are long --

while((condition1 && condition2)
        || (condtion3))
{
    /* stuff */
}

And also, we would probably benefit from using a documentation system (i.e. Doxygen) standard in the comments.

Allegro hackers guide looks good. I'll set my IDE up for that.

What classes are we going to have? Maybe it's just a personal preference, but i prefer to have a complete object API before we begin coding, even if none of the structs are actually coded. I was thinking:

{
NPC

Map

grid-square

Main character
}

at least.

Okay, SVN is up and running. All I need to do now is add users basically.

The repository url is: http://svn.miquelfire.com/monday/
The url to change your password is: http://svn.miquelfire.com/svnadmin/?project=monday

For now, only Chris and Matt (as they're leaders of this project) can send me usernames to add (VIA PM), so bug them about getting access. Later (next weekend I hope), I'll allow them to just add and remove names themselves without having to wait for me.

Oh yea, they need to contact me for the usernames they want. And Chris, if their anyone else you want to allow to add/remove user access to SVN, just let me know.

- Source

I feel like I've gotten out of my league. The last page or two... so confused! Is there some non-programming position available, I still want to help, you guys are just way beyond my technical skill.

I nominate myself to work on the storyline! Any objections?