Split up user.js about user.js HOT 10 CLOSED

• 000-header.js
• 001-html-apis-dom.js
• 002-misc.js
• 003-extensions-plugins.js
• 004-features-components.js
• 005-automatic-connections.js
• 006-http.js
• 007-caching.js
• 008-ui-related.js
• 009-tls-http-ocsp.js
• 010-ciphers.js

szepeviktor@eeb624f

from user.js.

Actually I cannot see through one file but these sections can be handled.
Now I examine all of the prefs and I decide keeping/changing them.

from user.js.

Do you know Debian's /etc/apt/sources.list.d/ (called conf.d)? Its purpose is to keep the code clean.

from user.js.

Excuse me, I wasn't clear. The distributed file would stay the same, only the development version would be in user.js.d.

from user.js.

Please consider splitting up user.js to sections into user.js.d directory and add a build script:
cat user.js.d/* > user.js

Somehow I feel it's easier to keep them all in one. At least when it's still reasonable sized. When it exceeds some 1000+ lines or something like that, it might be better to split it, but at this point I think it's better all in one.

Also it would be one more extra step to add changes to it :)

from user.js.

@CHEF-KOCH You can use UglifyJS.

from user.js.

I have a feeling user.js can be converted into a nice ansible playbook.

from user.js.

I did now the basic work in the wiki, now we possible need to talk about improvements and which stuff is important.

I think most of the stuff can be (and already are) documented directly in the README. Some topics that are more cumbersome might benefit of having their own wiki page.

from user.js.

@CHEF-KOCH Please see my proposed format: https://github.com/pyllyukko/user.js/wiki/Proposed-nicer-format
@pyllyukko Please delete it tomorrow.

from user.js.

You can make an exception with Ciphers.

from user.js.