<br><br><div class="gmail_quote">On 5 May 2010 08:00, Len Bullard <span dir="ltr"><<a href="mailto:cbullard@hiwaay.net" target="_blank">cbullard@hiwaay.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="blue">
<div><div>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy">“</span></font>To my thinking: the
same motivation one would have to support openGL : increased portability and
interoperability makes business sense to me.“</p>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"> </span></font></p>
</div><p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy">Mine too. Portability of content is
what I want. As the artist, I don’t WANT to pick the radios.</span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy"> </span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy">Art production requires lots of time
in. For the time in to pay out, content has to be resilient to shocks
from the browser. That makes it hard to host and rehost anything but
video. Some really easy to apply interface widgets can greatly
improve productivity but are costly to experiment with on the host given the
distribution of the host. Software kudzu. One response
is to identify and reward the strengths of the software instead of working to
perfect the deficits, in this case, take advantage of X3D’s relative
isolation and agree quickly to build widgets that DO reduce the authoring load
and are sharable among the local software ecosystem. </span></font></p><div>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy"> </span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy">VRML/X3D browser vendors should be
collapsing the space for ease of authorship * maintenance, or roughly, how much
time can be spent making new assets vs maintaining viable stock resources.</span></font></p></div></div></div></blockquote><div>One of the main benefits of the declarative nature of X3D is that it caters for all the non programmers - allowing them to create using even the simplest of tools. It should be the same for creating mutiuser networked content.</div>
<div><br></div><div>Interestingly, Chris Marrin is proposing a declarative layer for webGL, without which it would remain a programmers tool. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="blue"><div><div>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy"> </span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy">Ultimately content domains like biological
domains cohere in the face of novelty through practice, memory and feedback.
A framework of response domains maps the services to the organizations
that perform them in response to the panarchies that authorize them in response
to the event/incident type. That is the key to resilience.</span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy"></span></font></p></div></div></div></blockquote><div>hmm - you lost me :P</div><div><br></div><div>
chris </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="blue"><div><div><p class="MsoNormal"><font class="Apple-style-span" color="#000080" face="Arial"><br>
</font></p></div></div></div></blockquote></div><br>