If you have a Safari Library subscription, you can view the chapters free of charge, and see new ones as they’re added. Without a subscription, you can get access to the book in PDF format for $34.99, including the finished ebook version when the book is complete. You can also opt for the Rough Cuts PDF and Print bundle for $67.48. The print version is expected to be released in early August.

The chapters currently available are Lessons 1-3 and 4-7, covering the following subjects:

• An in-depth look at all the PHP features in Dreamweaver CS5
• Instructions for setting up a local PHP development environment
• A quick PHP crash course (or refresher)
• Creating your own database in MySQL
• Using Dreamweaver server behaviors for automatic code generation
• Building a robust user registration system with Zend_Validate and Zend_Db

Chapters still to come concentrate heavily on using selected modules of the Zend Framework for sending email, uploading files, and building a content management system. (To avoid any misunderstanding, the book does not use the MVC design pattern—it follows what the ZF documentation calls “use at will” design, making use of individual components.)

When CS4 was released 18 months ago, I described it as the “most significant release of Dreamweaver since Dreamweaver MX ”. To my mind, Dreamweaver CS5 just blows CS4 out of the water. Before I explain why, let me address the negatives. At least three groups of people are going to be disappointed by this new release:

• Early adopters of HTML5 and CSS3—support is close to zero.
• Developers of dynamic sites hoping for new server behaviors—there aren’t any.
• Former users of GoLive—Dreamweaver CS5 hasn’t incorporated any features from GL.

With the debate that has been raging over Apple’s decision to ban Flash from the iPad and iPhone in the name of HTML5 and “web standards”, many will be stunned to learn that the only concession to HTML5 in Dreamweaver CS5 is the option to use an HTML5 DOCTYPE. There’s also no support for CSS3. Has Adobe missed the boat on this? In publicity terms, maybe. In reality, I don’t think so.

HTML5 and CSS3 are still evolving. The current web standards are still HTML 4.01, XHTML 1.0, and CSS2.1. Moreover, Dreamweaver is extensible. Rick Curran has already created an extension for CSS3 code hints. You can also add HTML5 tags to Dreamweaver through the Tag Library. No doubt someone will come up with an extension for that, too. In my view, it would have been a mistake for Adobe to release a half-baked implementation of incomplete standards that are still not supported on all browsers in widespread use.

The other decision that’s likely to cause controversy is the lack of new server behaviors. In fact, some have been removed: CS5 has continued the process of weeding out support for less popular (at least among Dreamweaver users) server-side technologies. JSP and ASP.NET were dropped in CS4. Now, ASP JavaScript has gone, too, although ASP VBScript still survives. There are a few minor security improvements and bug fixes to the PHP server behaviors, but nothing new.

The basic design of the server behaviors is now eight years old, so many people had been asking for new, improved ones, particularly after the decision to drop Adobe Dreamweaver Developer Toolbox (ADDT) last year. Few people realized the significance of that move. This is only my personal opinion, but I think Adobe was sending a clear signal that it’s not in the business of creating server behaviors to automate the generation of server-side code. It’s leaving that market to extension developers like WebAssist, CartWeaver, DMXZone, and others.

So, what is it about Dreamweaver CS5 that I like so much? Lots!

One of the biggest improvements is that Live View now works like a browser. “What’s new about that?” you might think. The difference is that in CS5, the links work. Hold down Ctrl/Cmd while clicking a link, and the target page loads into the Dreamweaver Document window—even if it’s a live page on the internet (assuming, of course, that you’re connected). The Related Files toolbar gives you direct access to the code of all pages linked to the new page. If the target page is on a remote site, the code is read-only; but on a local site, you can edit the code, and press F5 to see the results in Live View. If you want to keep the changes, there’s a new option on the File menu to Save All Related Files.

If you’re still wondering why this is an improvement, just try it with a content management system (CMS) like WordPress, Drupal, or Joomla! As long as you have set up a testing server, you can now view a CMS in Live View. Not only that, Dreamweaver CS5 lets you interact directly with a database. You can test online forms in Live View, inserting database records, updating, and deleting them. Dreamweaver CS5 eliminates the need to make constant round trips to a browser for testing, because the browser is right there in the Document window.

