[x3d-public] remove SF/MFInt32 ?

GPU Group gpugroup at gmail.com
Fri Apr 6 09:49:32 PDT 2018

related: SF float32 vs double64: would all double be simpler on x3d specs,
and internally, up to opengl interface?

On Fri, Apr 6, 2018 at 9:22 AM, Andreas Plesch <andreasplesch at gmail.com>

> Here is a somewhat radical idea to simplify X3D a bit. Since x3dom is
> javascript it does not really distinguish between SFInt32 and SFFloat, and
> lives pretty well with it. So why not consider completely removing the
> SF/MFInt32 from the spec. in general ?
> The integer fields are used in not very many nodes: Switch,
> IntegerSequencer, LOD (level_changed) come to mind. A replacement with
> SFFloat would mean adding rounding or truncation to nearest integer in the
> spec. language but probably not more than that.
> The advantages are that it is an opportunity to make the spec. leaner, and
> help with some node communication issues.
> The disadvantages are that it would be a backwards incompatible change,
> and may have a minor performance impact.
> -Andreas
> --
> Andreas Plesch
> Waltham, MA 02453
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20180406/ddd9921d/attachment.html>

More information about the x3d-public mailing list