I know building a javascript fueled image gallery isn't exactly original, but I wanted an excuse to play around with jQuery a bit more. You can see the result here, which hopefully shows up in IE7.

I'm not really that thrilled with paying for another copy of Windows, when I have an XP disk and Parallels lying around. If only I could find the license for it...

I collected a bit of information from mod_rewrite "fun" over the years at stackoverflow, but then figured I'd post it here too, since I've been a bit lax about writing. Don't worry though (because I know you are), I have a few things in the pipes, including the next article in our MVC bare bones framework series, and my take on a drupal based image gallery.

I was excited to find out my pretend best friend plays dodgeball too. Of course, in our pretend life we both play, but it's always good when real life overlaps pretend life too. The easy thing to do at this point is to write me off as crazy, but I think you should read on a bit before coming to that conclusion.

As promised, we'll take a complete tour through the process of building a bare bones MVC framework in PHP. The goal of this series of articles is to explain MVC principles and design patterns in a useful way. This information is aimed at PHP programmers who are familiar with object oriented PHP, and have heard of, or poked around frameworks, MVC basics, and other design patterns, but are unsure how it all ties together. With all that out of the way, let's start with examining the concepts we'll cover.

Design patterns we'll cover in this introduction:

So that shiny new macbook the SO was so breathlessly waiting for? It lasted a whole 10 minutes before choking on itself. All that anticipation for a slender, eye-catching doorstop.

It was about time to put on a fresh coat of paint on the site, seeing as the old style was just some theme I found. Unfortunately, I really hate design. Well, to be fair, I really enjoy design, I just hate doing it. When it comes down to it, I'm really not that great at it, and the simplest of tasks end up taking a long time, or not looking the way I want it to.

Yes, I realize the title makes absolutely no sense, but really, you should be used to that by now.

Pagination (Node) has a new release (6.x-1.2), and you can read all about the fun additions there.

I've put my Pagination (Node) module up on drupal, and am looking to tackle two issues/features associated with it.

1 based paging

Currently, drupal pagination is 0 based, in that the URL will show "?page=1" for the link to page 2, "?page=2" for page 3, and etc. In the greater scheme of life, liberty, apple pie, and hockey, it's a pretty minor point, but it seems odd that the paging scheme ends up being "incorrect".

Pagination (Node) allows the main content of arbitrary node types (Page, Story, etc...) to be paginated according to one of two methods:

Method 1: Content is paginated by a selectable "words per page" count.
Method 2: Content is paginated by manual breaks, inserted by the content creator.

I've given ardarvin the first version of the buildering guidebook module. There's still some touch up features I'd like to add to polish it off, but it should serve our basic needs well. I'll post a link to it as soon as it actually goes up, and add it to the Random Code section for those interested in poking around.