[x3d-public] Issue: X3D V4 Functionality

[doug sanden]

Option3:
Include all nodes in the html profile, and rely on some pre-process(es) to deliver optimal blend of code and data, optimized around designers choice of bandwidth and/or client cpu load:
a) one-time scene compile:
i) select subset of all js node definitions/code to match scene
ii) automatically convert any scene sub-optimal or missing convenience node type data to basic node
b) server-side download pre-processing - similar to a) except on-demand
c) client-side as-needed pull mechanism for node-type-specific code


>
> Yes, Len, this is what I would lobby for. Some core code, and then pull
> in code needed to do what is required by the content (and/or author).
> I'm sure a tool could be used to 'compile' (minify and combine) parts
> for a slimmer download, but on developer-mode, it's just different bits
> of JS it loads, that would be nice. Unless as you say, the entire thing
> is small enough to include.
>
> Dave Arendash
>
> Follow me! @thatvrguy
>
>
> On 7/9/2015 9:10 PM, Leonard Daly wrote:
> Should there be multiple HTML profiles (different levels of
> functionality that work in HTML)? I can see this being useful to
> provide a very light-weight library, especially good for mobile use;
> and a heavier one (with more functionality) for larger applications.
>
> Generating multiple profiles takes additional work and can introduce
> errors (in the spec, in the code, in the use). If the full-capability
> one is sufficiently light-weight, then it does not much matter. Perhaps
> a base-level profile that can pull in needed extensions based on the
> content?
>
>
> Leonard Daly
>
>
>
>
>
> One man's convenience is another man's traffic saver.
>
> Technically, every geometry (including primitives) can be rendered to a FaceSet (indexed? what indexed?). But think of X3D size, were that to happen.
>
>
> ________________________________________
> From: Limper, Max [max.limper at igd.fraunhofer.de<mailto:max.limper at igd.fraunhofer.de>]
> Sent: Thursday, July 09, 2015 6:25 PM
> To: doug sanden
> Cc: x3d-public at web3d.org<mailto:x3d-public at web3d.org>
> Subject: Re: [x3d-public] Issue: X3D V4 Functionality
>
> I really like the idea of identifying "convenience nodes"!
>
> This should help us to define a minimal subset for HTML. X3DOM already has some nodes that are not really necessary, so it could make sense to also check X3DOM for convenience nodes that could be removed from the HTML Profile.
>
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org<mailto:x3d-public at web3d.org>
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
>
>
>
> --
> Leonard Daly
> X3D Co-Chair
> Cloud Consultant
> President, Daly Realism - Creating the Future
>
>
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org<mailto:x3d-public at web3d.org>
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
>
>
> _______________________________________________ x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org