Bruno Daniel

## ng-inspector Wait...nevermind :p

I think the term most appropriate is something related to **instrumentation**, which is the feature this module is supposed to provide. Maybe simply **angular-instrumentation**? A bit boring, but descriptive.

Too bad Protractor already exists, being the "instrument" to measure "angles"!

For now I just included the generated files in `/Editor/Art/Hivemind/`. Ideally a build step should copy them over to `/Editor Default Resources/`, or use the method above. For now, users...

Good catch, at least alphabetic ordering should be a good start, and later possibly an extension setting to toggle grouping by type.

The simple detection we're doing in [bootstrap.js](https://github.com/rev087/ng-inspector/blob/master/src/js/bootstrap.js) for the presence of the angular object in the window scope would probably stay even if we add an additional check borrowed from...

I'm not against adding an additional check using his method, but I'm not sure if it would add any benefits either.

Added disabled states for all toolbar button icon sizes, (same filename sufixed with `-disabled`) as well as the [empty state graphic](https://github.com/rev087/ng-inspector/blob/master/ng-inspector.chrome/empty.png) to the repo. Disabled:  Enabled: 

@jcummins no, setting that option does not make it work. As far as I can tell, there is no way to access the DOM and/or JavaScript context for `file:///` URLs

:+1: (btw, the plunkr example is very appreciated!)