Skip to main content
Preran
Community Manager
Community Manager
November 20, 2018
Question

Dreamweaver 2019 roadmap

  • November 20, 2018
  • 9 replies
  • 5437 views

Hi all,

There has been considerable speculation about the future for Dreamweaver on this forum, and elsewhere. The product team has published a blog post to allay rumors around this topic.

See What’s Coming to Dreamweaver in 2019? | Adobe Blog where the program manager for Dreamweaver has provided guidance on what's coming up in later versions of the software.

Thanks,

Preran

This topic has been closed for replies.

9 replies

Legend
December 21, 2018

I cannot comment on that Blog - it keeps redirecting me to a 'corporate login' whatever that is.

If I could have one thing for Xmas it would be for the old code editor to be restored .... Like thats happening 

Other points:

1) Live view needs a lot of  work, its hard to select things sometimes (if you can select them at all) - I spend majority of time in code view but I still use design view a bit with custom design-time stylesheets to make pages 'workable' in design view. I never use live view its too frustrating.


2) If Adobe were hell bent on the CSS Designer Panel, why couldn't they have retained the old CSS panel also and given users the option of choosing which style of CSS panel they want to use, one being more of a coders panel and the other more of a designers panel - I thought the whole concept of Dreamweaver was that it is for coders and designers? For a while the old CSS panel was hidden and clould be restored so we were half way there anyway!!

3) There are still problems with the 'apply source formatting' tool, for example in Tag Libraries if I set P tag;  Line Breaks: Before and After Tag and STRONG tag to : No Line Breaks, it will still put the closing P tag on a separate line in this example:

<p><strong>PUT TWO CLOSING TAGS NEXT TO EACH OTHER AND SOURCE FORMATTING WILL PUT THE SECOND CLOSING TAG ON A NEW LINE REGARDLESS OF YOUR SETTINGS IN TAG LIBRARIES</strong></p>

This is not an isolated glitch it happens right across the board as far as I can see for all tags when two closing tags are directly next to each other - its wrong and its NOT how it works in CC 2015.

4) I don't know where the dev team are with fixing issues with the 'apply source formatting' tool and PHP code either? It was breaking PHP code in some instances, it looks like some issues have been fixed although I see no confirmation of the fixes?

5) Source formatting is a staple feature of any decent code editor, since the Brackets integration this function has been, and still is totally untrustworthy to use.

Quite honestly, I doubt you would hear many complaints if the integrated Brackets code editor was ditched and the old code editor restored.

Paul-M - Community Expert
Preran
Community Manager
PreranCommunity ManagerAuthor
Community Manager
December 21, 2018

Thank you for your feedback. I have shared this post with the product team, so it's OK for you to post here if you are having issues commenting on the blog post.

Thanks,

Preran

Legend
December 21, 2018

Thank you for your feedback. I have shared this post with the product team, so it's OK for you to post here if you are having issues commenting on the blog post.

Thanks Preran

Paul-M - Community Expert
B i r n o u
Legend
November 27, 2018

<joke>be careful, the balcony generally only supports two places</joke>

pziecina
Legend
November 27, 2018

https://forums.adobe.com/people/B+i+r+n+o+u  wrote

<joke>be careful, the balcony generally only supports two places</joke>

I'm in the royal box, </end joke>.

Seriously though, someone has to complain when they think features are missing. Even though I know Dw cannot change it's current plans, I still think that if a user has to use another program for anything except creating assets, then that feature that makes the 'other program' a necessity to use, should be considered for inclussion into Dw.

Legend
November 27, 2018

pziecina  wrote

https://forums.adobe.com/people/B+i+r+n+o+u   wrote

<joke>be careful, the balcony generally only supports two places</joke>

I'm in the royal box, </end joke>.

DW obviously needs a much bigger balcony

pziecina
Legend
November 26, 2018

Just to clear thing up, this is what I posted in the comments section of the Dw PM's blog post -

"What are Dw's plans for none bootstrap, and none pre/post-processors users.

Everything included since 2014 has been for a single workflow, leaving anyone who wishes to build sites/apps with no option but to use another code editor. Simple items such as css prefixing require pre/post-processor use. Css grids and flexbox have no starter pages or visual workflows, git is for small teams or individuals, with no method to set and restrict privileges visually in Dw.

The web has moved on, and whilst Dw is finally realising that features must be updated on a regular basis, (bootstrap version) many other features are no longer supported or are outdated. Some examples are css designer, never updated (requires a complete rethink), debuggers both php and javascript are missing (can use browser dev tools, but even free code editors have them built in now).

Finally, just what does a designer who wishes to code mean?

It can apply to someone just building a page with html and css only, or someone who is part of a large team building an app with terabytes of data, for a very large organisation."

I will also repeat what I have said many, many times before - " I am not anti bootstrap" , I am against the single workflow that Dw now offers its users, which is bootstrap.

My apologies to Preran for it being necessary to lock his post.

Everyone can comment what they like, but please do not turn my posts meaning around to mean something I have not said.

Legend
November 26, 2018

Not sure what free options there currently are if youre not prepared to look beyond open source  front end frameworks for building your website and if you have or you are then you probably have no necessity at all to use one.

I see it as do you want to spend most of  your time managing and reverse engineering generally bloated code or working with something a bit more refined. Its a case of educating those that dont know the difference because unfortunately they start of with bad habits and never escape them.

Its going to be difficult to change the perception if you dont know any different, unwilling to take the leap of faith for those in it for the long term, or those that are just casual users who needs to be provided with simpler options.

pziecina
Legend
November 26, 2018

osgood_  wrote

