Autoprefixer

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?

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.

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.

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)