On our sister site, AjaxDeveloper.org, today, there's a new post that mentions the latest blog post from Joshua Eichorn - a look at Javascript behaviors in his PEAR package, HTML_AJAX.

Welcome to part two of the series "Sending email with AJAX." In three parts, this series goes through the making of a simple web-based email application. It uses AJAX as the driving technology for fetching the files responsible for sending email from the server, as well as for adding and updating contacts.

This part covers the development of a "email sender" module, a "contact listing" module, the "contact insertion" module, and, finally, starting things up with the initializeEmailClient function.

On our sister site, AjaxDeveloper.org, today, there's a new post that mentions the latest blog post from Joshua Eichorn - a look at Javascript behaviors in his PEAR package, HTML_AJAX.

Welcome to part two of the series "Sending email with AJAX." In three parts, this series goes through the making of a simple web-based email application. It uses AJAX as the driving technology for fetching the files responsible for sending email from the server, as well as for adding and updating contacts.

This part covers the development of a "email sender" module, a "contact listing" module, the "contact insertion" module, and, finally, starting things up with the initializeEmailClient function.

PHP Magazine has posted this new article from Lukas Smith today with a "State of the PEAR Address", an overview of where PEAR stands in the PHP community today.

For those of you who have been living under a rock the last few years, you may have managed to evade PEAR. However, avid readers of the International PHP Magazine will know PEAR quite well, so here is a quick run down.

He goes through a look at what PEAR is, the debates over its structure, monitoring for "high-quality non-redundant code", what checks and balances are in place, the myth of bloated PEAR code, how you can contribute, and a call to action for all developers out there to get involved. There's a lot more in there than that, but you'll have to check out the whole article for that...

PHP Magazine has posted this new article from Lukas Smith today with a "State of the PEAR Address", an overview of where PEAR stands in the PHP community today.

For those of you who have been living under a rock the last few years, you may have managed to evade PEAR. However, avid readers of the International PHP Magazine will know PEAR quite well, so here is a quick run down.

He goes through a look at what PEAR is, the debates over its structure, monitoring for "high-quality non-redundant code", what checks and balances are in place, the myth of bloated PEAR code, how you can contribute, and a call to action for all developers out there to get involved. There's a lot more in there than that, but you'll have to check out the whole article for that...