design patterns

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:

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 ran into a few snags while playing around with codeigniter. The first was the realization that it was actually a subset of the work that was originally pmachine.

Now perhaps I'm being slightly unfair, since I didn't have a lot of hands on experience back in the day, but from my role as a sys admin for a web hosting company, pmachine was the early candidate for "ugh, yet another security hole", and whenever I hear that word I cringe at the awful memories.

This is some pretty ancient code by web standards. However, it was used for a a decent amount of projects, including my early stabs at a community portal for my North American friends while I was living in Australia.

It handles basic CRUD operations without much hassle, and I built a helpdesk around this codebase as well. Unfortunately I haven't been able to keep up with the contact in the company the helpdesk was used at, so I'm unsure how well it eventually scaled.

First off, an example of it's usage: