Add debug cmd switch

[XhmikosR]

..which would show the time spent and the compression ratio for the task.

[GoalSmashers]

@XhmikosR quick question - would you like to see the same output as in npm run bench or rather than that something simple like:

Minification time: 93ms
Compression ratio: 19%

I'd go for the latter one.

[XhmikosR]

Yeah, I agree with the later one too. I don't think there is a gain by showing the time for each time of transformation.

[GoalSmashers]

@XhmikosR See d198bd2 - that should be it!

[XhmikosR]

1st thought, is maybe mention the switch change in History.md.

Secondly, I'm wondering, is "compression ratio" the right thing to show? How about showing the percentage of the original file the compressed file is?

[GoalSmashers]

Good point with History.md.

Maybe it shouldn't be called "ratio" but instead something like "compression efficiency" as it is calculated as:

• input data - 200 bytes
• minified data - 160 bytes
• compression ratio - (1 - 160 / 200) * 100 = 20%

[XhmikosR]

I think that's the difference then.

[GoalSmashers]

👍

[XhmikosR]

http://en.wikipedia.org/wiki/Data_compression_ratio

[GoalSmashers]

Ok, that's it. Merging to master...

[XhmikosR]

@GoalSmashers: Do you think you could expose debug in JS too?

Example:

var packCss = cleanCSS.process(inCss2, {
    removeEmpty: true,
    keepSpecialComments: 0,
    debug: true
});

[GoalSmashers]

We will do once #138 is done. Current stateless design is pretty messed up.

Please open a separate ticket for it.

On 7 Sep 2013, at 11:42, XhmikosR notifications@github.com wrote:

@GoalSmashers: Do you think you could expose debug in JS too?

Example:

var packCss = cleanCSS.process(inCss2, {
removeEmpty: true,
keepSpecialComments: 0,
debug: true
});
—
Reply to this email directly or view it on GitHub.