Caleb Stauffer

Okay, so here's what I found: When outputters are registered within the file that contains the output class (see Exhibit A), and those files are `include`d by hooking into `qm/outputter/html`...

@desrosj I just added this requested feature to my [Query Monitor Extend](https://github.com/crstauf/query-monitor-extend) plugin: https://github.com/crstauf/query-monitor-extend/commit/025427f2a19ec137a06e87fd3aa38fe437941776

@johnbillion totally your call on this, but if I may: @JPry my plugin [Query Monitor Extend](https://github.com/crstauf/query-monitor-extend) adds several extensions, including a whole table of 63 constants in the Environment section,...

Color coding could perhaps be used to help identify the values of the query vars.

I've been working on implementing this, and I'm getting close:  but can't determine the best way to handle large amounts of inline...

I'm wondering, if it's even worth it to show the inline data... it's in the source of the page, so perhaps just indicating that there is inline data is sufficient...

hmmm yeah I think providing the first 60 characters or so would be enough; user could grab the characters and search for them in the source. will do that.

yeah, that's what got me thinking about even showing it... I do and don't like showing it; seems redundant, but also helpful for a quick glance. _thinking it over_

thoughts, everyone? 

@szepeviktor count how many items are in the `data` and `after` keys? `data` is only a string, but `after` can have multiple items... is that what you're wanting? a count...