Journal FortKnox's Journal: Yargh... updates, newsite, etc... 18
Yargh! I've finished through the busy-ness of last week, and have time to finally get back going on the new site. Thanks for waiting patiently (Are we there yet?) ;-)
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.
Any opinions/suggestions??
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.
Any opinions/suggestions??
mod_rewrite (Score:2)
for what its worth (Score:2)
Re:for what its worth (Score:2)
Re: (Score:2)
I'd vote for Struts... (Score:2)
Hey. (Score:2)
Um, also...nothing about Doom 3 will be a "quick demo". Sheeeiizzznit, it is a hog. But it's scary as hell and somewhat fun to play. I have a 2.8Ghz with only 1/2 Gb of RAM and a GeForce 5600Ti and I have to way turn down the settings to not be choppy. That Geforce isn't too shabby either.
Oh well
Re:Hey. (Score:2)
Definitely Struts (Score:2)
You know, 'cause I have so much free time, and 'cause my hubby just loves it when I volunteer for geek projects in my spare time...
(-:
Pixie
Struts!!! And stuff (Score:2)
If we go with some new tech, then there will be a learning curve, and we will make msitakes (ha!). Just because something is "old," this doesn't mean it is obsolete. It could mean that it is mature, right? :)
When you get your list of requirements, let's take a minute and rank them. "Must Have" "Should have" "Nice to have" and that's the implementation order. For example, spell check would be gee-nifty, but it is a NTH, so it is go
Re:Struts!!! And stuff (Score:2)
What are the features of the new site? (Score:2)
Struts (Score:2)
The Slashdot "Powers"-That-Be are scared... (Score:2)
Notice how the first guy that replies to me is totally off-topic when he starts moaning that I should either like it or lump it or go make my own site. And notice how he doesn't receive a single moderation for wandering off-topic.
Then look at my reply to his comment, where I point out to him that collaborative work on a viable alternative to Slashdot is already gaining momentum. That post is moderated, all the way down from +2 to -1.
In fact, it's the onl
Features... (Score:2)
Threaded comments are probably an obvious one but something most blogs don't support-- one of the biggest advantages /. has over blogs.
RSS support would be good, but the problem with RSS is that being in an RSS app puts you
Re:Features... (Score:2)
And, as far as Java goes, it isn't an applet, it'll be JSPs. As long as you have a browser at work, you'll be able to hit the site without trouble.
Re:Features... (Score:2)
Excellent news about the JSPs... Java is one technology I know nothing about, so forgive my ignorance.
Quick suggestion (Score:2)
You should be able to nullify the effects of certain moderations. For example, if I don't want -1 Offtopic to affect the rating on comments, I should be able to do that. Or if I don't want +1 Funny to affect ratings, I should be able to do that.
Right now, I'd have to set "Offtopic" to a universal bonus of something. Not all offtopic comments are good - I only want to see positively moderate