#300 Making .jsbeautifyrc resolve work
* not using cc.find() anymore:
** using dedicated find based on cwd (cc uses __dirname, resolving to install dir of node_modules)
** not using recursive lookup when resolving file from user home
* user directory is either HOME or USERPROFILE (for windows)
Add node-static for easier local web testing
Add Block_comments to skipped token types
Line wrapping disabling in html_beautify fixed for web

Fixes #306
Python 1.4.1
1.4.1
Added tests for .jsbeautifyrc resolve algorithm of cli.js
beautify with js-beautify
put "whiteRe.test(output[output.length - 1]);" (used twice) in function
rename 'coma' to 'endChar' to represent more closely what it actually means
make sure there is exactly one whitespace after a colon (making a rule look like "color: red", not like "color:red")
add a newline after header-comments
introduce new option "end_with_newline".
The default value is "false" and this will make sure that the output ends with a newline ("\n")
don't add a newline between "{" and "}" when there is nothing in-between
before ".tabs {}" resulted in ".tabs {\n}". The rule is of course useless but a popular starting point
add option "remove_trailing_zero"
the option is disabled by default and will remove trailing zeros from floating point values (e.g. 0.9 to .9)
Initial version of a python port of the existing css-beautify. Tried to keep options and functionality and even code-flow as close as possible to the original version to make future updates easier.
Included unit tests suggest that the formatting works okay, best would be if these unit tests will be ported to the js-version also
Merge pull request #334 from dertseha/win_home

Making .jsbeautifyrc resolve work (in general and for Windows re home dir)
remove "remove trailing zeros"
add new option "selector_separator" which determines which string should separate selectors, e.g. setting it to '\n' results in 'a,\nbr', setting it to ' ' in 'a, br'
provide tests for beautify-css.js
fix header newline bug