Re: [Openvrml-develop] Our SFImage story

[Christopher K. S. J. <cs...@qu...>]

Braden McDaniel wrote:
> 
> In either of those cases, our current design would require dynamically
> converting to the 4-byte-element format when one of these bindings
> attempts to access the data.
>

 The java bindings (EAI and Script node) already use an array
of bytes. The netscape javascript api, if I'm remembering right,
lets you fiddle with the array access operators in the code
that binds the script object to the underlying C/C++ object.
You'd case out on numcomponents, but it shouldn't be very much
code. (That assumes I'm remembering correctly...)

 Besides, doing image processing in javascript is not likely to be
fast for a whole raft of other reasons, so I don't see it as a likely
bottleneck.


> I think we need to store the integer format in VrmlSFImage.
>

 Then you'd have to convert back and forth to an array of bytes
when you were using a java interface.

 Unless it turns out that the javascript implementation is
just totally undoable, I'd vote for leaving things the way
they are.


-cks