The challenge with changing it is most likely in how the Web IDE is acting upon. In addition - when connected - the Web IDE would have to harvest this information from the Web IDE host (win, osx, linux,... what-ever box), and transmit it. When Espruino then running and having a wired or wireless IP connection, overwriting / precedence challenges arise... and the variability overwhelms the Web IDE. Something that could work is when the Web IDE talks over IP to Espruino... then the Web IDE could somewhere in the banner display the IP (and a setup defined mapped name) of the connected device.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
The challenge with changing it is most likely in how the Web IDE is acting upon. In addition - when connected - the Web IDE would have to harvest this information from the Web IDE host (win, osx, linux,... what-ever box), and transmit it. When Espruino then running and having a wired or wireless IP connection, overwriting / precedence challenges arise... and the variability overwhelms the Web IDE. Something that could work is when the Web IDE talks over IP to Espruino... then the Web IDE could somewhere in the banner display the IP (and a setup defined mapped name) of the connected device.