I'm using the BCC NXT Screen capture tool on my PC screen when running simulateously a NXC program to watch what's happening there (because the NXT screen itself is too small and too dark because not backlit),
and some years ago I also temporarily used a variable watching tool for debugging (don't remember how it was actually called) (but meanwhile I don't use it anymore, I just debug directly via NXT screen output and BCC Screen capture tool.
I think this is what you mean by "have directly to do with either a native arm-linux or a VM compiler" (anyway, this is sort of what I understand of it's usage).
It sounds a little as if you feel sort of bugged of my question(s) but it's no offense :)
it's simply why I just couldn't imagine why I personally would need a tool to tell me where I have plugged what sensors to what port before because I'm used to use SetSensor(port, SensorType) commands manually for sensor setup (so I can read and look what I have done) and additionally I used printf commands to show values of interest in real-time on the NXT screen.
(of course, newbies to programming like for NXT-G or "EV3-G" surely will appreciate autosensing because I can sympathize how it feels if one searches any adjustments to ports or sensors or variables in those garish colorful icon and wire salads)^^ .
on the other hand, if this Live Sensor Tool was meant to be used simultaneously when running any compiled program to get an additional access to sensor values or encoder values to debug a running program in real-time
or if it had ben created to establish a module for daisy chaining I/O ports which then could be accessed by a C program, too - that indeed would be amazing and would be within the horizon of my skills of imagination ;)
but just don't care , my question actually is not important enough to start a dispute, it was just out of interest.
NXC CHESS for NXT: http://www.mindstormsforum.de/viewtopic.php?f=70&t=6790
indispensable for NXC + EV3-C: easy + trouble-free network & remote control for rs485, Xbee, BT, USB!