[x3d-public] both X3DOM and X_ITE.

[John Carlson]

Joe, in the past, my hands have been full with X3D JSON.   While this isn't
necessarily the case any more, the Proto Expander in X3DOM still needs
work, and X_ITE needs work on JSON embedded shaders.  I currently have been
unable to do builds with X_ITE.   Also, VRML Scripting still needs to be
implemented integrated with X3DOM.

Has BS Contact implemented X3D JSON yet?
Perhaps I should be working with X3D JSON in C++?

I agree that HAnim is important, but it has been unimportant for my use
cases (JSON, force directed graphs, blob/rose/orbital visualization, geo
visualization, bubble/prismatic visualization).   If you provide some HAnim
XML documents that are convertible to JSON, I can start looking into it.

On Mon, May 28, 2018, 10:42 AM Joseph D Williams <joedwil at earthlink.net>
wrote:

>
>    - > both X3DOM and X_ITE …
>
>
>
> The discussions about both X3DOM and X_ITE are, to me, missing a very
> important feature. Neither of these tools can do HAnim skeleton controlled
> deformable skin. This is a very important feature, lending itself to many
> important applications in addition to HAnim. There have been several
> discussions about the hanim joint(s) to deformable skin bindings and as far
> as I have seen, there is no doubt that the way x3d specifies the basic,
> most simple, and most transportable technique to achieve the result. So, as
> the HAnim standard takes the next step, why not move a bit toward
> implementing this important capability in your browsers. BSContact does it,
> I think Instant does it mostly but x3dom and x_ite don’t.
>
>
>
> Thanks and Best,
>
> Joe
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20180528/575280f9/attachment.html>