derouge

Wipe off the monitor and keyboard. I'm lame.

Below 30 credits is more lenient, or below 30 posts? It would make more sense, in my opinion, to be 30 posts since once you've got that many you've probably been here awhile and don't need easy credits .. but maybe my logic is wrong, wouldn't be the first time.

My younger brothers play (and love) it. I, however, could never get into it. It may be because I'm a Tibia addict (tibia.com) or possibly because the game is just too darn crowded! I mean, jeez, every 3 steps I take I'm walking on my next door neighbors feet. Annoying. I also find the graphics less than decent. It's sorta a forced 3d, in my opinion. Not a proffessional graphic set. But it's got some good points. I think. Uhh, free .. easy to learn, easy to play. A good time waster.

Definitely a valuable resource. I learned HTML from here, mostly through copy+pasting code and then twisting it into the forms I wanted. It seems to have gone much more .. commercial, though. I miss the old orange wavey side bar! But it's still got some of the highest quality tutorials out there - not only for HTML, but Java, ASP, and others!

Wow. I spent exactly 32.3 seconds viewing it and now have a pulsing headache. But, hey!, at least it's funny. Odd for sure. Someone should make a 15x15 pixel site and take the crown for world's smallest website. Muahhaha!

Make sure you have enough hosting credits. I was just trying to login a bit ago and hadn't realized that while out of town I used up the few credits I had built up. So, meh, make sure to pay close attention to that. It's a pretty easy thing to overlook if you're busy/out of town/whatever and come back to being minus credits.

MySQL is excellent .. fairly easy to learn and fits in perfectly with PHP. For web based stuff I'd definitely say MySQL. However, in the office I work at we do a lot of Access based database stuff. All our Order Management is done through that, and it works pretty well. I have a decent background in Visual Basic, which is what Access uses to write macros and whatnot, so that helps a lot. I think for commercial purposes Access is pretty slick, at least for small business.

The IFRAME pages I've done in PHP have been done pretty much exactly as described above. Works pretty good, too - the first option, anyways. Not so sure about the second. I might give that a try, too.

A nice introduction .. very useful. When learning a new programming language the simpler explanations, the better.

I'd have to agree with all the folks saying MySQL .. it just meshes so well with PHP, almost like they were made with each other in mind. Although, where I work everything is in MS Access, which I have found quite easy to learn and manage. I just think for freeform Web Design PHP+MySQL is awesome.

My thoughts on the two are as follows: ASP is supported, obviously, by Microsoft. Fully supported. This is Microsoft's answer to PHP. Therefore you get much, much, better support from the big boys. There is an entire dedicated community on the MSDN. Another good piece of ASP is that if you have any prior knowledge of Visual Basic (or just BASIC) you'll find this language a snap. It is, essentially, a web-based Visual Basic. That was my thougt anyways. PHP is freeform .. it's not done by some big company motivated only by profits. PHP is much more customizable, much more open. It also, in my opinion, is much better for web site projects. Although to be honest, it's a pain in the butt to install on a computer. I spent quite some time getting it rigged up and running with Apache, compared to the 10 minutes or so it took me to download ASP.NET and have that up and running. The winner? I'd say go with PHP. Why? Not exactly sure, maybe I'm just not a MS fan.

The planning on paper stage is sooo critical, I can't even stress how useful that is. To just go ahead and start sticking links here and there without any planned idea of where they are is just a horrible idea. I'll always sketch my page out first, and then include detailed labels of whats going to go there, the type of thingy (IFRAME, Table, Image, etc.) until I have the entire page planned out. Then I go to doing a rough outline in HTML. I'll code the page, using colors to denote certain things. For example, the last project I worked on had a central IFRAME in a table, surrounded by links across the top. I needed a certain part of the table to have a background, so those areas I filled with red. Other areas needed a different background textures, so I filled those with green. When it came time to actually produce the page, backgrounds included, I just replaced the BGCOLOR="" tags with BACKGROUND="" tags. Another bit of info to consider when laying out your page is the visitor's view. Test in different browsers, different screen sizes. I always include a splash page explaining how the page is best viewed. (800x600 in IE 6.0+) or something along those lines. Another tip is to use percentage values rather than pixel values. This will help reduce the vast differences users get when they view the page with a different screen size.Anyways, great tutorial! The SLIP method is the way to go.

Excellent information. I've always sort of wondered if there was some official legal process that I had to endure in order to stick that neat little "C" at the bottom of my pages. Neverseen, you suggested sending yourself an envelope to serve as proof .. so for a webpage you'd recommend printing the source code and mailing that to yourself? Would that stand up as well?