Anyone for Collaboration?

[JGadrow]

Ok, I've tried to start this project several times now lol. I was nearly to an alpha build stage and I scrapped the entire thing because I noticed it was going to be a maintainability nightmare.

I began building an application framework using the MVC paradigm, however, after using some 'professional' CMS, I've already seen ways to improve on my little framework to make it much more powerful. Also, I'd not gotten around to any sort of administration tools.

So, I'm starting over... again. This project actually has a lot of interest already. Even before I had working screenshots and I never ended up with an alpha release, I had an active forum of people who were eagerly awaiting the alpha. Before cancelling, I put the question to them whether I should continue with the known issues or if they'd rather I just start over and notify them when it was ready. They unanimously voted for me to just let them know when it was ready. I had over 70 forum members, of which at least 30 were active.

I'd like to know if anyone would be interested in collaborating on coding the project. I'm thinking if I have someone else assisting, I'll stop my endless theorizing and just get the blasted thing finished! lol

I can't afford to pay, but I am hoping this will be the initial revenue generator for my company. At which point, if all went well, it could lead to a paying job or (if already employed) sideline employment on a contractual basis.

A few key points:

• Space Empire Game
• Object Oriented using LAMP server
• XHTML 1.0 Strict, CSS 2.1, XML 1.1, WCAG-AA

[codestryke]

Ok, I've tried to start this project several times now lol. I was nearly to an alpha build stage and I scrapped the entire thing because I noticed it was going to be a maintainability nightmare.

Not sure how "Object Oriented" you are going for but for pure OO and a web game you are going to get into a maintenance nightmare. Although there are times when pure OO works well they don't tend to work well when it comes to web games. The reason for this is because the web game itself is fairly singular (ie hit a page) rather then an entire application.

A few key points:

• Space Empire Game
• Object Oriented using LAMP server
• XHTML 1.0 Strict, CSS 2.1, XML 1.1, WCAG-AA

Are you really married to the idea of XML? Have you worked with XML and Javascript, it is, in a word, a nightmare. XML IMHO is way to wordy, you might want to look at using JSON instead as it seems to fit well with xfering game data more then XML is.

[Chris]

Ok, I've tried to start this project several times now lol. I was nearly to an alpha build stage and I scrapped the entire thing because I noticed it was going to be a maintainability nightmare.

Not sure how "Object Oriented" you are going for but for pure OO and a web game you are going to get into a maintenance nightmare. Although there are times when pure OO works well they don't tend to work well when it comes to web games. The reason for this is because the web game itself is fairly singular (ie hit a page) rather then an entire application.

I agree.


Do you have a working something of your game? Or any design doc? If you have any of these, show them, I might join (but it woukld be more for a company, do not count for any real coding from my side, just some random small bits from time to time).

[JGadrow]

I do like XML as it can be transferred between applications that do not utilized JavaScript. Also, I do not like to rely on a ton of JS. I utilize JS mainly for effect rather than functionality.

**EDIT: I should also note that I utilize XML only for flat file storage. Once it enters the program it is parsed into the relevant object.**

The reason OO doesn't work well for web is, just as codestyke said, the fact that you've got to parse through each of the class declarations and such on each page load. However, if you create the application as a PHP command-line application, you can run it as a background task and bind it to a network socket. Then, your web interface can simply translate the URL into a command which is passed to the 'real' application and awaits the output for display.

Thus, your application allocates needed memory only once and you also reap the benefit of a persistent database connection. You can even allocate database connections as an array and load balance if you're running in a multi-server environment (which I most certainly won't to start off).

As far as some of the design stuff, yeah, I have it and I'll post it later as I'm off to work. Thanks for your guys' input.