Composer now supports PSR-4

Posted 2014-01-03
Category PHP
I haven't really posted about PSR-4 here, but if you follow me on Twitter or hang out on Reddit you've probably seen some news about it. PSR-4 was voted in as an "accepted" PSR by the FIG in December. It took a little while to get done and went through a series of painful rewrites but when we have in the end is a document that reflects what this truly is: an improvement on PSR-0. Time to upgrade your packages, but don't release them just yet.

Read More »

The Tribal Framework Mindset

The PHP community has made some amazing leaps forward in the last few years, but some folks still (intentionally, or unintentionally) are contributing towards the siloing of the PHP community into framework-specific sub-sections. We used to work that was for a handful of reasons, but with Composer, the FIG and the onset of PSR's we have literally no reason to do this anymore. This article hopes to point out some of the ways in which that can happen, with potential solutions too.

Read More »

Composer and PSR-0: Friends, Not Relatives

Posted 2013-05-07
Category PHP
As a huge proponent of Composer, a happy user of PSR-0 and a voting member on the PHP-FIG I get into plenty of conversations about all of them, and it worries me how much confusion there is in the community about these things not actually being related. To many of you this will be preaching to the choir, but this will hopefully clear a few things up for many or at the very least be a handy resource to link people to when they show signs of getting confused between the two.

Read More »

Testing and Contributing with Composer Packages

Posted 2013-05-01
Category PHP
While Composer has been around for a while now, many packages are still in their infancy (< 1.0) or sometimes are just not as feature filled as they could be. Pull requests are going to be a common thing for the PHP community to be doing to these packages and this needs to be done safely, with unit-testing. So, how do you run their test suite and add your own tests?

Read More »

5 Things CodeIgniter Cannot Do (without a rewrite)

CodeIgniter was build a long time ago and since its inception it has maintained the same API, without making sizable breaking changes through 3 major versions. Sadly, the API is at a point where it needs to be rewritten to support several fundamental features, which most other frameworks support. This is a walk through those features with a little insight as to what why and how from an ex core contributor.

Read More »

Package Watch: Image Management

Posted 2012-09-19
Category PHP
For years I was locked into using the same frameworks for everything, mainly because my clients were hiring me specifically to use CodeIgniter based on my reputation within the community.  Now that is not the case and I can build things however I damn well like, so I am doing it properly and that is using Composer. I tweeted about some useful libraries I found, so here is what they are with an explanation of the approach and why I used it.

Read More »

Moving On

My entire career seems to have come from being a CodeIgniter developer, and a vocal one at that. Since then I have risen up through the ranks of CodeIgniter developers to be active in maintaining it, but with my new job I just don't need to be on the team anymore. PHP 5.2 is finally dead to me, and as such I do not need to be part of a framework which focuses of PHP 5.2 compatability! It's not just CodeIgniter though, I am dropping as many of my responsibilities as I can to make way for an exciting [secret] new job.

Read More »

Laravel is Awesome

Posted 2012-05-22
Category PHP
You might not expect to hear that from a CodeIgniter and FuelPHP developer, but it's true. Taylor has done a brilliant job writing code that is clean, functional and has built a huge community of smart developers in less than a year of active development. People are flooding to Laravel from other frameworks and that's great for the PHP community, read on to find out why.

Read More »

Composer with CodeIgniter

Composer is the best thing for PHP since sliced arrays and using it in your applications means you have easy access to a large selection of well written PHP packages that plug and play with any framework that supports PSR-0 namespacing. This is BRILLIANT as it means less reliablity on the framework and framework-specific code, and helps you get towards the goal of portable code where the framework is essentially just the wrapper. FuelPHP will support Composer packages out of the box as does Symfony2 and I hear Drupal are working it in too. This interoperability is brilliant, but how do you use it with CodeIgniter?

Read More »