Those who are print designers know that InDesign, Photoshop and Illustrator have been tightly integrated for some time now. Adobe has brought that integration model to Dreamweaver CS3, Photoshop CS3 and Fireworks CS3. Native Photoshop files are now fully supported by Dreamweaver CS3: drag and drop a Photoshop document into Dreamweaver CS3 and it goes right in, or select a piece of a file and paste it in. Dreamweaver CS3 brings up an Image Preview dialog box (pictured) to help optimize the file. If you need to edit, double-click the image and the original will open in Photoshop.
Read more on Dreamweaver CS3 Implements New Web Technologies…
Those who are print designers know that InDesign, Photoshop and Illustrator have been tightly integrated for some time now. Adobe has brought that integration model to Dreamweaver CS3, Photoshop CS3 and Fireworks CS3. Native Photoshop files are now fully supported by Dreamweaver CS3: drag and drop a Photoshop document into Dreamweaver CS3 and it goes right in, or select a piece of a file and paste it in. Dreamweaver CS3 brings up an Image Preview dialog box (pictured) to help optimize the file. If you need to edit, double-click the image and the original will open in Photoshop.
I’m not sure how this feature will function, and I worry that (1) the Image Preview dialog box will be cumbersome and (2) revising graphics will involve a lot of back-and-forth optimization all the time. I can’t know for sure until I work with the application, but those are just two concerns I have as I read the information.
I have a beef against Dreamweaver and its browser and validation checks. I don’t know how many times Dreamweaver 8 has said a webpage of mine will display fine in browsers, or that it is XHTML 1.0 Strict, only to find some problems when I test it myself or use the W3C Validator. Dreamweaver CS3 sports a new Browser Compatibility Check that looks great, but it seems to focus only on CSS browser bugs. Adobe goes further with the CSS Advisor, a new website it has that lists CSS browser bugs and solutions. Users can comment, rate bug entries, and add their own bugs. I think it’s a great step forward, though I also hope they took a look at the current validation checks and made sure they are accurate.
The last two major improvements in Dreamweaver CS3 are all about CSS, the web technology used to style and dictate webpage structure and design. Dreamweaver has done much to make CSS easier to implement in the past two versions, and for CS3 we are given CSS templates and CSS management tools. The CSS templates are solid: there’s a lot of choices for one-, two- and three-column page structures and they are well-presented in the New Document dialog box. When a technology is pervasive enough to be offered in templates like these, you know it has hit the mainstream. Dreamweaver CS3 also helps template users after the New Document dialog box: each template has comments in its code to help guide novice CSS coders. I think it’s great that Adobe went above and beyond by helping designers throughout the CSS process, rather than give them a bunch of templates and then leaving it to them to figure it all out. Maybe Adobe should have called this product “Dreamweaver CSS3″.
Manage CSS will be a benefit for intermediate and advanced CSS coders who know enough to move their code around in external files and multiple stylesheets. With Manage CSS, you can move styles around—from head sections to external stylesheets, or between external stylesheets—and you can convert inline styles to rules and move them where you need them. I’m always moving styles around from file to file, so I think this is a great help. I’m sure Adobe heard from many folks who felt the same inconvenience. I can’t wait to try this feature out myself and see if it solves the hassles associated with CSS authoring.
I’m convinced now that the Adobe-Macromedia merger was a good thing. I see good things happening in the old Macromedia software—which in my opinion were getting a little rusty in terms of interface and features—and Dreamweaver CS3 represents a substantial step toward the dream of WYSIWYG web design. Coding is still a necessary skill, but the templates and Photoshop drag-and-drop features alone bring designing for the web a lot closer to designing for print. In the future I will be looking at Fireworks CS3, which is another interesting development in Adobe’s embrace of web technology during the CS3 evolution.


Worldlabel is a source for equivalent Avery® labels sizes and free label templates for designing.
[...] Designorati : Dreamweaver CS3 Implements New Web Technologies (tags: dw dreamweaver adobe) [...]
I agree that this is a very minor refresh update (spry was already there in DW8 as was CSS-though now improved slightly).
I’m somewhat dissapointed with the lack of new features to call this version CS3. Drag and drop images from PS seems to be the only real new feature? (PLUS maybe browser compatability/bugs list on the adobe wesbite AND some more templates thrown in).
I look forward to when they upgrade the IDE UI and actually sit down and code what THE CUSTOMERS were asking for (quickly!-before they swith IDE).
Are you sure DW8 has the Spry capabilities? I use DW8 myself and there’s nothing like that included with it. It’s possible Adobe included some Spry elements after they purchased Macromedia (I bought Studio 8 before the merger).
I won’t be passing judgment until I start working with DWCS3 and get a feel for what it improves upon.
DESIGNORATI
BTW, I got to talk a bit with Kenneth Berger, Dreamweaver product manager, and I learned some news:
• Spry was not included with DW8,
• Validation tools have not changed from DW8 to DWCS3
The last one is a relatively minor thing—DW8 and DWCS3 validates pages pretty well. What drives me crazy is when my sites validate in DWCS3 but they don’t with the W3C validator. I don’t like having to validate twice.
DESIGNORATI
I think dreamweaver is a night mare! Far too complicated and difficult to time consuming to learn. I have used Golive off and on for a number of years with reasonable success. Building sites is not my life but something that I am required to do from time to time. Golive does not require you to be an “expert.” Sites are very easy to make and change, especially if you don’t have much time, and I am sure there are many others like me with other talents and interests. It takes more or less twice the amount of work, for example, to build a button, inserting in line frames or tables is a snap. It is not easy to for a secretary to manage minor changes in text pages. Take a look at http://WWW.LingualInstitute.com. I took me a day once I had done the graphics. It is very easy to alter…
I agree that Dreamweaver is not “easy”—it’s a complicated application and difficult to master. However, I would sooner blame the nature of web design than the application itself: web design involves complicated code work and the inevitably futile process of trying to get everything to display accurately on all browsers. Technology is getting closer but it’s still a bear, and Dreamweaver does a decent job of making it all easier.
DESIGNORATI