[x3d-public] Issue: X3D V4 Functionality

[Leonard Daly]

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]
> Sent: Thursday, July 09, 2015 6:25 PM
> To: doug sanden
> Cc: 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
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>


-- 
*Leonard Daly*
X3D Co-Chair
Cloud Consultant
President, Daly Realism - /Creating the Future/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20150709/107d204f/attachment.html>