Attention all you Zend Framework junkies, Jochen Hartmann has uploaded a new video to YouTube that demonstrates the basics of how to use Zend Framework with the YouTube Data API. This step-by-step demonstration walks you though everything you need to know to upload files to Youtube via Zend Framework.

The video (from the official Google developers) shows the creation of a simple application that uses the Google Data component of the Zend Framework to upload the selected video from their local machine.

You can find out more about the Google API for YouTube on this page on the Google Code website.

My about page has mentioned a web based frontend for Xdebug for some time. The project has a name now: The idea for Webgrind, a spin on Valgrind, came from lack of profiling tools for PHP, particularly on OSX. Though it is possible to install kcachegrind on osx it seems overkill for many uses and is definitely not as easy as unzipping a folder to the webroot.

He and Jacob Oettinger have started up the project and have posted some initial code over on the Google Code page for Webgrind. You can check out a screenshot of it in action here too.

Because such [popularity] data is much better to comprehend when accompanied by some nice graphs, I had a look at the Google Chart API today.

He also mentions three wrapper libraries that help your apps interface with the Charts API. Of course, he also includes some graphs of the popularity stats showing things like web server usage and PHP versions.

TechCrunch is announcing Google's new "App Engine" service being launched this evening. The basic service is a full app stack hosted and managed by Google, providing a web framework (maybe I'm misreading this?) and the Google 'big table' database service. [...] My question is "why was Python was chosen instead of PHP?"

There's been some great responses since it was originally posted including everything from agreement to rationalizations for the move (though there is a fair amount of PHP and Python bashing going on - an obvious occurance).

• Jay Pipes on some of the projects for MySQL Forge
• The PHP-GTK Community site on their project
• Marcus Borger encouraging participation in this year's GSoC
• Sara Golemon's pointing developers in the right direction
• A proposal from the thyphp.com site for a WordPress category suggestor
• Derick Rethans mentioning his "pet peeve", the optimizer for APC
• Elizabeth Smith promoting participation in any of the list of ideas

Keep up to date on the happenings on each of the projects in the PHP group on this page on the PHP.net wiki.

Hello everyone, as mentioned a few weeks ago the most awaited Google Summer of Code is back again this year. This being said, once again the PHP Project has been accepted and we have started posting our list of ideas (http://wiki.php.net/gsoc/2008).

Some of the projects proposed include:

• PECL, website improvements and Windows Build Support
• Automatic Code Checker
• Implement Unicode into PHP 6
• Build Infrastructure and macro bindings for writing extension in D
• Rewrite the run-tests.php script
• PhD: The PHP based Docbook renderer

Be sure to check out the full list and see where you might want to get involved!

Geocoding is the process of finding the longitude and latitude of a given address or location. The Google Maps service gives developers and web site owners free access to their geocoder, both using the Google Maps JavaScript API, as well as using the web service. In this article I will show you how to access the geocoder web service using PHP so that it can be used in your own applications.

The tutorial walks you through every step of the way - from getting your Google API ID to making a simple request all the way out to using placemarks to store locations to fetch later on.

This is a great, very detailed summary that anyone wanting to work with the Google API in PHP should definitely check out.

In a very productive CakePHP session with nate a couple weeks ago in Atlanta I finally implemented some new HttpSocket stuff that was needed (minimal support for cookies / ssl) for creating the new API as a datasource. Now that its done I'm fairly happy with the outcome of the new API.

You can download the source here and follow his simple two-ish step process for getting it working on your site and with your Google account.