Triple-B: Yes, the plan is to fully automate WCTO so we can play over the internet without ironduke having to roll dice. (We already play over the 'net, but we do it by email right now). As for an AI.. I have no plans currently for that; AI coding is a whole field to itself.. but maybe one day. It certainly won't be out at launch.
As for the menu, it's a really nice feature, but for the games itself, I'd either speed it up a bit or make an option that allows disabling it. When you have to check more ships in a short time, it can get a little annoying.
There's a little issue with the form though, how do you handle the cap ships? I mean, they have as much as 4 digit hull strenght and their turn rate and acceleration are below 1. (so far I see that the form can accept two digits at most)
And I've entered a Broadsword and an Epee, so please check if they're the way you want them to be. ;-)
I mean, it's nice as a show-off, but can be annoying if you have to use it frequently (an example comes to mind, if you have ever played Privateer 2, the loading times and animations on the PAD were horrible.)
There's also the question of less-than-one values, how do you want them written, 1/3 or 0.3? Or even somehow else?
You might re-think this at some point, writing halfway-decent AI Scripting (especially in PHP) is not as difficult as you might think it is. I wouldn't do it by launch but down the line it's as simple as making a ship move in one of two directions (towards the target or away from the target) and making it attack when necessary.
Okay, looks like we're missing the astronomical budget and a failed marriage so far. Anyone care to help?It takes five years, three artists, an astronomical budget, and a failed marriage to build a successful browser based PHP/AJAX game.
Presto and KHTML are two other layout engines you might want to consider. Although I'll grant that Trident, Gecko and WebKit will cover the vast majority of the Internet population, you can't really say that Gecko and WebKit cover 'anything but Internet Explorer'.I am only designing for mozilla or webkit enabled systems at the moment (i.e. anything but internet explorer).
From what I understand (which may not be necessarily accurate, I'll admit), IE7+ will correctly render PNGs with transparency. IE only falls over when PNGs include gamma/colour correction.IE apparently has issues rendering PNG's properly, not sure if you're using those or not.
They did in the past, but since IE7, they've actually made some good progress in the direction of standards compliance. Trident is still far, far behind the other major browser engines, but you can't really say Microsoft refuses to adopt web standards any more.It's important to remember when developing browsers that IE and Microsoft by extension refuse to adopt the web standards.
And since the majority of the Internet use IE, the standard practice is to write according to web standards first, then selectively patch for IE.So code that works perfectly and looks perfectly fine in every other browser on the market just isn't going to work in IE. It's unfortunate, and frustrating.
Presto and KHTML are two other layout engines you might want to consider. Although I'll grant that Trident, Gecko and WebKit will cover the vast majority of the Internet population, you can't really say that Gecko and WebKit cover 'anything but Internet Explorer'.
Even if you choose to only check Trident, Gecko and WebKit, that's still a lot of work.
This is definitely an issue. I put in the fonts you used previously, but then I don't actually have said fonts, and so I did the formatting for the other fonts, in truth. I suspect the screenshots you see out there are because others are seeing it the way I am. For the time being, I've now removed the references to 'space gothic' and 'lady ice' so that everyone sees it how I do.Re the browser issue: I'm currently running Firefox 3.6.7. So the explanation lies in the fact that you have to have the font installed on your system... I've installed Lady Ice, but not Space Gothic, which is why it's messing things up here. I'm attaching a screenshot for you to see what I mean. (Lady Ice is much more narrow than the rest, so this is probably why it's screwing up the layout.)
I noticed that - in Jason_Ryock's screens as well (thanks for your feedback!) - the ship name, ship class and weapon loadout are in Times, while the rest of the stuff seems to be in Verdana. (That's why I assumed you were drawing all the Times parts from variables.)
Sounds good. I can size-down the 3D picts, or we could make *those* part of the background, or any number of things. that said, once I'm done prototyping all the windows I need, I plan to push forward and finish phase 3, and then move onto the harder (but more interesting to me) phase 4. I would, in such a case, come back and revisit these windows later. (For that matter, I can release all the available divs/classes currently in use here on the forum, and you guys can take a cut at laying it out differently. As long as the core divs don't change and only the CSS, the php doing the output won't care and I wouldn't need to do a code change)Generally speaking, I liked the Game 005 info size much, much more, but I don't want to lose the "3D" ship pics either. So maybe we can leave the general font size the way it is (and reduce the size for ship name, class and player name, along with a smaller Confed/Kilrathi logo) and just use the available space more efficiently. I think I'll try different layouts and send them your way asap.
By the way, would it be better to have the gradient background as a png?
Um, sure. I'll do that in a few minutes, with the current phase progress and all the demos.Another thought: Since we're getting a lot of links in this thread, why don't you create a thread where you collect them all? At least those you want to keep, like the ship entry form and the most recent demos. I could just sticky it then.
It looks terrible in IE, which I am not surprised by. IE apparently has issues rendering PNG's properly, not sure if you're using those or not. I'm using IE 8, 64-bit on a Win7 OS just so you know.
It's important to remember when developing browsers that IE and Microsoft by extension refuse to adopt the web standards. So code that works perfectly and looks perfectly fine in every other browser on the market just isn't going to work in IE. It's unfortunate, and frustrating.