Skip to main content
pziecina
pziecina
Legend
July 17, 2019
Question

Dreamweaver into the 2020's.

  • July 17, 2019
  • 5 replies
  • 5296 views

As many may know, myself, Birnou, (and others behind the sceen) have been asking about Dw's future. Well the blog post is up, and the discussion is ready to begin.

The post was in the 'output error' discussion and said -

We appreciate your feedback. We are actively working on improving Dreamweaver to meet your web development needs.

Here is an overview of improvements we are working on for upcoming Dreamweaver updates in 2019 and 2020.

Kindly have a look into the blog post and share your thoughts.

Regards

And was posted by Dw team member - yshivaprasad,

    This topic has been closed for replies.

    5 replies

    pziecina
    pziecinaAuthor
    Legend
    July 19, 2019

    Just going completely left field with this question.

    If Dw is going to include what is new in html5, I am wondering if they will include some form of srcset builder, in which one could actually build the 'media type query' that is possible when using srcset, or if anyone thinks that a straight forward 'code hints' approach would be all that is required.

    After all, some of what one can do with srcset goes way beyond the simple 1x, 2x, 3x. type of use most commonly seen.

    If you look at the resolution switching, (different sizes) example, you will see what I mean, and much more complicated structures are also possible -

    https://developer.mozilla.org/en-US/docs/Learn/HTML/Multimedia_and_embedding/Responsive_images

    Jon Fritz
    Community Expert
    Jon FritzCommunity Expert
    Community Expert
    July 19, 2019

    I don't think they have the resources to create a tool that would handle the complexity of options available with srcset. Unless they bought it from a third party extension developer, like Project VII (who have a basic but useful extension for it).

    pziecina
    pziecinaAuthor
    Legend
    July 19, 2019

    Thanks Jon,

    That is what I was thinking. I also thought that if the more complexed srcset structures are to be handled by code hints alone, it would be an indicator of 'how the team was thinking', (or not).

    Simply because a casual or beginner coder would have serious problems with anything more than the basic 1x, 2x or the 'w' descriptor usage, (I know I do, and I know how to use it).

    pziecina
    pziecinaAuthor
    Legend
    July 18, 2019

    Just wondering if anyone can answer a question.

    What does the blog post mean, in the O.S. compatability updates, when it says -

    "Chromium based Edge browser"

    The reason I ask is that I cannot see any compatability problems. After all it is a browser, so what has to be compatible with Dw?

    Brad Lawryk
    Brad Lawryk
    Legend
    July 18, 2019

    pziecina  wrote

    What does the blog post mean, in the O.S. compatability updates, when it says -

    "Chromium based Edge browser"

    It doesn't mean anything. Much like 90% of the content in the blog post. Just using big words to sound impressive.

      pziecina
      pziecinaAuthor
      Legend
      July 18, 2019

      Thanks Brad.

      I could not see any reason for a compatability problem. I even have the Edge Dev preview installed but thought I may have missed some update or other in Dw CC versions, that somehow causes a problem, as my Edge preview even works with CS6.

        Brad Lawryk
        Brad Lawryk
        Legend
        July 17, 2019

        I think the lack of traffic (new posts) in the forums also speaks volumes for the state of Dreamweaver. It's just not what it once was. Sad really. :-(

        B i r n o u
        B i r n o u
        Legend
        July 18, 2019

        https://forums.adobe.com/people/Brad+Lawryk  a écrit

        I think the lack of traffic (new posts) in the forums also speaks volumes for the state of Dreamweaver. It's just not what it once was. Sad really. :-(

        I did a call some weeks ago on the alpha forum to see who was present there... I recieved 1 answer...

        pziecina
        pziecinaAuthor
        Legend
        July 18, 2019

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

        I did a call some weeks ago on the alpha forum to see who was present there... I recieved 1 answer...

        I don't know if you remember my 'Is there anybody out there' post, to which only you replied. But I was later told that over 20 acp's had signed up to the alpha pre-release.

        The other problem with Dw is that they are catering for beginners and casual users, and not web designers/developers. Creating for the modern web requires one to know what is happening, and at least try to guess what is going to happen. Standing still for a year or more in the profession these days, means that catching up is very difficult, and Dw has stood still for years.

        Even simple things like srcset, and base 64 encoding have had feature requests filed since 2013, with Dw ignoring them.

        I don't know if the Dw team is to blame, or Adobe in general, but in the end the 'who is responsible' is no longer important. What is important is that they stop looking at wed design/development as a side-line to other professions for which adobe produces products.

        Brad Lawryk
        Brad Lawryk
        Legend
        July 17, 2019

        It's the beginning of the end for Dreamweaver. Glad I have moved on over a year ago. :-(

        pziecina
        pziecinaAuthor
        Legend
        July 17, 2019

        https://forums.adobe.com/people/Brad+Lawryk  wrote

        It's the beginning of the end for Dreamweaver. Glad I have moved on over a year ago. :-(

        As I discovered in the pre-release, some well thought of advisors to the Dw team, (and a few of the team) don't think none Dw users should have a say in Dw's future. I'd have thought that those who gave up on Dw are the people to ask what is wrong.

          pziecina
          pziecinaAuthor
          Legend
          July 17, 2019

          My reply -

          I was pleased to read that code hinting would be for ALL html5, css and js, but I would be interested to know what is ment by 'ALL'. As html5 contains much more than most people think, and in my experiance, much more than the Dw team think. Plus css and the js api's, at what stage in the recomendation process will a spec be included in code hints, as many specs are WD's but stable and well supported by browsers.

          Dw's code editor could use a lot of work, but the little information provided does not allow me to make any judgement. I see no mention of a stand alone css prefixer though, which as I have said previously makes Dw a 'do not use' for many.

          As for the pre-release, and testing. As I have said previously 'why should I bother'.

          I found some members of the CAB and prerelease insulting, and lacking in knowledge, (though not all). Anyone thinking they can influence anything, forget it. Replys or discussions with any Dw team member are now none existant. And lastly, whats in it for me?

          I don't use CC, so any 'here is a years CC subscription' is worthless.

          Terms & ConditionsAccessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices