<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
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).<br>
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.<br>
<br>
Dave Arendash<br>
<pre class="moz-signature" cols="72">Follow me! @thatvrguy
</pre>
<div class="moz-cite-prefix">On 7/9/2015 9:10 PM, Leonard Daly
wrote:<br>
</div>
<blockquote cite="mid:559F45BD.2040608@realism.com" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div class="moz-cite-prefix">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.<br>
<br>
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?<br>
<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
<br>
</div>
<blockquote
cite="mid:CC1C444FB9E32940BA18B288E9CAB83C145B178D@msgb05.nih.gov"
type="cite">
<pre wrap="">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 [<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:max.limper@igd.fraunhofer.de">max.limper@igd.fraunhofer.de</a>]
Sent: Thursday, July 09, 2015 6:25 PM
To: doug sanden
Cc: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>
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
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a>
</pre>
</blockquote>
<br>
<br>
<div class="moz-signature">-- <br>
<font class="tahoma,arial,helvetica san serif" color="#333366">
<font size="+1"><b>Leonard Daly</b></font><br>
X3D Co-Chair<br>
Cloud Consultant<br>
President, Daly Realism - <i>Creating the Future</i> </font></div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
x3d-public mailing list
<a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>
<a class="moz-txt-link-freetext" href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a>
</pre>
</blockquote>
<br>
</body>
</html>