Enable code coloring in Dreamweaver CC 2017

Hi All,

We have started working on “Code Color Customization” improvements by adding support for customization of generic and language specific colors.

We have further stabilized the code coloring feature in our latest Prerelease build 15333.


You can refer to below thread for more details on code coloring customization improvements.
https://forums.adobeprerelease.com/dwalpha/discussion/467/dreamweaver-build-15333-is-now-available#l...

Please join Dreamweaver beta program from below link and try out the feature.

https://www.adobeprerelease.com/beta/9EB451B5-D2E8-46E5-AFA2-78C85442FFA2/participate/CD0C95AA-6274-...

Please go ahead and try out the build and let inflow your thoughts/suggestions. Looking forward to your valuable feedback.

Thanks


Dreamweaver Team

I didn't see it specifically mentioned in this thread, but this fine person has created a solution to the code highlighting and coloring problem that actually works:

http://leifhanson.info/2017/03/12/fix-dreamweaver-2017-code-highlighting/

It removes the highlighting altogether, which is exactly what I was looking for.

I complained about how stupid Adobe is for producing a software like Dreamweaver with such bad color coding at the first link below. Feel free to like that post and maybe they will get the point that they are producing useless software and a software like Notepad++ is beating them. Wake-up Adobe, otherwise I'm not wasting any more money on your useless software for my company. If any of you want to vote on my bug report go to the second link.

Forum Post:

Color Coding

Bug Report:

Color Coding – Adobe Dreamweaver CC: Feature Ideas

Considering an update to Dreamweaver CC2017 killed my software today, don't expect me to ever respect you as decent software developers. Your software is absolute crap. Freeware developers pay closer attention to their users than you do. Honestly, it's really sad how far you've fallen.

Truly stunningly obtuse of Adobe.  It is this type reason why we are moving our entire firm away from Adobe CC.  At one time we had 37 licenses, now we're down to 17.   Dreamweaver use to be a great aggregating platform, you've not made it into a nearly useless shell html editor.  With these color losses, it's not even a good html editor anymore!

amazing that this is even an issue and amazing that Adobe has yet to correct it. so what exactly are we paying for? this has been an issue since at least november of 2016 and still not resolved. truly disappointed.

One note to all the people complaining about the new version of DW CC 2017. Dreamweaver is a work in progress. It is NOT finished. If you have used the program for any length of time you know that the latest version is completely different than it was just two versions ago. It has many improvements as well as some aggravating bugs and irritations. But, do not assume that this is it. That there is no future to the app.

I have been working in the beta program for about 10 years now and we are very active and diligent in improving the program and tools we all want and need to use. I have made hundreds of feature requests over the years and many have been incorporated. But it's not because I have some secret channel to the developers. My requests were popular and voted on by many others in the program. If you want the program to improve and to get the features you want you need to get involved. Join the free public beta and make constructive comments and suggestions. Work with other web designers to make your thoughts known to Adobe. They are listening.

2017 is a vast improvement from previous version in many ways. No, it's NOT perfect, but nothing is perfect. Yes we lost some very popular or useful features in this build but many were lost for two reasons:

1. This is nearly a complete rewrite of the program. That takes a lot of work. They wanted it ready for October so many of the features were simply not ready by October to be released. Some, are still in development.

2. Development costs money and takes time. Certain features and workflows are prioritized and need to be developed first. Since this is a new version, many of the old features cannot simply be plugged in, they need to be completely rewritten. If you think your favorite feature is absolutely necessary, get all your friends and co-workers to join the beta program and VOTE for it! Convince all the current beta testers to vote for it! Start a letter writing campaign! Post on Facebook and Twitter. But be positive. Give logical arguments and be patient. There are lots of thing already in the pipeline.

I downloaded newest version 2017.0.1 and the colors of the default HTML have changed (again). How can I get it back to what it was in the default 2017 version? Current color is very bland and just doesn't work well for me. Please advise..

Clearly the color coding and options need a huge improvement, as everyone is mentioning..

This should still be PRIORITY #1 for the ADOBE team.

Can someone help? I followed the instructions and used GitHub's Lion Theme, but my inline CSS selectors and elements (sorry if I'm using the wrong terminology) are still the same color and it makes editing a nightmare. I'd like things like "font-family:" or "display:" in one color and their values ("Arial" or "inline-block") in another.

This is what it looked like using the Raven theme in DW CC 2015:

and this is what it looks like using the Lion theme in DW CC 2017:

Are the Coldfusion comment colors coming back? So weird to "upgrade" dreamweaver to the newest version only to realize it's actually a significant downgrade if you are a Coldfusion developer. Especially when they're both from the same company and they're not supporting their own product? Unheard of oversight and limiter of productivity since other pieces of code's colors get messed up too from lack of CF comment support I assume?

Hi Preran,

And what about code coloring for html, javascript, comments or other codes in Twig files?

or

It seems to be random....
Learn how you can customize the colors of your code elements in Dreamweaver.

= not working.
Any solution?