As web developers, we know the importance of the JavaScript console provided by the browser in testing out code snippets. We don't need to write an entire HTML page and JavaScript code just to verify the functioning or logic of a small routine we wrote. Instead, we simply run the expressions in the console and immediately see the results. Similarly, a REPL (Read-Eval-Print Loop) is the console of a programming language in which we can write code line-by-line and see what it does. [...] PHP's REPL is very good in what it does, although it does have some limitations. [...] And so, Boris tries to solve these problems and other concerns as well.

He walks you through the installation (via a git clone and, later, through Composer) and shows how to run it as well as some sample output. He also shows how to make a custom command-line Boris runner and how to embed it into your application. His example of a tool that would benefit from this is a command-line web service client using Boris and Guzzle.

Behat scenarios are one of the best ways to describe system. UML Use Cases or tons of pages in SRS documents are fine, but hard to understand from the begining, and even harder to maintain in the future. Behat eases this process and also gives opportunity to automate requirements verification. To write Behat scenarios you need a text editor. I've picked my favourite - Vim, which highlights *.feature files syntax. But business people mostly don't use Vim, so I need to figure a way, to expose scenarios in easy and pleasant way.

His solution involves setting up some printing options in vim to export the tests as a Postscript file, setting the "colorscheme" to the default setting so the colors will be retained. The result is exported (via the "hardcopy" command) and can be converted into a PDF (with a result like this).

What if you still need to have printing support in your PHP application? With Zend Server, Zend's integrated PHP application stack, the answer might be not what you were expecting. Use the PHP Java Bridge, available in both the community and commercial editions of Zend Server.

Their method combines Java code with some native PHP code to create a "printer" and point your scripts to it. Various options and configuration file information are included as well as two scripts - one to make a simple "one image" document and another to make a more complex PDF containing an interactive form.

Q: Tell me some about the update/restructuring (like what prompted the change)

A: As of December 2008, php|architect will enter its sixth year of publication. Much has changed within the PHP community - and in our company'"since we launched our magazine, and we felt that it was time to ensure that our brand and our flagship product were up-to-date with the market they serve.

The process of change actually started earlier this summer, when we launched our new line of training courses - the first truly comprehensive training program designed specifically for PHP developers. Our brand identity and the magazine were the next logical targets - particularly when you consider how long they have been around and how many people they reach every month.

In addition, one problem that we have always had with the magazine has been its publication schedule - we initially created php|architect as a PDF-only publication, and since we've switched to the print format we've been struggling with the management of our publication timelines. The unfortunate reality is that postal services throughout the world sometimes take a *really* long time to deliver third-class mail and, historically. we have never done as good a job of taking that into account as we could'"something that we intend to fix with this relaunch.

Finally, our aim with php|architect has always been to create a resource capable of providing the PHP community with the educational tools and knowledge needed by professionals who work and operate in world-class, enterprise-level environments. We felt that our current price point and distribution strategy had moved away from this core goal, and that a major adjustment was needed to bring us back on track.

Q: What does this mean for current readers/subscribers?

A: A lot of good things! First of all, the cost of a subscription goes down to as low as $29.99 for twelve issues - and that includes both the print *and* the PDF versions of the magazine. Naturally, we're going to make good on all our current subscribers and extend their subscriptions based on the cost of the magazine when they signed up for it - thus, most people should see their remaining issue counts go up considerably at no extra cost, and new subscribers will be able to finally get access to the magazine at a very reasonable price.

In addition, our current subscribers (as well as the new ones!) will enjoy better delivery times, and all the advantages that come with the new format.

Q: What all is involved in the change? Are there any changes to the magazine(s)?

A: Much of the work that is involved in the relaunch of our activities will go on behind the scenes, but visitors to our websites will note lots of changes over the coming months'"starting with a minor redesign of our site to accommodate the new logo and brand identity, as well as the new pricing and subscription strategy for the magazine.

