It feels like an age ago that I wrote a component and helper for CakePHP that could mobilize an app. Since then, things in the WAPL and Wapple world have moved on at a rate of knots and it’s time to re-write, re-factor and re-engineer the mobile cake code to keep it up to date.
The first version had a pretty basic component, used SOAP to communicate and had no in-built schema check to always produce valid WAPL code.
PHP Package as a Vendor
But now there is a PHP package available that handles the schema check and communication can be done by either REST or SOAP (the preferred method would now seem to be REST seeing as it has better error handling and doesn’t trigger a fatal error if a soap client can’t be created).
Plugging that package in as a vendor should be dead easy (although it does need a few little mods and upgrades of its own first) and then it’ll be just a case of writing a component and helper to make use of it.
Hopefully I’ll have something ready this week so you’ll be able to mobilize your real world cake apps!
Let me know if you have any ideas for how it should be built – as a component & helper? Maybe a plugin? Or just keep it as a vendor.. or maybe all of the above!
Related posts:
- REST or SOAP? Or don’t care?
- PHP Classes – WAPL code released
- WordPress Mobile Plugin Version 1.2 is here
- WordPress on Load Balanced Servers
Tags: CakePHP, component, helper, refactor, REST, SOAP, vendor
