From my personal, non-affiliated perspective, yes, you should. It will save you hours of going back and forth on the forum. The worst that can happen is that someone will have to revert the changes—nothing serious.

Personally, I think one of your biggest goals should be working towards the point where each developer doesn't need his own branch. Of course, I'm not participating

I think it's positive that we work in branches. Though for really small tasks you can work in trunk, as long as you don't have to commit half done work.

I STILL get the strange segfault error on the lappy! It's not the allegro libs, as I have compiled them again to make sure. Both systems I've tested on where x86_64 openSUSE 11, both with the same SVN of allegro (latest), both are AMD chips...the only major difference (besides lappy vs desktop), being nVidia on the desktop and ATI on the lappy. Doesn't show any graphical errors though...???
I've got a collect of game tiles and sprites here from various places...I will upload them to the SVN later.8-)

Quick question: Is the game suppose to allow us to play the "demo" map yet? I remember being able to before, but I can't get past the menu system anymore...Just will not do it!???

wait wate w8 what?!

Oates! I need tiles!

Ok I committed a little fix to make that menu option work.
The menus are gonna change completely when Matt gets Ma5king running, I think.

Oh, and is that a Monday folder I'm seeing under your branch? It's getting really weird.

Wow, off the front page. To the top with you!

For my part, I've pretty much finalized the plot progression, and actually drew up the final dungeon layout, among other stuff. Problem is it's all in a notebook I've been writing in in my spare time and I don't feel like typing out 20 pages of notes just yet, so once the game has reached "playable" I'll compile it all into The Final Script and the responsibility for doing work will shift off the programmers and onto us content guys. Let's make sure the basic engine is playable for everyone, bug free, and can handle some basic gameplay and in-game cinema correctly.

I don't get the segfault on my desktop running opensuse 11...but I do on the laptop running opensuse 11, both have EXACTLY the same version of allegro. Desktop is nVidia, laptop is ATI. What GFX card do you have? I wonder if it doesn't have something to do with allegro's openGL interface with ATI's gl driver.

Those errors you posted about (about the entity...I have them corrected in my branch I am working on here...but have been busy TRYING to compile allegro for windows ) I will most likely boot into Linux later this evening and take a look and fix the trunk...:)

So...another ATI chipset with segfaults. Anyone else confirm my suspensions?:D

Edit:
To OnlineCop:
Any suggestions on how to actually get allegro compiled under windows? I have mingw and visual studio 9...I would prefer visual studio 9, but at this point...I don't give a damn...just to have a windows version so I can do some tests of Monday in windows.::)
This is my current visual studio attempt.

Thanks, I've managed to hack it together somewhat...just need to get a a5_ttf.dll and I'll be able to run the "Monday" project.

Edit: never mind...it's static built only, which means no dll's...

Back on track:
I've fixed the trunk, so it compiles cleanly with the changes. Also, doing debugging, I've noticed:

/bin/sh: line 1: 26686 Segmentation fault      /home/donald/Desktop/Programming/Monday/debug/./src/monday
// first frame is:
/usr/X11R6/lib64/libGL.so.1  // What is causing the segfault...it seems to only happen with an ATI chipset.

Don Freeman: Your commits o svn lacks commenting. It would be nice to get a hint at what you've done without having to do compares.

Of all the programmers [thinking about] working on the Monday project, what is the biggest bottleneck? For me, my only bottleneck with the project (besides day-to-day time constraints) is actually the allegro5 library. Other than that, I'm still all gung-ho about the project.

I just keep fighting with allegro5 and all of the unexplainable segfaults that I get when I try to compile and run it.

Leaders (23yrold3yrold, Matt Smith, Trezker, etc.), should I assume that all of you are able to get it running without problems with allegro5? Or are you having problems too?

I seem to have the leas problems of all, which kinda sucks, I think the lead programmer should have the mos problems so he knows what needs fixin'.

I don't think Matt has much problems either...

There is one segfault I know of, but it's just when I shut the program down so it's not critical, and I have a strong suspicion of where it is. I think I introduced it myself when I refactored my entity and container stuff.

Don Freeman is doing some good work with null checks and such, though he's not using asserts, I think it would not hurt to make errors shout a little louder. We do have a pretty nice assert macro in Debug.h.

Oh, and I have started working on collision code.

As for the state of the project. I think people could start making maps and scripts to test it (if you can get it to build and run). The two .lua files demonstrate all available functions I think, though not properly documented. I should write some documentation on that...

CGamesPlay: Too late, we already got a working map, his system was scrapped. It was far from functional as it was.

We're only missing collision, and fancy features.