Log in

No account? Create an account
Previous Entry Share Next Entry
(no subject)
I'm working on the layout, but I thought I'd put some content there first, in order to build stuff around it. So, a few reviews...

Sum 41 - All Killer No Filler
Lifehouse - No Name Face (special edition)
The Offspring - Conspiracy of One
Blink 182 - Take off your Pants and Jacket

Now to work on making it more PHP-like, and use that in order to pull of some fun tricks :o)

  • 1
Heh, nothing like seeing a website an knowing how it's put together :D

I take it it's an:
<? include ("bottom.php") ?>
<td class="foreground">

<h6 class="title">Take Off Your Pants and Jacket</h6>
<h6 class="artist">Blink 182</h6>
<? include ("top.php") ?>

job. Nice HTML, none of the wysiwyg crap, and proper CSS.

I wanna see some interactve database stuff going on, with users an stuff. Drop and give me 20.

Yup, that's almost exactly how I did it - the (td class="foreground") part is in the top include, but otherwise, yup. That way, I can change the whole layout easily enough without editing more than one file. Of course, ultimately, it'll be more like this

The URL will be like this: review.php?revid=312

Then you'll have something like

<h6 class="title"<<?php echo $title[the argument up there that says 312]; ?< etc.

However, it's a bit slow - learning PHP is easy enough, except that I learned ASP first, and I keep having to check that I'm writing code in the right language. At first, I'm thinking of just storing a massive set of arrays server-side, and letting the parser put in the relevant data (as in the example above), but ultimately it's going to be running on a MySQL server...

Thanks for the kind words regarding the use of CSS and stuff - I'm trying my best. Now to actually put some nice stuff on there so it's not just a couple of plain boxes :o)

Wow, I forgot how to write >'s there for a minute ;o)


I'd recommend going for the DB option as soon as possible, makes life much easier in the long run. The thing I hate though is making the urls look nice. /review.php?id=23 is always gonna look kinda sucky.

Best to create a php file called just "reviews", mark it explicitly as a file to be put through the PHP server, then after sufficient blood sweat and tears you can have it accept variables like $band == GreenDay from /users/band/GreenDay. Which is mucho nicer.

Yeah, I'm not sure about that either, although then again, there's an easy way of fixing it - change links on the site for forms, whose action is review.php, that pass in the relevant arguments. That way, it'd do that, but you'd never see it. Then again, it means that external links to the site would have to take that form anyway...

I could do that, yes, which is probably where it's heading in the long run, but I can only deal with one change at a time right now, and I'd rather get the DB up and running before I try worrying too much about aesthetics :o)

  • 1