Update, 2012-05-24: Fixed some typos and added the screenshot (eyecandy!). I think it took me (or us) a couple attempts to get this right — let me introduce you to Zf_Crud, a CRUD controller for the Zend Framework. What’s CRUD? CRUD is an acronym and stands for: Create Read Update Delete A general purpose for CRUD are administrative interfaces — view records, create them, update them or delete them. Think of phpMyAdmin as a very general purpose CRUD interface....
So frequently, I need to run small data migrations or transformations. Especially on the way to Doctrine, there’s a lot to clean-up in a database which has been used and evolved over five years or so. The other day, I wanted to run some transformations on the data located a history column in a pretty simple table — here’s what it looks like: Building a class to interface the table is simple:...
I dig Twitter’s bootstrap library because as a developer, it helps me produce good looking forms without a lot of effort. Especially when administration interfaces are concerned, you I can only go so far — my first constraint is not being a great designer (to confirm, check out this blog) and two: I don’t like working with ugly interfaces. To cut to the chase… Easybib_Form_Decorator It’s a decorator library for Zend_Form....
Here’s how I literally wasted eight hours of my life. :-) We signed up for Yahoo! Search Boss last week. The process itself was pretty straight: Sign into your Yahoo! account at https://developer.apps.yahoo.com/ Click “New Project”, fill out the form. Then click on the project name, activate “Yahoo! Search Boss” by suppling some billing info. Consumer key rejected? The above process doesn’t even take five minutes, but then I spent eight hours figuring out what oauth_problem=consumer_key_rejected means....
After running away screaming from Zend_XmlRpc we migrated of our internal webservices are RESTful nowadays — which implies that we make heavy use of HTTP status codes and so on. On the PHP side of things we implemented almost all of those webservices using the Zend Framework where some parts are replaced by in-house replacements (mostly stripped-down and optimized versions equivalents of Zend_Foo) and a couple nifty PEAR packages. RESTful — how does it work?...