Sure, the situation regarding CF and DW stinks, for those who were/are fans of both. But for the sake of some readers, I will add some more perspective to this thread, which your three 2019 comments have resurrected from its originally posting in 2013 and other comments mostly from 2014. I realize you are putting this wish out there for Adobe to consider, and we could leave it at that. There are no signs at all of CF support ever being returned to DW. Karma, I can concur with your observation that there are no seeming plans for Adobe to drop CF (indeed, they have offered a form on the CF portal to signup for the CF2020 prerelease, when it comes out).īut as for CF support within DW, that seems a christmas wish of yours that will never be fulfilled. The problem is, is that Dreamweaver is just a superior editor to Coldfusion Builder, so I wish Adobe would just bite the bullet, and reintegrate support for Coldfusion into the former. I just think that Adobe are trying to push developers towards Coldfusion Builder. In the US, the Coldfusion Development market is strong and I have seen no hints to substantiate this claim. I really cannot understand why Dreamweaver is not built around Coldfusion? And for those who say that Adobe are planning to drop Coldfusion, I really don't think this is the case.
ADOBE DREAMWEAVER CC EXTENSIONS CODE
It was such a relief to see built in support for Coldfusion with proper tag/function intellisense and code colour formatting. Even, if you create a new interface and use main.scss to try and create a custom style sheet for CFML, it doesn't really work, because there are not enough selectors to properly format the language.Īlthough, I will continue to work on the ZXP extension, I have decided to uninstall Dreamweaver CC 2020, and reinstall Dreamweaver CS6. None of the interfaces properly colour format CFML. So, I had another look at Dreamweaver CC, and noticed that there is another issue, related to Coldfusion.
0 kommentar(er)
