Known Participant

Question

Has Adobe abandoned CF in Dreamweaver CC?

Forum|Forum|12 years ago
June 18, 2013
3 replies
5523 views

Decided to try Dreamweaver CC today and it appears it does not support Coldfusion page? They have removed CF integration and Live view (even preview) appears to be broken for CF pages?

Can someone at Adobe explain if this is just a bug or is Dreameaver really not supporting design of CF pages?

This topic has been closed for replies.

R

Reed_Powell-ttnmOb

Inspiring

Please read this posting on House of Fusion. CF editing support is still in Dreamweaver CC, it just needs to be enabled. Doesn't seem to have all of the more recent tags, but I don't think that the latest desktop Dreamweaver did either. I am able to edit/code in CF with Dreamweaver CC after following the steps in the posting:

http://www.houseoffusion.com/groups/cf-talk/thread.cfm/threadid:64695

hth

-reed

Lawrence_Cramer

Inspiring

This isn't the first time Adobe has treated like the proverbial "red headed stepchild" so I guess we should not be too shocked. If you are standing on the tracks and hear the whistle blowing, getting closer and closer, then it should not come as a surprise when the train hits you! It's true that CF development continues, but Adobe's focus is more and more laserred in on the enterprise and government levels. CF 10 introduced many new very powerful features, but it also became even more difficult for a shared host environment. If this is their intent then I can see why they remove it from Dreamweaver - Enterprise application developers don't develop WYSISYG - they just don't.

All of this is why, when we were developing version 4 of Cartweaver we did a couple of key moves -

#1 we made absolutely sure it supported Railo!

#2 we pulled any dependency we may have had on Server Behaviors or Dreamweaver's support for dynamic development. Cartweaver still has a Dreamweaver Extension and works fine in Dreamweaver CC, but all it does is pretty much drop in all the files and set/write the Data Source information to a global variables .cfm file... that's it. Everything else is handled by the app itself or in the web based admin, and other features the user may want to add can be dragged in from the Snippets panel, which Dreamweaver continues to support. This way the Dreamweaver integration is not even needed, it's actually just as quick, if not quicker to manually copy the files over, open the global file and enter a few variables, save it, and move on. Dreamweaver not required.

I saw this coming a long time ago, although even I am pretty aghast at how far they went and how fast. They are even removing a lot of the essential ingredients for PHP support - I'm scratching my head over this one!

With the Edge products, the direction that Dreamweaver is going, and the whole Business Catalyst thing, I'm betting that for all but the most advanced enterprise application development Adobe sees the web and web development going the same way PostScript did. That some day, soon in their eyes, designers will be "printing" out web sites without ANY contact with or idea of what the code looks like, much less caring about it. That's been tried before. But who knows... Live, watch, learn, and adapt.

--
Lawrence Cramer - *Adobe Community Professional*
http://www.Cartweaver.com
PHP & ColdFusion Shopping Cart for Adobe Dreamweaver

Stay updated:
http://www.facebook.com/cartweaver
http://www.twitter.com/cartweaver
http://blog.cartweaver.com

BreakawayPaul

Inspiring

Well this is both annoying and exciting. Annoying because my office (a large federal government agency) is a CF shop, and we have a home-brewed CMS built in CF. My office's portion of the agency's webite is 60,000+ pages, and that's just a small portion of the total site. If CF eventually goes away, we'll obviously have to switch platforms, which means hiring some people who know whatever other language we change to, because all of our current people are CF people.

I guess it's job security though, because that's a LOT of coding.

But it's exciting too, because it'll be the opportunity for us to basically purge anything and everything Adobe. That includes all the copies of CS that our many developers use, along with the CF platform. Since my agency already has an instance of ASP.NET running on another machine, that'll probably be the direction we go, so I guess I should start reading up on ASP programming! It'll also make it a lot easier to find coders, because there are probably a lot more ASP developers than there are CF developers.

Fun times!

Hedge

Inspiring

WOW. As a CF person from the Macromedia days I am shocked Adobe has removed CF support in DW CC. That is just plain stupid. I just begrudgingly moved to CC because it felt like I had no other option since everything is going CC and now you remove CF support (your own language) from your main development product? I don't want to have to buy a seperate product to work with CF and use DW CC to do my layout work. If support for CF doesn't get put back into then I will be dropping CC all together and moving to alternative options such as Gimp and Eclipse. VERY disappointed long time customer!

Anit_Kumar

Inspiring

Hello,

The Support for ColdFusion is removed in Dreamweaver CC and later. Please refer to http://help.adobe.com/en_US/dreamweaver/cs/using/WScbb6b82af5544594822510a94ae8d65-7874a.html for documentation.

Regards,

Anit Kumar

G

GAlbers56

Participating Frequently

Yeah we all get that. The point we're all making is that the decision is a mistake. The single line on that page "

Note: Support for ColdFusion is removed in Dreamweaver CC and later." does nothing to help us who use DW to do development with ColdFusion (Again... ADOBE's own language).

No reason is given for the removal. No alternative is available. You say oh you can buy CFBuilder. Oh really? I can pay $300 more for another specific IDE that doesn't do eveything I need and then I need to create a new workflow.

And CF Builder doesn't support any of the new stuff from responsive design with the proper code completes or hinting etc.

Just saying it is depreciated doesn't help use users and developers at all.

Petro_O__Bochan

Inspiring

Yep, this is the bitter truth. Adobe has also removed support for CF includes if you still happen to open a CFM file and keyboard shortcuts are very buggy – half of those don’t work. I dare say the new CSS panel is barely a decent replacement for the bellowed CF support. Hopefully, we’ll see a ColdFusion10_Tags_for_DW.mxp and more for DW CC soon.

G

GAlbers56

Participating Frequently

I seriously can't believe this. Talked with support over chat and phone, confirmed that they have completley removed support. As they say "I understand your concern, but i would like to tell you that, this feature is a deprecated feature in Dreamweaver CC".

Not sure what Adobe's message is here other than to screw over it's own community. And as I see it, there are no other ways to create and work with ColdFusion files in any Creative Cloud program. The only one now is CFBuilder.

What is Dreamweaver good for now that it has been stripped of the two major coding lauguages (they also dropped .Net - odd they kept PHP). With the Edge tools, you can basically do most of what DW is good for. I guess some extra CSS support and an FTP manager...

Seems like one minor step forward with a whole hand full of steps backward. Adobe screwed up on this one. It's their own dang product. Just baffled.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded