Added top level .jshintrc for global rules; removed corresponding JSHint directive

@juberti @marwahvikas @andresusanopinto PTAL.
>
> Once you try to jshint on apps that split across multiple js files (such
> as test-rtc) wouldn't this list grow considerably?
>
This list should only need to include names of variables defined in
adapter.js (or any other variables that are used across multiple files).
You can also put a JSHint global directive in an individual file – such as
apprtc/js/main.js, which has 'initiator', 'roomLink', etc.


> Regarding the remove the "use strict" I am not sure.. that string is used
> by the browsers so we could left it in.
>
I'm inclined to leave it in – advice I've had is that it's not problematic
in production.


On Mon, Oct 13, 2014 at 3:26 PM, André Susano Pinto <
notifications@github.com> wrote:

> In samples/web/.jshintrc:
>
> > @@ -0,0 +1,13 @@
> > +{
> > +  "browser": true,
> > +  "camelcase": true,
> > +  "curly": true,
> > +  "devel": true,
> > +  "eqeqeq": true,
> > +  "forin": false,
> > +  "global": ["RTCPeerConnection", "trace", "webrtcDetectedBrowser", "webrtcDetectedVersion"],
>
> Once you try to jshint on apps that split across multiple js files (such
> as test-rtc) wouldn't this list grow considerably?
>
> Yeah I am in favor of strict.. just not sure about the global.
> Regarding the remove the "use strict" I am not sure.. that string is used
> by the browsers so we could left it in.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/GoogleChrome/webrtc/pull/146/files#r18771945>.
>