[x3d-public] remove SF/MFInt32 ?
andreasplesch at gmail.com
Fri Apr 6 10:14:03 PDT 2018
That came to mind as well, since js numbers are doubles. May be it is time
to trade less efficient use of resources for simplicity and convenience ?
Mobile is a large area with limited resources, however.
On Fri, Apr 6, 2018, 12:49 PM GPU Group <gpugroup at gmail.com> wrote:
> 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
>> 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 Plesch
>> Waltham, MA 02453
>> x3d-public mailing list
>> x3d-public at web3d.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the x3d-public