Its going to be difficult to change the perception if you dont know any different, unwilling to take the leap of faith for those in it for the long term, or those that are just casual users who needs to be provided with simpler options.

The problem, (or one of them) is that Adobe no longer offers any means of demonstrating how to create anything now. We used to have css advisor, and the developers connection, but these have 'fallen by the wayside' as far as user posted examples goes. Now there are a few short videos to help users get started, but nothing I can see that goes beyond creating anything to help with the basics.

Educating anyone is not the main reason for the user to user forum, as much regarding the html/css why of doing something cannot be said. Even books on the subject leave many questions unanswered.

ALsp
Legend
November 23, 2018

Sadly, though, there is not much commentary, which bears out my assertions that Dreamweaver is slowly being killed. That Adobe seems to want to fix it, the sad truth is that it has become just a wrapper for Bootstrap... and that is what is going to kill it.

pziecina
Legend
November 23, 2018

You might, (and might being the operative word) get a reply posting in the articles 'comments' section, but don't hold your breath .

ALsp
Legend
November 23, 2018

pziecina  wrote

You might, (and might being the operative word) get a reply posting in the articles 'comments' section, but don't hold your breath .

I did, a couple of days ago. Fortunately I did not hold my breath

Inspiring
November 21, 2018

Peran,

I followed you link in FF and got a white page. I tried Al's suggestion of using Edge, and I got a white page. And I am signed into the DW forum.

No biggie, but thought I'd mention it.

Chris

Preran
Community Manager
PreranCommunity ManagerAuthor
Community Manager
November 21, 2018

The concerned team is working on this page. I request you to wait until I receive confirmation about the page being fixed.

Thanks,

Preran

WolfShade
Legend
November 21, 2018

Is the blog also Jive?  This is what happens when you outsource things that should be done internally.

V/r,

^ _ ^

ALsp
Legend
November 20, 2018

Commenting does not work. So, I'll comment here.

In an offline discussion with the Dreamweaver and Exchange Teams, it has been stated to me that Adobe will fix the local configuration bugs with misnamed user configuration folder in English International installations. This bug affects extension installation using Adobe ExMan (either in Command Line/Terminal Mode or with a visual front end). Also noted is that Adobe will include an extension installer as part of the Creative Cloud Desktop App.

The Dreamweaver Team needs to come to its senses and treat Bootstrap as an accommodation, rather than a defacto page layout feature. Optimally, an assortment of quality starter templates that allow a user to choose a Bootstrap track, a basic Flexbox track, or a CSS Grid track. Marrying itself to Bootstrap is a major mistake on so many different levels.

The Adobe Dreamweaver team and the forum team need to promote the extension community. Why? Because it is what sets Dreamweaver apart from other editors. There needs to be a balance of appeal to both coders and non-coders alike.

Once the Dreamweaver Team understands and accepts the simple logic of a successful path, the teams of ACPs that frequent the online community need to be briefed on strategy and tactics - an Adobe version of The Art of War.

I see nothing of major interest or import in the blog post. It is marketing fluff.

Preran
Community Manager
PreranCommunity ManagerAuthor
Community Manager
November 20, 2018

Can you try what I did and post your comments? Let me know if you are still having issues.

ALsp
Legend
November 20, 2018

Preran  wrote

Can you try what I did and post your comments? Let me know if you are still having issues.

Not Paula, but all I see is a brief flash of a button labeled Show More Comments, which immediately disappears. Id bad coding epidemic at Adobe or is it just an issue of continually choosing the wrong software :-)

pziecina
Legend
November 20, 2018

Thank you for posting Preran .

Are we allowed to comment? As I only see the recommendation to post feature requests in the user voice.

Preran
Community Manager
PreranCommunity ManagerAuthor
Community Manager
November 20, 2018

I I don't see a commenting area in any of the blog posts under the Adobe blog site, it's probably a limitation that's imposed by the administrator.

Thanks,

Preran

pziecina
Legend
November 20, 2018

Preran, in the article it says -

"If there are other features and enhancements you’d like to see built, please leave your feedback in the comments section or on UserVoice."

​But as you pointed out, there is no comments section!

Inspiring
November 20, 2018

Embrace modern web -- We are committed to supporting the latest versions of Bootstrap with Dreamweaver

LOL.

While no mention of CSS Grid, etc., so not really even coming close to moving towards the "modern web". Looks like the only thing that this confirmed, is that Dreamweaver will remain behind going forward ;-)

WolfShade
Legend
November 20, 2018

Just a heads up, Preran.  The link you provided will trigger uBlock Origin.

V/r,

^ _ ^

Preran
Community Manager
PreranCommunity ManagerAuthor
Community Manager
November 20, 2018

The blog is on the official Adobe Blog site. Can you check the settings on your computer and browser, just to be sure?

Thanks,

Preran

WolfShade
Legend
November 20, 2018

There are no settings on my end to change anything, except to temporarily or permanently allow traffic from na01.safelinks.protection.outlook.com (ain't happening).  I'm assuming that you submitted this thread via email.

If you come to the forum website and hover over the link you provided, the URL is:

https://na01.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Ftheblog.adobe.com%252Fwhats-coming-to-dreamweaver-in-2019%252F%26data%3D02%257C01%257Csyogin%2540adobe.com%257C5500bdfefbb848aa77ff08d64a95cb02%257Cfa7b1b5a7b34438794aed2c178decee1%257C0%257C0%257C636778404566601765%26sdata%3DmTtRLqh7YTQGC%252B010FimHBVv2g5hA1Mmop7aJXXWrS8%253D%26reserved%3D0

V/r,

^ _ ^