It was in UI2 but not in UI3 because I wanted to keep UI3 more focused on the core experience and not be bursting at the seams with buttons and features. Smaller apps are less work to build and maintain. That is really all there is to it. Though honestly I feel like every patch takes UI3 further from that simplicity I wanted.
Thing is, I believe you are the first person to ask to have this feature in UI3, and it has been in public beta on this forum since November. There are other development priorities which would be useful for more people, not to mention things that I am personally more interested in having than labels.
Is it good enough for people to just right click on a camera to see its name in the context menu?
While camera labels are something you could technically achieve with a local script, it would require programming experience and a great deal of knowledge of the inner workings of UI3.
Is camera names really that cluttering? Personally I think it's an essential feature, though not necessarily enabled by default as it is probably not necessary for every use case.
Understandable that your time is better spent on more pressing features though.
I can write JavaScript, but being a n3wb at this forum and BI, and looking through UI3 source I can see what you mean about needing a great deal of knowledge on the inner workings. I see it's outputting the stream on a canvas element but I can't see how I could get any reference to each of the camer names within, to inject a simple label overlay (fixed to the top of each camera).
The UI obviously receives the info I need to make a label, as you can see the camera names on the right click menu's. Any pointers on how I can achieve this? Is there a JSON API or anything similar?
I wish I didn't have to but will have to stay on UI2 otherwise as the site I'm using it needs a visible name on each camera.