Anywho, the return of Joey has come, and he's terribly spoiled. So the wife is spending the day breaking him down and getting him back on his reg schedule. Hopefully he'll go to sleep at 8 like he normally does tonight. I plan on giving Doom3 a quick demo, and checking out the first couple series of the Broncos/Redskins game (FOOTBALL! WHOOOO!!!). Then I'll type out all the requirements I've documented. For those that want to help out, requirements are just what they sound like... stuff that you want in the app. Not in a specific sense, but get your idea across. When the usecases come around, they'll get more into specifics. I need everyone to read them when they come up, and ask questions on it, and suggest new ones, and make sure its everything we want. Making the use cases based on them shouldn't be too tough. After that, we code.
So, things should start rolling this week, but don't expect to 'play' with a beta version for quite a while (probably a month at the very least). So we have to be patient and stay the course (I feel like a politician).
Oh, and for coders, I'm starting to reconsider the front end... I planned on Tapestry, but am still considering struts.
With tapestry, its much more OOP and reusable, but the URLs will be all whacked, so you won't be able to bookmark anything (well, bookmark in your browser), and there will be a learning curve, because I'm no expert at it.
Struts isn't as reusable (and its considered 'old' in the webapp world, already), but I AM an expert on it, and know its strengths and limitations.