lkpmission.blogg.se

That said, you actually can use Dreamweaver CC for CFML development. I know it’ll take effort, but you’ll really be better off for having done so.

But I’ve not used Dreamweaver for CFML for years, and for those of you who are still using Dreamweaver for CFML development, I’d take this latest change as a long overdue nudge to find a better IDE. I recently worked on a project which made extensive use of jQuery and jQuery UI, and Dreamweaver worked perfectly and intelligently and usefully. I use Dreamweaver extensively for what it does best, client-side work. In fact, even Brackets now has a work-in-progress community based CFML extension. I understand that many don’t like ColdFusion Builder, I’m not a major Eclipse fan myself, but ColdFusion Builder is a far better CFML IDE than Dreamweaver ever was, and so that’s the focus going forward. And so, recognizing Dreamweaver for what it was, the ColdFusion team opted to build ColdFusion Builder, and that’s where they are putting their efforts. And over the years that has frustrated me far more than Dreamweaver CC reducing ColdFusion support does. There was one release (MX maybe?) that added some decent CFC support, but honestly, there has been no real Dreamweaver support for ColdFusion since then, just more of the same. Even back in Allaire days when I worked with the then Macromedia Dreamweaver team to add ColdFusion support, the support was minimal at best. But, to be brutally honest, I had given up on Dreamweaver support for ColdFusion a long time ago because Dreamweaver has never been a true ColdFusion IDE. As I said, this was overdue.Īnd so, yes, Dreamweaver now has less ColdFusion support.

Do you know that DW6 still had dialog boxes with Netscape Navigator icons in it? Seriously, Dreamweaver was suffering from ongoing feature addition while nothing was ever deprecated or removed. And personally, I like the Dreamweaver focus it’s long overdue. Would I like Dreamweaver to do it all? Sure, but that’s not practical, and so they made the trade-offs and decisions that every Product Manager has to make. Likewise, the Dreamweaver team has to focus on what’s important for them and their numbers, and their client-side focus makes sense to them (and, actually, to me, too). The ColdFusion team has to do what they think is best for the ColdFusion business, and that includes a CF10, a planned CF11, an upcoming conference, and, yes, ColdFusion Builder. Every product team has to do what they think is in the best interests of their product. It is true, the Dreamweaver team has significantly reduced support for ASP/ASP.NET, JSP, and CF. And so this is a chance to try to set the record straight. But, as usually happens, facts and realities get misconstrued amidst the angst and hand-wringing. This has upset many in the ColdFusion community, and understandably so. And among the removed features is some of Dreamweaver’s ColdFusion support.

To support that focus the Dreamweaver team made a decision to deemphasize other areas of functionality. The release of Dreamweaver CC brought some important enhancements to the product, along with a renewed focus on client-side development and technologies.