And we’re back with part 3 of our incredible CI tutorial. In part 1, we installed and configured CodeIgniter. In part 2, we took a basic look at how CodeIgniter handles the MVC architecture. Now we’ll check out CodeIgniter’s database handling including the Active Record implementation, performing simple CRUD (Create, Read, Update, Delete) operations, and sending query data from models to controllers to views.
Welcome back. In the last section we got up and running with CodeIgniter and familiarized ourselves with the structure and installation of it. This time, we’re going to take a closer look at how CodeIgniter handles MVC, and what MVC really even means!
This is the meat of CodeIgniter and most other web application frameworks (Symfony, Zend, CakePHP, and even the infamous Ruby on Rails). It’s also a really great way to structure any kind of application, and you’ll feel like a better person for having learned it. And it’s good in bed. Moving on…
CodeIgniter is an “Open Source Web Application Framework that helps you write kick-ass PHP programs.” The website says it all. CodeIgniter is BALLER. However, it’s documentation is awesome after you get going, but getting going is a little tougher. That’s what I’m here for. Hopefully, after this tutorial, you’ll know your way around CodeIgniter and have a pretty good feel for the MVC architecture.
In part one, we’re going to learn about installation and configuration of CI, and also get a feel for the folder structure (which always seems to scare people away). So let’s get going!
For a project we’ve been working on, I recently had to implement a calendar in PHP to show upcoming events. The solution was a wee bit tricky (and pretty annoying), so here it is in all it’s glory, in case someone else is looking. It’s pretty easily skinnable, and very scalable, so it should fit in nicely with your project.