Starting with the January issue, we are targeting a 45-day window for shipment of the magazine'"meaning that the print copies of the January issue, for example, will be mailed out to subscribers around the beginning of December - thus ensuring more prompt delivery in everybody's mailboxes. In addition, the entire magazine will switch to full-colour printing throughout - thus providing a richer experience for our users and a more challenging and fun environment for us to develop our work in. We will continue to support the PDF version using our popular DRM-free distribution and personalization system, and try to synchronize the arrival of the print issue with the release of the PDF file as closely as possible.

Also for the first time, we are publishing our editorial calendar for all of 2009. This will help readers know what's coming, advertisers better plan their campaigns and authors draw inspiration for their writing activities.

Q: Will there be new things available immediately after the change?

Once the initial brand relaunch is complete, we are planning to re-engineer our site to provide a smoother shopping experience and better account management facilities. Since we relaunched our website almost a year ago, our web-based sales have more than doubled, and our back-end infrastructure has handled the growth without any problems. On the front-end side, however, we have done a considerable amount of research on the habits and needs of our customers and have discovered areas ripe for improvements that we couldn't even imagine before, and we will be redesigning some areas of our website to reflect the lessons we have learned.

In addition, we have some great promotions planned between here and New Year's - including a comeback for our greatly popular "Seven Days of Christmas" series of offers over the holidays. We skipped 7DOX last year, and our users gave us an earful for it, so we'll make sure to keep our priorities straight this time!

The new php|architect website has already been launched along with new training courses for the Zend Framework Certified Exam.

To subscribe to the new and improved php|architect magazine, visit their subscription page and signup. Find out more in this post on their site.

We're happy to announce the upcoming release of php|architect's Guide to Programming Magento, the first comprehensive guide for developers who want to learn more about the Magento e-commerce platform.

The book, by Mark Kimsal shows you how to install and successfully deploy a Magento installation on your website. The preorder is available right now for a 15% discount and the full PDF version will be released on May 15th, 2008 (print on May 31st). Check out the product page for more information and to reserve your copy today.

Again a somewhat belated announcement: PHP in Action is in print. [...] Strenuously objective as always, I have to say that it's a pretty good book. I've had to read it about fifteen times already, and I still sort of enjoyed it the last time.

You can get more information on the book from its page on the Manning Publishing website as well as purchase a copy - $39.99 USD for the print version (plus PDF ebook) or just $20.00 USD for the PDF ebook by itself.

Manning Publications has released the book PHP In Action as ebook in PDF format. I wrote it with help from my co-authors Marcus Baker and Chris Shiflett. The print version is due out June 30.

You can order both the ebook only or a combo of the ebook plus the print version directly from Manning.

Many PHP examples out there are designed for a linux/unix operating system. I am going to give some examples of some interesting functionality that only works with php running in a windows environment (IIS or apache).

Here's the list:

• Eject the CD-ROM
• Read and write from/to the registry
• Register and un-register phpscripts as a windows service
• Print pages/data
• List the current system processes

Each item has sample code and a simple explanation to get you started using it.

Essentially, what I plan to demonstrate here is how this pattern can be used to build different versions of a given web document on the fly, either for display on a typical computer monitor, or for printing.

This involves the creation of a class to define the styles for both sides - print and screen - and a class that will figure out which of these needs to be applied.

The web site I currently work on is going to be for the hotel where my step father is the manager of. One of the things that is going to be an important 'feature' for the site, is to make it printer friendly.

Since the new site has a very clean markup, I thought about simply creating an additonal style sheet for the media type "print". However, after thinking about it a little bit more today, I came to to the conclusion that I'm dealing with WYSIWYG visitors. So I decided to get a little fancier, and to create a PrintController, which would output printable versions of any site requested by /print/*

He gives the code for the controller and for the easy to use link to go over to the "printable version" of each page, hiding the none-printable information from the browser.