if you've already read the two installments that precede this one, it's probable that you're familiar with the inner workings of this sample ORM. In those chapters I implemented the ORM's data access and mapping layers, along with a simple domain model. To be frank, the development of this last tier is entirely optional; however, it's useful for demonstrating the ORM's actual functionality in the deployment of a blog program, which naturally will handle some "typical" domain objects, namely blog entries, comments and authors.

They share the code for creating proxy objects and, using a "poor man's dependency injection container" made from a factory method, interfaces and service classes to handle the results.

Funkatron was kind enough to put together a blog post about building a Tumblelog with Gimme Bar and PHP so I told him I would write up what I did on my own blog. One of my intents was to use the Gimme Bar API to pull in a list of my latest Gimmies for the sidebar on this blog. Ed had posted a very simple example in Javascript (I cannot remember where it is) so I took it and ran with it to modify it to work with the blogging software used here.

He includes the simple javascript, about 15 lines of it, that pulls the latest "gimmies" from his own feed and posting them as sidebar items (as you can see right next to the code snippet).It uses a combination of Ender.js, Reqwest, Underscore and regular javascript to get the job done.

One of the coolest things about working on Gimme Bar has been the opportunity to build a platform. While most folks interact with our service via the web site, the site is just one application built on top of the Gimme Bar content collection and curation system. Our web site interacts with the system via our HTTP API, which is open to everyone, not just our internal team. That means that anyone can build applications on top of our platform to suit their own needs or interests.

This simple blog (demo here grabs items from his Gimmie Bar feed and posts them. He includes complete installation instructions and a brief overview of how the parts work together.

This is the second article in a two part series in which I show you how to create a photo blog that is updated from your mobile device. Part 1 laid out the plan for building the application, set up the database requirements, and introduced you to some user contributed functions from the PHP manual which make it easy to retrieve messages from a POP3 mail server. In this installment I show you how to bring everything together so you can start photo-blogging on the go.

In this new tutorial they include the code to authenticate against the database, insert the email details into the tables and inserting the formatted results into blog posts. It's finished off with the code to pull out the latest entries and display them along with their matching photos.

This is the first article in a two-part series in which I will show you how to create a photo blog as part of your personal website which you can update from your phone simply by sending an email. You'll write a script to check the inbox of an email account for new messages using POP3; the script will extract the messages' subject line, body text, and attachments and update a database accordingly. You can then pull the information from the database for display on your blog, in a sidebar, or however else you see fit.

The start with some of the security considerations you'll need to keep in mind when creating a script like this depending on how open you want it to be (like filtering based on the "From" email or sending an approval message before posting). Included in the post is the SQL to create their basic tables for posts, image details and the pending items. There's also a PHP class (POP3) that makes an IMAP connection to a remote server, authenticates as your account and fetches the latest messages along with their attachments. These are pulled with a quick script and displayed via a foreach.

Part two will get into more of the integration of the images and the approval technique prior to posting the images.

The tutorial walks you through all the steps you'll need:

• setting up the environment
• creating a site skeleton
• making the blog posts model (with the CRUD generator)
• make the main page to display the latest posts
• adding comments
• creating a page for each posts's detail
• and the comments view

If you'd like to just skip to the end, you can download the source here.

Given the scale of how client-side technologies (such as JavaScript) evolved, most of dynamic functionality can be implemented using client-side scripts + remote web-services (e.g. Disqus for comments). More than often we a going down that road even on our completely dynamic sites - it makes things more simple.

He gives the example of being able to write the content in VIM and run a single application - Phrozn - and generate the new page to add to the site. He sees it as a good alternative to something like WordPress where most people only use 1% of the functionality it offers. You can find out more about the project by looking into its documentation or you can just dive into the code by grabbing it from github. As a side note, several other tools, like Jekyll are "blog aware" and can be used similarly.

Most conversation has moved from blogs to Twitter, and although Twitter is more active than blogs ever were, there are fewer quality conversations and debates taking place as a result of this transition. I'm hoping you'll join me in a blog revival.

He suggests that, during the month of March, bloggers band together and write more posts and make more comments than usual to bring out that good content that Twitter loses in it's 140 characters. He shares a few suggestions of the steps to take to join in - write the post, pledge to write more the rest of the month and point out your entry on twitter.

Several members of the PHP community have already posted their "Ideas of March" posts:

• Lorna Mitchell
• Chris Cornutt
• Stefan Koopmanschap
• Jason Lotito
• Jose da Silva
• Sean Coates
• Paul Jones
• Elizabeth Naramore
• Steve Rydz
• Rich Bowen
• Harry Roberts
• David Rhoden
• Drew McLellan
• Anthony Killeen
• Elizabeth Smith
• Rafael Dohms
• Nicholas Sloan
• Stuart Herbert
• Anthony Gentile
• Cameron Koczon
• Joel Perras
• Rick Hurst
• Court Ewing
• Robert Basic
• Matthew Weier O'Phinney
• Chris Hartjes
• Antonios Pavlakis
• Kevin Schroeder
• Nate Abele
• Web Standardistas
• Joe Constant
• Phil Norton
• Vid Luther
• Jason Sweat
• Alan Colville

If you've written your own "Ideas of March" blog post, let us know and we'll add it!

If you want to develop a blog from sctrach without using any CMS like WordPress or Drupal, then you've come at the right place! In this series, we will understand how to develop a blog using the CakePHP framework. So, why CakePHP? CakePHP is a robust PHP Framework having an extensive community and excellent documentation. It's based on the MVC pattern, which makes it really simple to use.

This first part of the series focuses on helping you get CakePHP installed and running on your platform.

I have given up on feed readers. I never did like them much to begin with and have found over the past couple of years that twitter does a better job of showing me interesting blog posts than Google Reader ever did. In addition to recommendations from friends however, there are a hand full of accounts that I follow to keep up with what is going on.

Here's his list of the five accounts to follow:

• @phpdeveloper (yup, that's us!)
• @planetphp
• @weierophinney (Matthew Weier O'Phinney)
• @phpc
• @phpcamp