Adobe has officially announced details of Creative Suite 6 (CS6) and the Creative Cloud. What’s particularly significant about this release is that it represents the last chance to skip one or two versions and still benefit from reduced upgrade pricing. Owners of CS4, CS5, and CS5.5 have until the end of December to upgrade to CS6. After that cut-off point, upgrade pricing will be available only to owners of the immediately preceding version. In other words, to upgrade to CS7 you’ll need to pay full price if you don’t own CS6.
Alternatively, you’ll have to switch to the Creative Cloud subscription service. The Creative Cloud has been very attractively priced, and it holds out the prospect of early updates and some nice bonus extras, such as Typekit fonts, but it has the disadvantage that once you stop paying, you can no longer use the software. I’ll leave it up to you to weigh up the pros and cons of the Creative Cloud. In this post, I’m going to concentrate on what’s new in Dreamweaver CS6 and what I think of it.
If I were to sum up this new version in a single word, I think that “evolutionary” is the most appropriate. The main focus is on CSS improvements, including:
Video Training Courses
I have recorded two video training courses about Dreamweaver CS6. The first one is a New Features Workshop, which contains more than three hours of videos showing how to use all these new features. It should be available from video2brain later this week. The other video course is an in-depth treatment of web design and development with Dreamweaver CS6, aimed mainly at beginners and intermediate users. It will be published jointly by Adobe Press and video2brain sometime later. I’ll post more details when they’re available.
Web Font Management
The new Web Fonts Manager in Dreamweaver CS6 installs web fonts into your personal configuration folder, making them available in all your Dreamweaver sites. Installing a font is very simple. You just launch the Web Fonts Manager from the Modify menu, and click Add Font. In the dialog box that appears, click the folder icon to the right of one of the font fields, and select the font. Dreamweaver detects all formats of the font in the same folder, and automatically fills in all the remaining fields, as shown in the following screen shot.
Installing a web font makes it available in Dreamweaver’s code hints and dialog boxes. You can also build custom font stacks that incorporate fonts that you have installed. When you select a web font in the CSS Styles panel or CSS Rule Definition dialog box, Dreamweaver copies the font files to a new folder in your site root, and creates a style sheet with the necessary
@font-face rule. Web fonts aren’t rendered in Design view, but they’re fully supported in Live view.
My only reservation about the way that Dreamweaver handles web fonts is that it uses a separate style sheet for each
@font-face rule. However, it’s easy enough to cut and paste the rules into the top of your main style sheet.
Dreamweaver CS6 makes it easy to create CSS transitions—simple animations that smooth the transition from one state to another, for example if you scale up an image when hovering over it. The quickest and simplest way is to use the new CSS Transitions panel, which creates both the transition properties and the styles for the end state in a single operation. The CSS Rule Definition dialog box supports the creation of more complex transitions, such as those triggered on a nested element. Both methods generate not only the standard properties, but also browser-specific prefixed versions. This is a great time-saver because you need browser-specific prefixes for Firefox, Internet Explorer, Opera, and WebKit-based browsers.
I like this feature a lot, but it seems odd that you need to use the CSS Rule Definition dialog box to create more advanced transitions. In my experience, advanced users rarely touch that dialog box. However, if a style rule already exists, you can just click the Edit Rule icon in the CSS Styles panel without having to go through the hassle of the New CSS Rule dialog box.
This is something that Dreamweaver users have been demanding for a long time—the ability to apply multiple classes to an element. Hallelujah, Adobe has finally listened. Just select the element in the Document window, and choose Apply Multiple Classes from the Class menu in the Property inspector to open the Multiclass Selection dialog box. This presents you with a list of all classes in your site, as shown in the following screen shot.
Select the check box alongside each class that you want to apply to the element. If you haven’t already defined the class, you can add it to the space-separated list in the field at the bottom of the dialog box. A long overdue, but nevertheless very welcome improvement.
Fluid Grid Layout
This should be the star attraction of Dreamweaver CS6. In some respects, it’s stunning, but it feels like a work in progress rather than a polished feature. Inspired by Ethan Marcotte’s Responsive Web Design, this feature allows you to specify three fluid grids for mobile, tablet, and desktop layout. Each grid can have 2–24 columns, and you can specify how wide the grid should spread across the screen, as shown in the following screen shot.
You then add fluid grid layout div elements to build the structure of your page in the mobile layout. Next comes the brilliant part—you can resize the elements and snap them to the grid, and move elements to sit alongside each other. All this is done in Design view or Live view, and Dreamweaver automatically calculates the width of elements and margins to four decimal places. The CSS uses percentage widths and floats, so it produces layouts that adapt to any screen size. It’s most definitely not a throwback to the bad old days of Dreamweaver’s Layout mode. The styles are constructed on the basis of “mobile first”, and work even in browsers that don’t understand media queries.
Where the Fluid Grid Layout feature falls down is in Dreamweaver’s inability to indicate which media query controls a particular style rule. Another problem is that it doesn’t support nesting elements to create more complex layouts. It’s to be hoped that these shortcomings will be addressed in an updater. One of the ideas behind the Creative Cloud subscription setup is that new features or improvements to existing ones can be added as soon as they’re ready without needing to wait for the next major release.
jQuery Mobile Theming
The integrated version of jQuery Mobile in Dreamweaver CS6 has been updated to the 1.0 stable version (not 1.1). There’s also a new jQuery Mobile Swatches panel that’s designed to make it easy to change the look of individual elements (see screen shot).
Let’s be honest. In the past, Dreamweaver’s FTP client was a dog. Not any more. It now supports multichannel transfers, and can even download at the same time as uploading. Orange arrows indicate items queued for transfer. When the transfer begins, the arrow turns green. And if you’re transferring a large item, hovering over the filename displays a tooltip of how much of the file has been transferred. With Dreamweaver CS5.5, it took more than 90 minutes to upload a WordPress site on my internet connection. Now, it’s more than ten times faster.
The FTP error messages are also more meaningful. No one is likely to buy Dreamweaver CS6 for its FTP client alone, but this is a major improvement to the program.
PhoneGap Build Integration
You can now build an app for iOS on either Mac or Windows, but in order to compile it, you need to create a valid signing key and upload it to PhoneGap Build. The signing key must be created on a Mac. You also need to register with Apple as an iOS developer and pay an annual fee.
I like the new features in Dreamweaver CS6, but I have to admit that they don’t have me jumping up and down with excitement. Maybe that’s because I felt CS5 and CS5.5 were such strong releases, and I was hoping for a similar performance this time. The Fluid Grid Layout and PhoneGap Build features had the potential to be outstanding, but fell slightly short of the mark. As a result, I’d give Dreamweaver CS6 only 7 or 8 out of 10. It’s good, but it could have been so much better.
In fairness to the Adobe engineering team, I understand that a huge amount of work was devoted to solving the long-standing problems with FTP and to converting the Mac version of Dreamweaver to run on Cocoa, the native application programming interface (API) for Mac OS X. The conversion to Cocoa should result in a more stable experience on a Mac, combined with the knowledge that Dreamweaver CS6 won’t suddenly stop working when Carbon is deprecated in Mac OS X 10.8 (Mountain Lion). However, the conversion work means that less time was available to develop or polish other features.
I’ve long felt that the idea of releasing more than a dozen complex programs according to a rigid timetable was impracticable. Photoshop, Illustrator, and Fireworks effectively sat out of the last upgrade cycle, which gave them 24 months to prepare for CS6. Dreamweaver hasn’t had that luxury. As a result, the Fluid Grid Layout and PhoneGap Build integration have some rough edges that could probably have been eliminated with more time. The message that I keep hearing from my contacts in Adobe is that moving to the Creative Cloud subscription model means that new features and improvements to individual programs can be released as soon as they’re ready. The problem is that to benefit from the updates, you need to switch to the subscription model. Anyone buying a perpetual licence will have to wait for the next full version to get the new features.
Getting new features as soon as they’re ready makes a lot of sense in the light of the speed at which the web is changing. What’s far from clear is how successful Adobe will be in persuading Creative Suite users to switch to the subscription model. It’s a big gamble for Adobe.