For me who works with your software to make a living... here are some things I don't want Adobe to do.

1. Change the interface every time someone has an intellectual orgasm.




2. What in the world did you do with the excellent Find and Replace tool? The new one sucks royally!




3. Don't keep changing the interface and the button locations (the files panel refresh button. We who work with your software build up "muscle memory" on where things are. Please don't change stuff because you think it's cute.




4. This version of Dreamweaver is so bad (CC2017), I've went back to CC2015 and am getting work done and using the excellent Find and Replace tool!




5. Adobe's incompetence has cost me two days. Please get your act together, this was the worst upgrade since PS CS 6 and the crop tool debacle.

I often find vertical split screen helpful when comparing two similar files or features shared between two files. I find the horizontal split mode more difficult to use for comparisons as I cannot track code line for line.

I found no way to load a second file into the second pane. It only seems useful for loading referenced files like css or js. This may be intentional, but seems like an oversight to think that developers would not need to load two root level html/php/etc files side by side for comparison.

My suggestion is to provide developers the ability to choose what file they wish to open in what tab by dragging an open file tab into the second pane, and/or by right clicking a context menu and choosing from an option to open in tab 1 or tab 2.

When clicking anywhere inside an HTML tag in code view, DW highlights the entire tag in an ugly brown (using dark theme), but most tragically - changes all the text inside this highlight to WHITE - all of the code coloring is gone. So if I have attributes within the tag that were nice and color coded before, I now have to read through plain white text to quickly know what I'm dealing with as I add / edit them.

If my dark them is #222 background, how about highlight the tags with #444, and leave all my code coloring alone? Best of both worlds!

How did you guys not think of this? Who said, "Hey, let's remove ALL code coloring from HTML tags if the user clicks anywhere inside of it. AND let's not give users the option to turn it off. Awesome!"

I am enjoying much of the upgrade to CC 2017 however, Find and Replace performace has regressed. To be honest, DW's Find and Replace is the primary reason I have stuck with DW all this time, mainly due to its Regex capabilities and speed in this area. Prior to 2017, when performing a search (or find/replace), DW would simply list matches in the Search panel as they appeared however the app now hangs when searching for anything more than a simple term and if this happens, the search 'STOP' button is unavailable so there is no way to cancel a search if the wrong string was entered. As I mentioned, I often use DW for Regex find and replace searches, and frequently on directories with tens of thousands of files so it is becoming increasingly annoying to have to wait for DW to execute this task. I am not using an underpowered machine either... This issue is unique to 2017.

The 2017 release is clearly not ready for use.

Here is an idea: go back to the 2015 release...
add in the following features:
+ allow light/dark themes
+ add a panel to manage DWR extensions
+ update the interface (just a tiny bit)

Then, please fix the small list of bugs from 2015
=> initialing assets freeze problem
=> patch the "colorpreview" JS error on start up
=> patch the small list of other complaints up on Adobe since March 2015

DONE.

Presto! The new 2017 release would then be ready, everyone would be happy, legitimate progress would have been made and the development team would have an entire year to roll out new stuff and the time needed to test and confirm features!

What do you think? Vote for this!