Of course, you still need to test pages in a variety of browsers, but you can launch BrowserLab directly from Dreamweaver to test your pages in Adobe’s online service. Up to now, BrowserLab has been free, but it’s being turned into a paid-for service. Your purchase of Dreamweaver CS5 or one of the suites gives you continued free access to BrowserLab and InContext Editing for another year. [Update] Adobe announced today that development of InContext Editing is being terminated. You will be able to maintain existing sites, but the service will cease to exist as a standalone service in 2011. For more details, see the InContext Editing FAQ.

The related files feature now searches for dynamically related files, in addition to those directly linked to the current page. This gives users of WordPress and other CMSs access to the style sheets, which you can edit in Split view or through the CSS Styles panel, seeing the results immediately right inside Dreamweaver. You can even navigate to inside pages of a CMS to style them. And to make it easier to work with CSS, Live View has a CSS Inspect button that highlights block-level elements, padding, and margins in the same way as Firebug—all within the Document window. Another Firebug-like feature is the ability to disable a style rule temporarily by clicking next to the property name in the CSS Styles panel.

As a PHP developer, it’s the changes in Code view that really excite me. When you start typing a PHP script in Dreamweaver CS5, you’ll immediately notice a red marker in the line numbers column and an alert about a syntax error.

Complete the line without errors, and the marker and warning disappear. Dreamweaver constantly checks your syntax on the fly. It doesn’t tell you what the errors are, but it highlights all lines with errors, making the debugging process much quicker. PHP code hints have also been improved dramatically. There’s full support for all core functions, constants, and classes (as of PHP 5.2).

Code hinting is also much smarter. Instead of needing to search through code hints alphabetically, Dreamweaver CS5 searches for substrings. This is helpful when you can’t remember the exact name of function or class—just type the part of the name that you remember, and Dreamweaver includes it in the list. You can also work out your own shortcuts. For example, if you press Ctrl+spacebar and type gesi, the code hints take you straight to getimagesize() by recognizing the ge of “image” and the si of “size”. And in case you don’t know how a function or class works, the official manual page—complete with code examples—appears as a tooltip at the bottom of the selected code hint.

Incidentally, the smart nature of code hints also applies to style sheets. If, like me, you constantly pick widows instead of width, just type dt—it takes you straight to width.

For serious PHP developers, it gets even better. Dreamweaver CS5 is capable of code introspection, so it builds code hints on the fly for your own functions and classes, as well as for third-party libraries, such as the Zend Framework.

The definition files don’t even need to be directly attached to the page you’re working in. With Site-Specific Code Hints, you tell Dreamweaver where your library files are located, and it scans them for you automatically.

My feeling is that Adobe made the right decisions. HTML5 and CSS3 are not ready for prime time; and server behaviors can offer only a limited number of options if they’re to remain manageable. Site-Specific Code Hints and the improvements to Live View open up a vast new range of opportunities to the beginner and more experienced PHP developer alike. I liked Dreamweaver CS4 a lot, but CS5 is a huge improvement.

Of course, Adobe can’t stop there. CS6 will need to offer solid support for HTML5 and CSS3, but by that time the specification should have settled down and browsers should have caught up.

I answer a lot of questions in the Dreamweaver forums, and realized that a lot of the solutions I was coming up with for people weren’t easy to find after a couple of days. So, rather than letting them disappear into cyberoblivion, I decided to add any of general interest to the cookbook when I had a few spare moments. The Dreamweaver Cookbook is intended for code samples, and doesn’t have the capability of including screenshots, so I’ll continue posting longer tutorials on my own site. But I hope you’ll find my contributions to the cookbook useful.

Here are direct links to some of the articles I have added to the Dreamweaver Cookbook:

• Create nested lists from a recordset
• Set a time limit on a login session
• Registration system that requires the user to validate the email address (in two parts)
• Alternate colours for table rows (using PHP, Spry, or jQuery)
• Upload image to website
• Format date for insertion into MySQL
• Formatting dates stored in MySQL

The Dreamweaver Cookbook is open to anyone to either request recipes or contribute recipes of their own. It could turn into a very useful resource if people start using it regularly. Check it out!

The only recent ones not yet available on Kindle are The Essential Guide to Dreamweaver CS3 and The Essential Guide to Dreamweaver CS4. Both are long and contain a large number of screenshots, so it might take some time to convert them. Once they are, though, I’m sure Kindle owners will be delighted at no longer needing to lug such heavy books around.

