You can get hold of the beta releases and view example screencasts at Chris’ site – xtnd.us – and make sure to send him some love for really kicking tail on these extensions. If you’re interested in MooTools and/or YUI support, he’s taking requests – and it also appears that a Mochikit extension is in the works as we speak.

Although Chris has noted an ExtJS extension is current on hold at the xtnd.us site linked above, it may be (as noted in the comment threads here at Ajaxian) due to the fact that a Windows ExtJS extension for Dreamweaver MX 2004 was built out by the Spket folks, which they’re planning to port up to CS3 soon.

Chris: here’s a virtual high-five from the DW team for your innate coolness in jumping on this project so quickly for DW developers worldwide. We’ve got some plans in the works in these regards ourselves, but this is a solution that the DW/Ajax development community can use right now, today. Hot damn. You rock, my man.

And in case I wasn’t direct enough… this extension is a free download, no less. Go get it!

Check out more details on Nitobi’s Complete UI 2007, which is easy because they’ve got a trial version you can play with too. I think you’ll be impressed. This is great stuff- kudos, Nitobi!

Yes, this list will likely be controversial to some – particularly if you’re relying on one or more of these features today. However, the team decided to publish this list early- to both help you prepare for the changes, evaluate other options and adjust your own workflows. Most all the deprecated features either have become more code-centric workflows in other dedicated IDEs/environments (JSP, .NET), or had visual user interfaces that enabled DW developers and designers to generate poorly-formed code in the back end (Layout Mode and Timelines, for example) – something the team takes very seriously.

My personal opinion is that this move will really free up resources to do a LOT in the next few releases of Dreamweaver, and start doing more ‘revolutionary’ feature and architectural work as opposed to strictly ‘evolutionary’ features and polish. If any of the features to be removed give you pause, post a note, and it’s likely we can suggest alternatives for the post-CS3 era to help smooth the transition.

Personally- I hope that when we’re able to talk more about what’s being planned for the next version (or two) of Dreamweaver, the tradeoffs made here will be more than justified in your eyes. But that’s a subject for a much later date with a lot more details- so keep posted.

CSS Sculptor is an elegant Dreamweaver extension that helps you quickly build a customized CSS layout, starting with 30 of the most popular variants- elastic, liquid and fixed layouts, 1-3 column configurations, and much more. The interface doesn’t just help you choose from a completely ‘pre-canned’ design, but gives you a clear starting point to help expose the CSS and attributes required to customize a layout for your specific project and design- helping educate users on CSS best practices as well as expedite their development. Win/win.

The community is taking notice, too- you can read Jeffrey Zeldman’s aforementioned take on CSS Sculptor (great comment thread, too), articles from InfoWorld and Website Magazine, and of course Eric’s own take on CSS Sculptor at his personal weblog. Don’t forget to digg the news, as well.

Great product from two heavyweights in their respective spheres of influence, and yet another reason why Dreamweaver’s such a rich product to work with- the extensibility/third-party developer community around Dreamweaver just plain rocks! Awesome job, guys.

(Side note: I feel compelled to put a little plug in here for the standards-compliant CSS Layouts that ship with Dreamweaver CS3 for the record – which are also great sources of education on CSS design/layout best practices – heavily commented, and coded for Dreamweaver by The Web Standards Project’s Stephanie Sullivan.)

This screencast covers installation and general functionality of the extension, and should get you up and running quickly. From there, it should be a snap to start leveraging your existing XHTML/JS/Spry/CSS skills to write sweet desktop apps using the AIR runtime.
Enjoy!

Between August 24th and 28th Adobe will be shooting on-camera interviews of Adobe software enthusiasts, talking about the software and work they love, for a video to be shown at the MAX conference in Chicago. If selected, you’d only be needed for one of those days (individual shoots will range between 1 to 2 hours maximum, FYI). If you want to be considered for this big-screen appearance you just have to drop a note to ‘adobecast@yahoo.com’ providing:

• Your occupation
• What Adobe products you use
• A recent photo or two of yourself
• Contact information

If you’ve got an interesting story to tell – especially if you’re using Dreamweaver, of course (as I’m biased that way) – drop a note to the production email account and get yourself in the running. I’m really looking forward to seeing the final piece, as well as the blooper reels…

The comments in the Ajaxian article’s thread are interesting- I was pleased to see there’s certainly a contingent of folks within giving a thumbs-up to recent release(s) of DW, along with the expected ‘WYSIWYG editing is for dolts’ responses, the latter of which Dion’s question may actually be a valid one for. My answer is simple- I’m a designer who likes code. I spend most of my time in DW’s code view exclusively, and occasionally do quick mockups/proof-of-concept work with the WYSIWYG tools. DW CS3 is speedy and nimble for me (particularly when compared to the glacial performance of MX 2004 and perhaps DW 8), and I have no problems using it regularly as a code editor – again, with the occasional drift into the GUI-driven features if I’m doing quick tests/proofs.

Now I can’t (and won’t) argue with those who simply prefer completely stripped-down tools like Notepad or TextMate/BBEdit – I occasionally do as well (have been a BBEdit user longer than a Dreamweaver user), and understand the minimalist approach – but the extended features of DW (along with it’s recent updates for code-centric folks) are way too much to discount wholesale just for percieved street cred on my part, or the spectre of old (and now- largely resolved) code trust issues in the visual editing features.

Anyway, I’d be interested in your comments, suggestions and opinions on this, too- as Dreamweaver is a app very near and dear to my own workflow I’ve also got strong (and yes- potentially biased) opinions upon it myself. Sound off below, why dontcha?

The Adobe web team’s David Hatch talks a little more about the update in this forums thread, and notes that this is the first, interim release of several updates the web team will be making to the Exchange app based on extensive user research across the Adobe product communities they’ve been doing over the past few months. David’s also noted some current issues with the updated Exchange UI – be sure to visit the thread and let the web team know what you think – and of course report bugs you run into so they can be addressed downstream.

(Note: comments are closed in this post, as discussion is being centralized in David’s forum thread instead.)