Dreamweaver CC has removed all support for editing ColdFusion CFM and CFC files, as well as removing default support for working with ColdFusion data sources, databases, bindings and server behaviors.
“As we have added new features, we have also begun reviewing the features that were integrated during the 15 years since Dreamweaver was released.
What we found was that some of the features support web technologies that are no longer relevant for most Dreamweaver customers.
We have decided to focus on modernizing Dreamweaver and streamlining the user interface by removing these older features. We have removed the Bindings, Server Behaviors, Components, and Databases panel, as well as Spry, Browser Compatibility Check, and a few others.
Some of these items will be available as extensions for customers who still rely on these features.
As we move forward we will continue to focus Dreamweaver on modern web standards and technologies including HTML5, jQuery, and more.”
I guess Adobe considers ColdFusion to be no longer modern, nor relevant.
Personally, I think that removing CFM and CFC support from Dreamweaver CC would be akin to Microsoft removing .NET and ASP support from the latest version of Visual Studio.
Then again, Adobe removed ASP and .NET file support from Dreamweaver as well, so I suppose ColdFusion developers shouldn’t feel too slighted.
An editor that can’t edit files…
Worse, this brilliant design move effectively positions Dreamweaver as an oversized, over-priced HTML and CSS design tool.
One that’s totally unable to create and edit the common file formats used on many, many, many web sites.
According to Adobe, with Dreamweaver CC you can code faster with new visual editing capabilities, including CSS Designer and the updated Fluid Grid Layout interface. With it, says Adobe, you can generate clean, web-standard code.
Problem is, you can’t save any of that wonderful code as a CFM or ASP or ASPX or JSP file.
Okay. That’s not quite true. You can edit the extension and save your HTML as a CFM file. But if you try to reopen that file again using the IDE’s file browser, Dreamweaver CC will throw you back into CS6 and open it there.
A web file editor that refuses to edit web files.
What genius came up with that concept???
The only official way to work with the files associated with Adobe’s own server product is to get CF Builder, which, of course, is not part of the Creative Cloud subscription.
That’s yet another $300 per developer seat, yet another program to purchase and maintain, and yet another IDE to learn and use.
At the very least, Adobe needs to bundle CF Builder into Creative Cloud.
And they need to do it today.
Why? Well, we lost Fireworks. We effectively just lost Dreamweaver. And the writing’s on the wall for Flash.
And because of all of those things, that monthly Creative Cloud subscription fee is looking less and less valuable each and every day.
ColdFusion Server is already viewed by outsiders to be a staid, antiquated and overly expensive web development platform.
So of course the solution to this perception is to place even more obstacles and roadblocks in front of the companies and developers who might consider using it for a project.
Adobe needs to decide.
Either they’re behind ColdFusion and they’re going to support its development across all of their products… or they simply need to tell us that they’re are dropping it and let us all move on to .NET, Python, Ruby, or some other “modern” web development platform.