Week 1 ccug hit upon a topic I've been trying to organize a request about. Yay!
Per Inara Pey's summary: "In terms of HUDs, it was suggested by Vir Linden that a more cohesive approach might be to provide support directly through the existing viewer UI and using commands native to the UI rather than part of an additional scripting capability to build / operate HUDs."
This is the direction I'd love to see this go towards. LSL is designed to run server-side; rather than pick it apart and split out what can happen in-viewer, I'd love to see the viewer itself accessible via an API.
At present, to implement "that one feature"--a UI, some RLV or RLVA, something designed for gaming... in all cases the would-be developer has to develop their own entire viewer just to slide in the thing they need.
Is it too controversial to go one further, as a way so solve the inevitable next issue where people try to run code on my device?
SLAPP store? Ok, maybe a different name. But, there's a $140 billion industry that suggests people
want
to be able to take the base "OS" and to hook into pre-defined sets of "api permissions" to expand the capabilities of the device. I can envision entering a custom game region, and just like the Experience prompt now, getting a SLAPP prompt to let me know a viewer extension is needed to play the game. In this way, the permissions used would be clear (and vetted) and there'd be a much less sketch way to extend the viewer.
arguments ensue