• audetpascale/silex-crowdin-provider (0.0.1, 0.0.0) Silex Provider to use Crowdin.
  
  
• brown-paper-tickets/bpt-api (v0.11.1) A library for interacting with the Brown Paper Tickets API
  
  

The NetTuts.com site has continued their series looking at design patterns and how they can be used in PHP. In this new post they focus in on the Decorator pattern, most commonly used to add functionality to a existing class (to "decorate" it).

Earlier in this series we explored both the facade and adapter design patterns in this series. Using facade, we can simplify large systems, and by implementing adapter we can stay safe while working with external API and classes. Now we are going to cover the decorator design pattern, which also falls under the category of structural patterns. We can use the decorator pattern when we just want to give some added responsibility to our base class. This design pattern is a great alternative to a sub‑classing feature for extending functionality with some added advantages.

They start with a problem that needs solving - sending an email with additional content not defined in the parent class. They show how to do something similar with child classes, but quickly find a limitation. Instead, they show how to use decorator classes and a simple interface to provide interchangeable classes that augment the contents of the email body as passed in via constructor injection.

The Zend Framework project has a new post to their blog today officially announcing the roadmap for version three of the popular PHP framework.

The most often-asked questions we get around the Zend Framework project include: Where is Zend Framework heading? When will Zend Framework 3 be released? What changes and enhancements should we expect? Since inception, our goal for Zend Framework has been to further the art of PHP and ensure our users concentrate on the business logic of their application rather than wasting time reinventing the plumbing. The plumbing is Zend Framework's job.

We have built an incredibly powerful framework with Zend Framework 2 that met its key goals of flexibility, consistency and testability. However, the world has changed since ZF2 was released, and the project needs to move with the times. With that in mind, we have gathered feedback from our users and core contributors to map the path forward. Zend Framework 3 will be an evolution from ZF2, concentrating on simplicity, reusability, and performance.

The post lists out a few of the things involved in this roadmap including separating components into individual, versioned projects and embracing the concept and functionality of middleware. If you'd like to get involved or just find out about the latest on this upcoming version, be sure you either join the zf-contributors mailing list or come to the #zftalk.dev channel on the Freenode IRC network.

In his latest post Stephan Hochdörfer shows you how to define Phing tasks according to the PSR-0 autoloading format. Phing is a PHP-based automation tool that uses an XML configuration to execute a series of tasks.

Before anybody complains: I know that "as of 2014-10-21 PSR-0 has been marked as deprecated. PSR-4 is now recommended as an alternative." - Anyway I still think this little gem makes sense to be shared because a lot of people are probably not aware of it. I recently found out by accident that it is possible pass a task name in PSR-0 style to the "taskdef" task. In the old days you had to use the Java-like dot-style notation like this and also define the classpath to make sure the class could be loaded correct! This is ok if the task resides in the same project. If the task is located in a dependent package loaded via Composer this can get ugly.

The post is quick but provides two very handy code examples, one showing the old "dot notation" version and the other showing how to make use of the autoloader. The trick is in the classname value and using the full namespace/class name rather than the dot notation.

The PHP.net has posted the latest releases of the language for all of the major series - PHP 5.4, 5.5 and 5.6. Each release fixes several bugs including a few security related issues:

• CVE-2015-0231 - a "use after free" issue with unserialize
• CVE-2014-9427 - an out of bounds issue with php-cgi
• CVE-2015-0232 - free being called on an unitialized pointer

It is strongly encouraged that you upgrade to the latest release for the major version you're using to prevent issues around these vulnerabilities. You can find these latest releases on the main downloads page or windows.php.net for the Windows binaries.

In the latest Three Devs & A Maybe podcast the hosts Michael Budd, Fraser Hart, Lewis Cains and Edd Mann are joined by Joe Watkins aka krakjoe for an update on all things PHP.

This week we are lucky to be joined by Joe Watkins, for a general catch-up on a host of PHP-related topics. We start the show off talking about his newly created blog and what drew him to start writing. Following this, we touch upon his first proposed talk on 'Parallel PHP' - hoping to resolve some of the confusion around concurrent terminology and patterns. We then mention his experience looking at YouTube Vitess (for MySQL scaling), and the pros and cons of the team deciding to use Go. His work on strict parameter type-hints is then discussed, along with how the idea has changed over time to be a little less strict. We then highlight the awesome work that Nikic has done for the PHP community, along with his most recent article on the improvements made to PHP's hash-table implementation. PHP 7 and the proposed 5.7 release are then touched upon, followed by the speedy Unicode String implementation. Finally, we discuss the common perception of fear around compiling PHP from source, along with the differences between static and shared libraries.

You can listen to this latest episode either through the in-page audio player or by downloading the mp3 of the show and listening at your leisure. If you enjoy the episode, be sure to subscribe to their feed to get the latest episodes as they're released.