I only wish that Amazon would make Kindle available in Europe (and other parts of the world), too. I’ve been itching to get my hands on a Kindle.

O’Reilly classifies a programming language as “large” if more than 100,000 copies of books dedicated to that language sell during the year. That’s the total for all titles, not how many copies of each book that sell. According to O’Reilly’s data (gathered from Nielsen BookScan, which tracks roughly 70% of book sales in the USA), books on PHP were the third most popular category, selling a total of more than 173,000 units. The bad news is that 129 titles were competing for the same PHP book market, making the average sales for each title a meagre 1,340. I haven’t seen my sales figures for Q4 2008, but I’m pleased to say that the figures for the first three quarters put my sales well above the average. However, they’re not all that big, which is why I was surprised to find my book at number 3. O’Reilly lists the top 5 as follows:

1. Pro C# 2008 and the .NET 3.5 Platform
2. Sams Teach Yourself PHP, MySQL and Apache All in One
3. The Essential Guide to Dreamweaver CS3 with CSS, Ajax, and PHP
4. Head First Design Patterns
5. PHP 6 and MySQL 5 for Dynamic Web Sites: Visual QuickPro Guide

It’s interesting to note that three of the top 5 are about PHP, confirming my belief that PHP is a strong language that’s here to stay for a long while.

With so many books competing for a relatively small market, you might wonder why authors like me continue to write. Researching, writing, and editing a book takes many months of hard work—and all for the sake of a couple of dollars royalty on each copy sold. Part of the answer lies in the fact that I like writing. I did it for many years in my career as a radio and TV journalist; it’s what I’m good at. It’s also nice to see my work in print. In TV and radio news, I might have been seen or heard by millions, but once the news bulletin was over, that was it. Although computer books have a relatively short shelf life, they certainly last longer than a news bulletin; and I hope my readers get practical value from them.

The other thing that drives many of us to write is the hope that, one day, we’ll hit the big time. O’Reilly has also analyzed the top three best-selling writers of computer books: David Pogue, Scott Kelby, and Andy Rathbone. Between them, they account for nearly 6 percent of the computer book market. Andy Rathbone, who comes in at number 3, sells more books each year than I have sold since I started writing about PHP and web design five years ago. David Pogue, the biggest seller, clocked up an impressive 190,000 copies last year. I’m sure he’s delighted—and let’s be honest, he deserves success because he’s a good writer—but it pales into insignificance alongside JK Rowling, the creator of Harry Potter.

Anyway, thank you to everyone who bought my book and helped me reach number 3 in the Large Programming Languages category. And thank you to O’Reilly for doing all the number crunching.

If you’re contemplating buying one of my books, and want a better idea of what they’re like, sample chapters in PDF format are available for each title. Just go to the list of web design books at friends of ED, and click the link for the title you’re interested in. This brings up a description of the book; you can download the sample chapter from the links on the right.

You can find a link to the zip file for each book at the bottom of the following pages (files added for “Foundation PHP 5 for Flash”):

• Essential Guide to Dreamweaver CS4
• Essential Guide to Dreamweaver CS3
• PHP Solutions
• PHP Object-Oriented Solutions
• Foundation PHP for Dreamweaver 8
• Foundation PHP 5 for Flash

The problem with the main friends of ED website does not affect the friends of ED forum, where you can post any questions about the books and any problems you might encounter.

I’ll create a full tutorial on the revised procedure when I get time, but you can find a summary of the main differences on the updates page for The Essential Guide to Dreamweaver CS4.

If you turn magic quotes off in PHP—which you should—you won’t be affected by this bug. It serves as a reminder that magic quotes are due to be removed in PHP 6. Magic quotes were originally introduced to make life “easier” for inexperienced developers by automatically inserting a backslash in front of single and double quotes in user input to prevent problems with database insertion. However, they have proved more trouble than they’re worth. Instead of magic quotes, you should use dedicated functions, such as mysql_real_escape_string(), or prepared statements with MySQLi or PDO to handle quotes and other special characters and protect your database from SQL injection attacks.

The tutorials are hosted on an Adobe site, and the videos start automatically after opening in a new window. A control panel lets you skip to different sections of the tutorial, and most of the text can be read by opening the Notes tab. The videos are resizable, but are best viewed in a 1024 x 768 browser window. The Windows tutorial is here, and the Mac one is here.