Client-side dialogs / snap-ins

If this has already been proposed in the voting system (couldn't find it) or posted on a different thread, please let me know. I'm posting here first before propsing it on the voting sytem so we can discuss it a bit and work out the kinks in the proposal, also hopefully garner some voters...

I've started making a system in-world (won't talk about specific functionality), that has a "control panel", which of course is prim based with dialogs (the hokey ones with the hokey buttons.. llDialogue()), and chat listens for certain types of commands and such. Anyway, it would really benefit, as I'm sure many systems would, from being able to author the control panel as a client-side (full-featured) dialog that looks like the current built in ones for preferences etc..

I'm proposing they let us write "client" scripts that allow us to use the sliders, textboxes and other controls to build custom dialogs that are executed on the client side but that can transmit values back to the originating scripts... much like javascript works in a web browser.

So many benefits... let's discuss it a bit here before i put the proposal in.

It's prop 8.
I voted for it.
It got accepted for development - hooray!

Oh, that's the HUD attachment. Very cool, but not what I'm talking about. With that you still use prims and such.

If you go to the "Edit" menu, then go to Preferences, you'll see what I'm talking about. That dialog, with tabs, sliders, color pickers, etc..

It would be great if we could write scripts to create those types of client-side dialogs using those same types of controls.

Right now if I want a slider it's a bit of an ordeal to program... would be nice to able to define dialogs with some sort of markup (xml perhaps), and insert an llSlider(); call where needed.