Address a pointSize NaN bug

[rocky]

Fixes #125

There are probably deeper issues in setting the pointSize.

[TiagoCavalcante]

Hi @rocky. I've implemented a more reliable fix: pass the container size as a uniform which is updated whenever the container size changes. It should work well now.
The tests haven't passed for some time (#107), but it is working.

[rocky]

@TiagoCavalcante Many many thanks!

[rocky]

@TiagoCavalcante: Can we get a release on npm please?

I've pushed this to npmjs.org. Thanks again!

[rocky]

(One other thing that might be interesting, but not needed right now, is to see if we can update the three.js version.)

[rocky]

@TiagoCavalcante: Can we get a release on npm, please?

I see that I can do. I will do, but there will be another PR to change Mathics to Mathics3.

[TiagoCavalcante]

(One other thing that might be interesting, but not needed right now, is to see if we can update the three.js version.)

I've updated it to the latest version (r184) in #129.

[rocky]

(One other thing that might be interesting, but not needed right now, is to see if we can update the three.js version.)

I've updated it to the latest version (r184) in #129.

You're the best!