On the PHP::Impact blog today Federico points out a few HTML DOM parsers that work similar to jQuery:

• the Simple HTML DOM Parser
• Zend_Dom_Query
• phpQuery

Check out a previous tutorial of his for more information on using DOM parsers to scrape information from remote sites.

On the Developer Tutorials blog today Akash Mehta looks at screen scraping using a simple DOM library to help make it easy.

In PHP, regular expressions tend to get rather messy, DOM calls can be confusing and verbose, and often the string functions just aren't enough. In this tutorial, I'll show you how to use the middle ground - the open source PHP Simple HTML DOM Parser library, which provides jQuery-grade awesomeness for easy screen scraping without messy regular expressions.

In his examples he shows how to grab the contents of a page (google.com), find and replace information in the HTML and perform a query on the data (like finding each of the news stories out of the front page of slashdot.org).

In a new blog post today Jonathan Snook shows how to create a contact form for your CakePHP application (version 1.2).

Most contact forms take a name and feedback from a user and mail it off to the administrator but don't store any information in the database. This tutorial will show how to use CakePHP's models, even when no table is being used.

He shows how to define the model class, set up the mapping of columns to named elements and the code to handle the submit. It just sends a basic email with the contents of the form with a few validation rules to ensure it's not abused. Simple stuff...

Nick Halstead and crew have launched fav.or.it (yesterday), a social site that seeks to "bring blogging to the masses" and runs on top of the Zend Framework.

From their blog:

We have long talked about 'bringing blogging to the masses' and today we have released a new version of fav.or.it which we think moves a quite a few steps towards that goal. We hope that we have firstly simplified the interaction with blogosphere and in turn made it accessible to a whole new audience. And for the more tech aware users we hope we have a raft of features that will also appeal.

Some of the more important things the site can do include conversation tracking, identity management, simple and easy to use searching, integrated commenting and much more. Check out Nick's list for more great features or just make a login and check it out for yourself.

Lukas Smith recently posted about issues he's been coming across with the "KISS" mentality (and code) that the Zend Framework implements, specifically for the Zend_Feed component.

Now that I am actually using the Zend Framework on my first project, hitting bugs/limitations in Zend_Feed and therefore looking at the code, I must say I am seeing feature duplication with internal PHP features that does not quite fit in with the KISS principle.

He points out a few things that illustrate his point - the use of Zend_Http_Client instead of a strea context, passing XML contents into loadXML instead of just load. As a replacement, he's considered a Feed component from the eZ components system, but it hasn't been released (officially) yet. So, as an alternative, he's come up with a patch to fix a few things in the Zend_Feed component to make it a bit more KISS-friendly.

The PHP::Impact blog has posted a list of thirty classes and components that can make your PHP development life so much easier:

Simplicity and extensibility are the main reasons why PHP became the favourite dynamic language of the Web. In the last decade, PHP has developed from a niche language for adding dynamic functionality to small websites to a powerful tool making strong inroads into large-scale Web systems.

Their list includes software like:

• LINQ for PHP
• Doctrine
• HTML Purifier
• SimpleTest
• Phing
• PHP Security Scanner
• SimplePie
• Smarty

...and many more. Check out the full list for all sorts of useful tools.

Felix Geisendorfer is taking an interesting approach to defining programming in this new post to the Debuggable blog - he's coming at it more from the level of the perception the programmer has about writing good code.

I believe understanding the patterns in your own thinking will by far make the biggest impact on how good you will get as a programmer. Forget design patterns, forget unit testing, forget all those functions you know. Important is to question why they exist and how they could be improved.

He illustrates through a few examples what he means. He describes one such thought method, the "return home early" process - basically, if something looks too complex for its own good, it probably is. He offers a different way of thinking about it too, a more visual way that can help simplify things even more by laying out the pieces and seeing where they all fit.

On the Developer Tutorials site today, Akash Mehta has posted his look at having search functionality on your website.

Today's websites have a lot of content. [...] Needless to say, effectively searching all that data can be a real challenge, and chances are at the end of the day you'll still be stuck with a slow and ineffective search system. [...] Implementing effective search doesn't have to be hard. In this tutorial, I'll show you how to build a basic site-specific web search in just five lines of code, using the Yahoo! APIs.

He includes a (very) brief look at the search API Yahoo! offers followed by examples of queries and then on to the real deal, a search system that takes in a user query and asks the Yahoo! API for results matching it. The results are outputted below the box.

On the Developer Tutorials blog today, Hasin Hayder has pointed out a handy PHP function that can make your debugging a bit less of a headache - debug_backtrace.

Most of the PHP developers debug php code in their local machine just by trial and error using "print_r","var_dump" and "echo". They don't write unit tests or follow any advanced debugger like xdebug. But the problem of using these methods is you cannot fool proof your code and their might be some bugs still present in your code.

He includes a simple example to show how it works and what kind of output it will give - a nested function call. Personally, I use this in some of my classes (like a database abstraction later) to track and see which functions my calls are coming from and what data they're sending me - easier to debug in one place than trying to guess.

Nick Halstead has shared tip number six in his "Programming Tips" series. This one focuses on keeping things simple.

Next up on my programming tips series we have another guest post. This one is written by Georgi Momchilov. "Make things as simple as possible, but no simpler" ( quote from Einstein ).

Georgi suggests thinking of your application like a living organism or a house - don't expect any one part of it to take more than its share of load. Keep components simple and to the point of doing they job. It makes for much easier code to maintain and to expand on later.