| Home | Books | PHP5 Hosting | Sudoku | About TPG |
| Company | Work for the WWE |
| Location | Stamford, CT |
| Title | Sr. PHP Developer |
| Summary |
We need a Sr. PHP Developer Requirements: PHP/Mysql Experience: 3-4 years, where 1 year must be PHP5. Candidates must be well versed in:
Candidates must show:
Other skills:
Office Location: WWE Corporate Office - Stamford |
| Link | More Information |
Cal Evans has a new post over on the Zend Developer Zone today talking about an upcoming conference, a MySQL-related one, that several of the notable PHP speakers will be presenting at - the MySQL Users Conference.
This year’s event takes place from April 23rd — April 26th in Santa Clara, CA. This year’s line up looks better than ever. In amongst all the database names and Internet Luminaries, you’ll find a few names that PHP people will recognize.
Among those on the list there are names like George Schlossnagle, Rasmus Lerdorf and Laura Thomson. You can get complete information about the conference (for which you can still register for) at the main conference website.
Wanting to automate a common task he found himself doing, Raphael Stolt came up with his own process and use Phing to help.
To round off an older article on this blog called “Using the PHP 5 reflection API to keep track of unsolved refactorings” I wanted to automate the following task: collect and log some information about developer marked unsolved refactorings for a single class file or more common multiple files of an whole directory. And as I’m getting more and more acquainted with Phing I wanted to craft this custom task by using it’s provided extension possibilities.
He gives examples of what the “unsolvedRefactoring” notation looks, the XML mapping for its definition, and the code that actually makes the mapping work - and makes it easy to pull out the needed information. There’s two versions presented, one a normal pull and the other modified slightly to “actually retrieve the metadata of the methods marked as improveable via the @unsolvedRefactoring doclet”. And, finally, the integration with Phing comes, showing how to run the files and what the results should look like.
In a new post to the SitePoint PHP Blog today, Ian Muir shows you how to keep thing separated using the HTML Template IT extension. It helps prevent application functionality and logic from seeping its way into your output.
One of the more challenging things I’ve run into while doing PHP development is effectively separating presentation from program logic. In many projects, I felt I was doing a great job until I had to do a markup change and jump through a lot hurdles to make it happen. In my recent projects, I’ve starting using the HTML Template IT extension in PEAR, and its made things a lot easier.
By way of example, he gives code blocks - one showing an example template and the other how to populate it with your own data. You can get more information on the extension from it’s PEAR page.
The Developer Tutorial website has a new article posted today about the creation of “state-enabled applications” with PHP. Basically, a chunk of functionality to keep user data persistent throughout the whole time they’re on the site.
A major drawback is that while browsing from one page to another, the website does not remember the State of the browsing session. This make interactivity almost impossible. In order to increase interactivity, the developer can use the session handling features of PHP to augment the features of HTTP in order to remember the State of the browsing session.
They look at two solutions - using cookies and using sessions. Cookies are simple enough, but when it comes to sessions, there’s actually two different roads to follow: with cookies enabled and without. They have to be handled slightly differently, but both essentially work the same way.