Skip to main content
BenPleysier
Community Expert
Community Expert
May 11, 2018
Question

Autoprefixer

  • May 11, 2018
  • 4 replies
  • 5799 views

In the process of testing a code editor (IDE), I came across an Autoprefixer. Although this was a while back, I thought it important enough to share the experience with you and the importance of having this feature added to Dreamweaver. As a side note, because I use Sass with the correct add-on, prefixes for my projects are already added. This feature is for those that do not use pre/post compilers.

Set the Site Options

Write the code

And Save

    This topic has been closed for replies.

    4 replies

    pziecina
    Legend
    May 17, 2018

    The real question is -

    Why is Wappler better than Dw, or is it?

    Given that-

    Most if not all Wappler testers, are Dw users.

    Why if  -

    A number of Wappler testers are also members of Dw CAB or pre-release, then why have the ideas such as a stand-alone css autoprefixer never been supported, or included in Dw, was it lack of foresight or simply because those who objected to such features simple did not care.

    What will/would Wappler replace -

    Will Wappler replace Dw, especially for those who only have a single app subscription to CC for Dw?

    Is Wappler more in-line with what an up-to-date version of Dw CS6 may have been?

    BenPleysier
    Community Expert
    Community Expert
    May 17, 2018
    Why is Wappler better than Dw, or is it?

    At this stage it is not, it still misses a lot of functionality. I have found that I tend to use Wappler's Design view more than Code view, something I would not dream of when using DW.

    A number of Wappler testers are also members of Dw CAB or pre-release, then why have the ideas such as a stand-alone css autoprefixer never been supported, or included in Dw, was it lack of foresight or simply because those who objected to such features simple did not care.

    A rhetorical question?

    Will Wappler replace Dw, especially for those who only have a single app subscription to CC for Dw?

    No, Dreamweaver with DMXZone extensions will do the same as Wappler. The difference is that Wappler is a much faster and smoother application.

    Is Wappler more in-line with what an up-to-date version of Dw CS6 may have been?

    Another rhetorical question?

    The main reason why DMXZone have chosen to go their own way is because they did not want to rely on Adobe for their future.

    Having said that, they will continue to support Dreamweaver with their extensions which is good news for users of Dreamweaver. After all, it is the likes of DMXZone, PVII and Webassist that make Dreamweaver bearable.

    Wappler is the DMXzone-made Dreamweaver replacement and includes the best of their powerful extensions, as well as much more!
    Legend
    May 18, 2018

    BenPleysier  wrote

    After all, it is the likes of DMXZone, PVII and Webassist that make Dreamweaver bearable.

    Exactly why I could so easily walk away from it, without it affecting my workflow. So many are locked into an application as a concequence of being dependent on centric focused solutions.

    pziecina
    Legend
    May 11, 2018

    As I have been asking for this feature for years, I cannot see Dw bothering now.

    Everything I think about autoprefixers and workflows I have already said in previous discussions, so no longer interested as I now have my own in CS6, and CC I will never use.

    Legend
    May 11, 2018

    BenPleysier  wrote

    In the process of testing a code editor (IDE), I came across an Autoprefixer. Although this was a while back, I thought it important enough to share the experience with you and the importance of having this feature added to Dreamweaver. As a side note, because I use Sass with the correct add-on, prefixes for my projects are already added. This feature is for those that do not use pre/post compilers.

    Set the Site Options

    I guess that would be Wappler then?

    This kind of thing has been around for years - Coda 2, to a certain extent, added some prefixes on save but not all. The question I ask is are all the prefixes built into the IDE or are they pulling the prefixes from an external source because IDEs can becaome outdated quit  fast as the prefixing that needs to be supported changes.

    I think I would agree that there should be an option to add the final prefixes at stage when its convienient to the developer, which in turn could make a duplicate of the clean css file.

    Something is better than nothing though. What I object to with build files just to include the prefixes is it just means an extra set of files to manage which is not always desriable.

    At the moment I use Prepros which does have and option to add the prefixes at a time the developer chooses but it would sure be nice to have everyting in one IDE rather than everything splatted about all over the place.

    Inspiring
    May 11, 2018

    osgood_  wrote

    I guess that would be Wappler then?

    Thats the first mention of that app I seen in a while. I noticed they have now removed all the links for the crowdfunding from their main site, blog, etc. So maybe in twelve more full moons we will finally get to see it released to the public.

    Legend
    May 11, 2018

    W_J_T  wrote

    osgood_   wrote

    I guess that would be Wappler then?

    So maybe in twelve more full moons we will finally get to see it released to the public.

    Seems it was a much bigger project to manage than they thought going by their original timeline for beta product launch. Will it even see the light of day.

    B i r n o u
    Legend
    May 11, 2018

    thanks Ben for the heads up on such a feature... what follow is not argue ... it is just a point of view

    what I don't like on this type of mecanism, is that once applied, the CSS become verbose... and as far as I understand there is not way to get back to original file, because the new CSS generated overwrite the original one.

    what I like in Post CSS or in task automator (depending on project) is the fact that original working files are not the same than the production ones. (personally I never used Sass for prefixing files)

    BenPleysier
    Community Expert
    Community Expert
    May 11, 2018
    what I don't like on this type of mecanism, is that once applied, the CSS become verbose... and as far as I understand there is not way to get back to original file, because the new CSS generated overwrite the original one.

    I wholeheartedly agree with you there.

    Using a task automator (let's invent this word) adds another process and Post CSS is not included in Dreamweaver, not that I am saying that either should be ignored because of that.

    I prefer something that is automatic saying that it would be worthwhile arguing for a double save of the CSS like styles-orig.css and styles.css.​ Thanks for the idea.

    Wappler is the DMXzone-made Dreamweaver replacement and includes the best of their powerful extensions, as well as much more!
    B i r n o u
    Legend
    May 11, 2018

    arf arf... task automator... I don't know why I often use this words... for qualifying task runner...

    I think that all the IDE task include in a process (for minifying, concatening, prefixing, removing unusued, ...)  should adopt a non destructive way... having in some folders development files... and in others folders production files....