TUAW Review: Dreamweaver CS4 beta
Adobe Dreamweaver, for better or for worse, is probably the most mature integrated development environment for website building for the Mac. Professionals might be supplied with Dreamweaver through their company's site-license; beginners might get Dreamweaver on the recommendation of a friend. Hard-core coders have their favorite text editors and IDEs. This review is not for them. To be clear, I use Coda and TextMate almost exclusively for web development. This review is for people who use Dreamweaver primarily as a WYSIWYG HTML editor (as much as that makes me cringe). But that's what Dreamweaver does best.
The public beta of Dreamweaver CS4 dropped on Tuesday, and I'm going to show you what's new and different about Dreamweaver CS4, and if it's worth the upgrade.
Weavin' your dreams, after the jump.
First of all, Dreamweaver CS4 is enormous. 509MB of sweet, sweet application. Dreamweaver CS3 was a mere 366MB. Coda is just a wisp of a thing at 52MB. TextMate is practically anorexic at 30MB. For what CS4 provides over CS3, I can't really say that the extra 200MB are doing much. Hopefully that's just test code and cruft that will come out before the final version is released.
Looking at the interface, it's not significantly different than the last version of Dreamweaver (true, it's just as customizable as the last one, too). Palettes are organized similarly, with one major difference. The Insert palette now lives down with the rest of the palettes, instead of as a toolbar above the workspace.
One nifty addition is a small tab-like toolbar above the workspace that shows documents (like stylesheets and scripts) linked in the current document. No need to thrash through your document structure to find a buried CSS file: it's listed right next to your open document at the top.

Before I switched to Coda, I used Dreamweaver (in its various iterations, including CS3) since Dreamweaver 3, I think (note to readers: I am old). I'm very familiar with how it works. As I grew in my career, I moved away from the WYSIWYG development process, and started coding by hand. Dreamweaver was a fair-to-middling text editor, and the code view's maturity as part of the Dreamweaver product definitely shows in CS4.
Still, certain features like Coda's terminal integration and visual CSS editor would be a welcome addition to Dreamweaver.
Another addition is the Code Navigator, a contextual menu that shows you the CSS properties of the item you clicked. No more switching to Firebug to find out what styles are assigned to a particular object. A helpful (Firebug-like) addition to this pop-up might be to show which styles are overridden by others.

