esocyn

I'm trying to set up a web database that archives electronica bands. It's going to be just like how www.metal-archives.com operates. So far, all I have is the menu, the main page and I've strung them together via PHP.

I've got what I have so far uploaded onto Tripod; http://esocyn.tripod.com/EncycElectroEnter.htm

Nevermind the ads, once I get finished with it, i'm going to set it up on a good ad-free server.

What I need help with is how do I set up MySQL and start documenting .css pages (The band archives pages, member pages etc.)?

DaWei

The information you impart is pretty sparse. About all I can say is that I wouldn't recommend having an "ENTER" link on your first page. Do you have MySql installed? Exactly what is your platform? Can you replicate it on your personal system, or will you be developing on your server? I might suggest that you drop into the C forum just to read the "How to post" thread. Information is critical to a decent response except on those days our crystals aren't in the shop for "ball" joints.

__________________
Abstraction doesn't make it impossible to write bad code; it makes it possible to write superior code.
Contributor's Corner: Grumpy on C++ Exceptions DaWei on Pointers

esocyn

1. Yes, MySQL is installed.

2. Windows XP Home

3. Right now, I'm developing on my personal computer... but I hope one of my friends will partition a few MBs to me temporarily so I can develop it there.

DaWei

Okay, at this point you need to get the MySQL up and running. Just follow the installation instructions. You still don't say anything about the kind of server you have, so I'll just bust right ahead. Personally, I'd install a WAMP mix of some kind. That would be Windows/Apache/MySQL/PHP. Add to the mix phpMyAdmin if you don't have any MySQL experience. I'd add it even if you DO have the experience. It'll allow you to deal with the database in an administrative capacity without having to know too much SQL right away. If you have any DB design experience with front ends, such as you'd get with Access or Paradox, you might want to design your database that way then transfer the table set you come up with to MySQL. That'll give you a leg up.

Once you're there, there's just nothing for it but to bite the bullet. DESIGN YOUR APPLICATION BEFORE YOU BEGIN TO CODE. If you don't do that, you get to do it over several times. Once you know WHAT you're going to do, in terms of flow charts or pseudo-code or whatever design medium you choose, start in. Write from top down to begin with, stubbing as necessary to get enough to tell if you like the pages you see. When you can't get by with stubs, switch to bottom-up for a while.

You're statement, "documenting .css pages", throws me. That's not the same thing as writing .css pages. If you're just now getting into all this, you have some work cut out for you. You know the old saying, "Anyone can make a web site." That's a true statement. Only a few, however, can design and make a GOOD web site. Anyone can make a blivet. (A blivet is 10 pounds of excrement in a 5 pound bag, if you're unfamiliar with the term.)

__________________
Abstraction doesn't make it impossible to write bad code; it makes it possible to write superior code.
Contributor's Corner: Grumpy on C++ Exceptions DaWei on Pointers