The deed is done. I’ve formally given the nice people at Yamgo/AdSpruce my notice to leave the company. While this is really a sad day for me overall, it’s also an exciting one. I’ve had a great time here in Swansea Bay and feel like I’ve made an amazing contribution to the development of an SDK that is now delivering 10m requests daily.
(or how I stopped blindly including shit in my composer.json)
I have absolutely no doubt this post will be largely disagreed upon by many in the PHP community, but I’ve had a terrible day and I’m hoping that the process of just getting this off my chest will be therapeutic in some way.
Mainly because I keep forgetting how to do this, I decided to create a quick reminder on how to get forms to hydrate into objects when they are successfully validated.
I know lots of people have been waiting a long time for Part 3 of this series, I can only apologies for the delay, and hope that this post somehow makes up for the wait!
In February I gave a talk on behalf of Zend which compiled parts one and two of this series, plus the non-written part
three into a spoken talk that included code examples. The video is included here for all your viewing pleasure:
This is part 2 of my series aimed at giving Zend Framework 1 developers an introduction to Zend Framework 2, if you haven’t read part 1, there’s a link at the top of the page.
I’ve decided to actually make this series 3 parts, in this part I’ll be talking about Routing, the Event Manager, and finally the Service Manager.
Having worked with ZF1 for a lot of years, I’ve been watching the development of ZF2 with interest. I’ve tried nearly every version, from the heady days of the pre-Skeleton App, right through the betas and release candidates.
After speaking to a prospective employer in a job interview, I was interested to try out the ZendMvcControllerRestfulController. With Zend_Json_Server in ZF1 having, shall we say, a less than sterling reputation, it was very interesting for me to see how the strategy has been implemented in ZF2.
Recently I’ve been working a lot on trying to get OAuth2 support into beta 4 of Zend Framework 2, and there were a few challenges. Allowing the client to consume the variety of providers out there proved to be the first. There have been several drafts of the OAuth2 specification, and providers have implemented a variety of the drafts. As each of the drafts have subtle differences, the client needs to be able to have a default configuration that can be over-ridden on a per-provider basis.
Yes, it’s true, I’ve officially mastered the most under documented API in history.
We are currently using the FBML method of publishing our wonderful Lord of the Rings licensed game. All has been rosey in the garden of The One Ring, until we found out that the FBJS Flash bridge is the most unimpressive piece of script I have ever seen. We found that random errors would creep into the loading of the SWF because of this bridge, and decided that the only way around it was to bite the bullet and move to iframe mode.
Today I wanted to change the custom validation error messages that are generated when using Zend_Form. This isn’t as easy as I first hoped, because even with all of the documentation on the ZF site, I still had some problems understanding exactly what the Zend_Validate class needed to receive in order to display my custom errors.