Not ideal because our object.lookAt flips orientation.

Fixes #2524

Some things probably could be done still nicer, e.g. using new gui.dat color controllers.

Just emergency fixes to make examples work. Still lot of things with GUI itself are broken :S

At least it works now, though GUI is still crazy.

For the moment handling just changes via UI, not yet possible to drag gizmos.

Still fog color picker widget behaves weird: it doesn't display color selected by mouse after setting value from JS, yet value gets transmitted fine. Maybe it's a Chrome bug.

Editor: Reverting Menubar styling that was strangely opening when clicking on dropdowns and confirm()s.

Added "AddOperation" environment mapping combine type for additive cube maps reflections / refractions.

Fixes #2559

We'll see, if this becomes a bottleneck in the fragment shader, all three environment mapping combine options could be changed from uniforms & ifs into #ifdefs.

Ugh! And there I was thinking that UI.Color had a bug.

Not there yet completely, some things are still broken and code is pretty horrible but at least something starts to work.

This just adds an easy convience method with thanks to @jibooo

And menubar hover thingies are back ;)

See discussion in https://github.com/alteredq/three.js/commit/fe902e553f5e30e3752398ad1588bcc4ea1f5513

That was a bit tricky - because Viewport was created before Sidebar.Outliner, cameraChanged signal wasn't effectively setting activeCamera in Outliner (which is how it is passed to SceneExporter).

Changing order of these UI element creations though started to (correctly) highlight Viewport, and as this is controlled via pseudo CSS :focus class, it can't be easily overridden from JavaScript. We should really start to use CSS.