New Idea: Scrap 2017, Go back to 2015 CC, fix old bugs, add in a few new features
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!

14 comments
-
Dreamweaver User Since v3 commented
CC 2015 with the GIT panel would be perfect, the Brackets code editor is just HORRIBLE, laggy, glitchy and terrible.
-
Dreamweaver User Since v3 commented
Add GIT to CC 2015 and I would''t even bother with CC2017 OR 2018. I still prefer the old code editor in CC 2015.
-
Christian Zagarskas commented
well... its been 1 LONG year and DWR 18 "looks" like its ready for use. After 140 bugs that did not exist in the 2015 release were finally patched in 17 and 18 (good job on that) looks like we are almost back to a sane DWR product... (now if they could just put code coloring back to the way it was then 2018 would be an improvement)
Seriously though, check out DWR 18, its not bad... there is even a GIT tool and the Find tool is working properly again,
-
Anonymous commented
-
Anonymous commented
Christian Zagarskas is totally right,separe dreamweaver into two distinct products should be really great.
As a PHP developper i only need these features :
- Projects managment with FTP (i use dw only because the others code editors doesn't have a similar tool)
- Code fragments
- Find / replace
- LintingI never use live view and all designers features, unfortunaly dw is loading all of them...
You should split developpment with a lightweight code editor for developpers and wysiwyg for designers, it could be the best idea i seen here.
Maybe more simplier : let us compose your own dw by enabling / disabling exsting features. -
Izbuh commented
The big problem is that 2017 version is not more Dreamweaver, is another program/app.
Adobe has urgent need to remove old Macromedia's customers and I think this version has been created to achieve this goal. -
Jake commented
"We have a lot of new features in Dreamweaver"
None of which I want or need.
"we have upgraded already existing features for more ease of use"
You completely broke find + replace, then added the original functionality back in under a different keyboard shortcut, which can't be rebound to the original shortcut to prevent accidentally opening the new, featureless find.
"we feel that they have changed for better"
I really don't care what you feel. I'm the one paying for this product.
"We are still doing the same things that CC 2015 was doing but in an improved way."
The avalanche of "put it back the way it was" comments throughout this feedback site says otherwise.
"Hoping to hear more constructive feedback rather than generic criticism."
Well I'd like to see some constructive improvements so I guess none of us are happy.
-
Pete Batin commented
"We have a lot of new features in Dreamweaver since the earlier versions and we have upgraded already existing features for more ease of use."
That either do not work or we as paying customers are being used as guinea pigs to bug test for you.
"I agree that with this new update, the workflows that were present earlier have changed a little bit but we feel that they have changed for better."
Not based on user feedback and major emphasis placed on "*WE* feel that they have changed for better"; well you would say that, you're defending a substandard product that is not fit for purpose.
"Hoping to hear more constructive feedback rather than generic criticism."
You've had the benefit of our feedback, for free, too much, this product is Beta at best. We're still expected to pay the same price for this product and at the same time be your bug testing department, I'm not getting paid for this service, nor am I receiving a discount on my team subscription. I'm past the point of being constructive, my patience has been stretched too far and I believe others have and are feeling this way too. You can't even provide us with a date of when you're going to be releasing updates for bugs that have been supposedly fixed, until there's an update there's no proof of this.
At least it would be decent of Adobe to email CC subscribers with an apology for this product and a promise that everything that can be done is being done and in the meantime here's a gift from us to you X% discount off your subscriptions until we've fixed it.
-
Hi,
Thanks for sharing your feedback.
We have a lot of new features in Dreamweaver since the earlier versions and we have upgraded already existing features for more ease of use.I agree that with this new update, the workflows that were present earlier have changed a little bit but we feel that they have changed for better. We are still doing the same things that CC 2015 was doing but in an improved way.
Let us know if you are facing any issues with the functionality, we did be more than happy to help. Hoping to hear more constructive feedback rather than generic criticism.
Regards,
Niharika Gupta
Adobe Dreamweaver -
Jake commented
Latest update makes this idea even more necessary
-
Giosa Studio Web commented
I'm uninstalling 2017 version and switching to 2015, no more time wasting for me.
-
Giosa Studio Web commented
Adobe, I'm not a beta tester, I use this software for my work. I don't want to spend my time looking for work-around to resolve your bugs.
-
Daniel Journo commented
Never going to install another update.
-
Christian Zagarskas commented
Please Split Dreamweaver into 2 products - one for Coders and one for Designers
=> https://forums.adobe.com/ideas/5142
PS: the permanent fix I found for EVERY single bug up here was to just switch back to CC 2015. Ahhhh... everything back to normal.