For me, the most anticipated feature is Live View, a preview environment (much like Coda's) that renders the web page as if it was in Safari, Camino, OmniWeb (thanks commenters!) or the raft of other browsers that use the WebKit engine. The disappointment is this: the Design view (that is, the WYSIWYG environment) doesn't use WebKit, but the same rendering engine as the last version of Dreamweaver. As a result, Live View is given a strange "separate but equal" preview status. I think it would be great to make WebKit the rendering engine for all of Dreamweaver's WYSIWYG output, furthering the push toward design for standards compliance.
Even so, testing is at least easier, obviating the need to switch from IDE to browser and back again.
Overall, Dreamweaver is a mature HTML development environment. The changes to the environment shouldn't have to be radical to be useful. In fact, Adobe is helping the development community push more towards standards compliance, which is great for everyone: developers and visitors alike.
Share
Adobe Dreamweaver, for better or for worse, is probably the most mature integrated development environment for website building for the...
Add a Comment
Now it is very easy to create theme in dupal using our dreamweaver extension
Dreamweaver Drupal
http://dreamweaverdrupalthemeextension.blogspot.com
is the site
Now it is very easy to create theme in dupal using our dreamweaver extension
Dreamweaver Drupal
A great discussion and fascinating to see how the design people fear the developers and vice versa. Even if you donât need each other now, you will soon. Designers: like it or not, code and left brain mega-complexity are the web and thatâs the way it will always be. Websites are getting more interactive and complicated all the time, and clientsâ expectations will continue to follow this trend.
In the late 90âs you could get away with exporting some Photoshop slices into Dreamweaver and hack up a quick website. Unfortunately, this is not going to work in a modern website. Modern websites are database driven and have the content separate from presentation. This is necessary to allow for easier maintenance, consistency of style, repurposing into different formats, etc. It wonât be long before even small businesses come to expect to have to enter in their data in one location and have it sync with their contacts, financial data, print materials, website, etc.
I'm a graphic designer who does everything from brochures, posters and catalogs to full e-commerce websites. I've been designing websites steadily since around 1997. I know HTML/CSS very well and work with PHP, ASP, SQL, etc. Dreamweaver was my tool of choice since it was version 2. Up until not long ago, I absolutely swore by it. That was before I discovered tools like Firebug for Firefox and open source cms's like Joomla. Dreamweaver is trying to keep afloat with the old ways, but if you take a look at these tools youâll see that Dreamweaver is left in the dust.
At this point, Dreamweaver is good for no one, beginners and pros alike. For example, give a beginner Joomla and a decent template and theyâll have an entire website up in a fraction of the time it takes with DW. And one that Dreamweaver couldnât even touch without a lot of hard programming.
Graphic designers need not fear (except for free trade agreements, which we all should be VERY scared about). Of course you are still needed, and youâre right... most developers canât design their way out of a paper bag. But unless you start learning some good coding practices soon, youâll soon be lucky to be asked to build a website by your 8 year old kid. But donât get mad, network. Send that PSD off to someone who can put it to work. Or scratch your head to learn and try and juggle 3 different careers like me!
I agree with Van that at the end of the day it's whatever gets the job done the way the client wants it and on time. If you find coding tools etc your thing then stick to that. But don't dismiss the likes of dreamweaver because its ide is very well suited and adaptable.
regarding the review itself - robert was honest about where he came from and didn't outrightly dismiss it. Besides it's a mini review of a early beta and not a fully bloated review.
also there's no need to be so polarised. Good clean code is a good thing, but at times rough code with a great design is better than beautiful code with a rubbish design.
If you're so clearly biased, then YOU SHOULDN'T REVIEW THE PRODUCT. This review is worthless.
May 29 2008 at 10:07 PM Report abuse Permalink rate up rate down ReplyIs it just me, or did this review read more like a commercial for Coda than a review of Dreamweaver CS4?
May 29 2008 at 8:01 PM Report abuse Permalink rate up rate down ReplyIf I worked for you, and you used "LOL" in a sentence, I think I would quit.
May 29 2008 at 6:21 PM Report abuse Permalink rate up rate down ReplyYeah, i'm gonna agree with those users on the lines of - who is it for?
Web Pro's - I pray not.
Consumers. Maybe there is a need for something a little more robust than iWeb, but way simpler than Dreamweaver to fill that void.
Web designers. If you need to make lots of sites as a designer... well then you're doing the job of a developer and calling it something else. Why wouldn't you either a) team up with a developer. b) Learn HTML + CSS and use textmate (or whatever your choice or text editor is) like everyone else.
There are not many good designers that can code a good website (ala Jonathan Snook).
Unfortunately having been in the business for long enough the fact of the matter is there are lots of clients paying plenty of good money (i've seen hundreds (of thousands (UK Pounds)) for websites that are designed by a flashy photoshop user and coded by some clueless dreamweaver 'web developer' who doesn't know how to do anything outside of clicking the buttons in dreamweaver.
And I doubt it's going to change. If you're a client, you don't know HTML (or even good design most of the time) so how are you going to know a mediocre dreamweaver user from a talented web developer?
Okay, that's my bemoaning over. My recommendation is you use the money you could spend on buying or upgrading to dreamweaver on good HTML + CSS books!
I couldn't agree with you more!
May 30 2008 at 10:43 AM Report abuse Permalink rate up rate down ReplyFor the past few years I've been developing new types of web authoring tools called StackSite to help advance website accessibility, graphics, and navigation. Basically, these tools with little effort, allows beginner Web Authors to advance web Developers the ability to freely create graphically rich accessible websites. Their not available yet, but I hope to have a set of them available for Dreamweaver by the end of the summer, and other programs later. Anyway, Dreamweaver's new beta seems to be on a fast past in the right direction. Something I was hoping they would do when Adobe took hold of it. They also seemed to preserve what really made Dreamweaver successful, which is a amazing group of people developing and supporting each new version. The speed question and concern above is interesting. I can't speak for them, but whenever I'm developing software, I first try to get it to work, then I change and try different things to get it right. Then I work on getting it fast and faster. The new Dreamweaver will require a G5 or intel Mac. I'm guessing more the latter. I personally don't know about either, because over the year I was unsuccessful with obtaining any G5s or Intel Macs being tossed to the Garbage to work with. Anyway, I know many web developers use Vmware or Parallel to test ie browsers when developing a website with a Mac. But would U guys run the Dreamweaver windows version using Vmware or Parallel to use my tools or at least until I can get some Intel macs to work with?
Robert Stack
Zoshe Foundation
http://www.zoshe.com
Have they gotten Dreamweaver to actually make valid webpages yet?
May 29 2008 at 2:28 PM Report abuse Permalink rate up rate down ReplyHot Apps on TUAW
Deals of the Day
more deals- Refurb Apple MacBook Air Laptops: 12" 64GB SSD for $699 + free shipping
- JVC Motion Sensing Clock Radio with Dual iPod Docks for $55 + free shipping
- Apple iPhone Headset with Mic for $4 + $2 s&h
- miFrame Picture Frame Dock for iPad for $64 + $8 s&h
- Refurb Apple iPod nano 8GB MP3 Player for $99 + free shipping, 16GB for $119
- Hannspree Apple-Shaped 28" 1080p LCD HDTV for $270 + free shipping
Software Updates
more updates- EFI Firmware Update brings Lion Internet Recovery to 2010-model Macs
- OS X Lion 10.7.3 released with Safari 5.1.3, Wi-Fi bug fix
- Aperture updated to 3.2.2, addresses Photo Stream issue
- Apple updates Keynote to address Lion issues
- Google Search app gets new look on iPad
- Apple releases Apple TV Software Update 4.4.3



53 Comments