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

@juberti @marwahvikas @andresusanopinto PTAL.
>
> why do we need these on global? doesn't seems a scalable solution if
> every-time some js files depends on another we need to add the exported
> symbols here.


These are all variables defined in adapter.js and used in other JavaScript
files. I'm aiming to add to this list as I go through the other files and
find other variables from adapter.js that are used.

globalstrict allows global strict mode as opposed to function-scope strict
mode (i.e. the 'use strict'; declaration at the top of the file, not
within). JSHint advises against this in general (
jshint.com/docs/options/#globalstrict
<http://www.jshint.com/docs/options/#globalstrict>) but for us I don't
think it's a problem. Alternatively, we could take out 'use strict'; from
.js files and add strict: true to .jshintrtc.


On Mon, Oct 13, 2014 at 2:41 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"],
>
> why do we need these on global? doesn't seems a scalable solution if
> every-time some js files depends on another we need to add the exported
> symbols here.
>
> Maybe not care about "globalstrict" for now?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/GoogleChrome/webrtc/pull/146/files#r18769729>.
>