Extra check doesn't seem to have much effect on performance. This may become a bigger concern if other bottlenecks would go away.

Fixes #2568

Don't need to update scene graph matrices (molecules don't change).

This has very little impact on performance though, bottleneck is not on JS side, profiler shows ~65% of time spent in "(program)".

Maybe these should be toggleable, they are too slow for larger molecules.

It seems no matter which DOM elements are used for CSS 3D, you can't have more than couple hundreds without starting to hit a performance wall, even on desktop browsers ;S

This was causing vortex-looking bug when panning camera with TrackballControls on right click drag.

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.