[Fiware-webui] WebTundra & new Three.js versions

[Toni Alatalo]

Hi, just a little heads-up for devs using or considering WebTundra / Three.js:

Current WebTundra versions in production use a bit old Three.js
version. I made a branch last week where ported the previous WebTundra
1.0 version (master & dev branches) to current Three.js release (r68
from July) and there's a pullrequest for dev open for that now:
https://github.com/realXtend/WebTundra/pull/72

There's one major API change that affects direct usage of three
Object3Ds: position, scale and rotation are now unassignable. You need
to use set() and clone() methods to change them instead. This has been
controversial on the three.js side but actually the change seems
mostly to enchance our codes when looking at changes:

- in core: https://github.com/realXtend/WebTundra/commit/648db1785434b770fed31e0b51ee726bdde7f1dd
- in Pong example:
https://github.com/playsign/PongThreeJS/commit/0ede0815b8db9abdf72c9e48af1a906bf89fcc5d

.. less creation of extra THREE.Vector objects. So I think we'll just
adapt to this change and not complain to upstream or so.

If you're just moving objects in the net-synchronized way via
EC_Placeable you're unnaffected (we'll do the porting for you
underneath). But if using the Three API directly for something this is
good to know and adopt in new dev straight away.

There is still more we need to test and possibly port but in general
it looks like we are able to follow Three's development just fine and
use the latest and greatest in coming releases. They have some new
optimizations for mobile (i.e. weak cpu) devices (commits from NVIDIA
who tested with Tegra), faster upload of textures (by Microsoft from
Photosynth2 work), PVRTC texture example for iOS8 etc. so is good that
we can update.

I'll also test what happens with current Three.js dev branch (next
upcoming release) and WebTundra when get the chance (or feel free
anyone if beat me to it!).

Cheers,
~Toni