[x3d-public] X3D working group meeting 14 AUG 2020: status conference, webinars, X3DCSAIL, ISO, X3D4

[John Carlson]

Interesting, from field tooltips:

*Warning:* setting a value is not allowed for ExternProtoDeclare field
declarations, since original ProtoDeclare initializations or local
ProtoInstance fieldValue initializations take precedence.
*Warning:* not allowed for field variables with accessType inputOnly or
outputOnly.
*Warning:* initialization value is not allowed if this field is part of a
Script interface and has a corresponding IS/connect definition.

John

On Fri, Aug 14, 2020 at 8:36 PM John Carlson <yottzumm at gmail.com> wrote:

> It looks like Andreas adds a watcher to fields in ProtoDeclare handling,
> among other things.
>
> On Fri, Aug 14, 2020 at 8:12 PM John Carlson <yottzumm at gmail.com> wrote:
>
>> Is there an IS (International Standard), as opposed to a CD (Committee
>> Draft?)?
>>
>> I was guessing once I got field support working, that events would be
>> automatic? Not really sure...  I guess I'll have to do the set_, _changed
>> stuff, but I'm not really sure.  Maybe I should do initializing in the
>> initialize() method?
>>
>> I haven't figured out how to call shutdown() yet. document.onunload?
>>
>> It would seem like if I copied field stuff from Composed Shader/Shader
>> Part, that I would get the default fields?  I am not really sure.
>> Should I look at Andreas' ProtoDeclare? Are there other places with
>> fields?
>>
>> Thanks,
>>
>> John
>>
>> On Fri, Aug 14, 2020 at 3:44 PM Don Brutzman <brutzman at nps.edu> wrote:
>>
>>> Congrats on excellent progress!
>>>
>>> On 8/14/2020 10:51 AM, John Carlson wrote:
>>> > Approach of X3DScript tag being developed for X3DOM:
>>> >
>>> > 1.  Field support
>>> > 2. Event support between routes and scripts
>>> > 3. URL and CDATA section supported with “new Function”
>>> > 4. Call initialize function
>>>
>>> there is also an overridable shutdown() function which is very similar.
>>>
>>> * Extensible 3D (X3D) language bindings, Part 1: ECMAScript, ISO/IEC CD
>>> 19777-1:201x
>>>
>>> https://www.web3d.org/documents/specifications/19777-1/V3.3/index.html
>>>
>>> p.s. Dick, it looks like we have a stray "x" in that specification's
>>> title.
>>>
>>> > Current outstanding tasks:
>>> >
>>> > 1.   Deal with non specified field values...what are the defaults?
>>>
>>> All fields have default values defined in spec.  Tooltips also list them
>>> as a convenience.
>>>
>>> * X3D Architecture Specification: 5 Field type reference defines default
>>> values for each field type.
>>>
>>> https://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/fieldsDef.html
>>>
>>> > 2.  Insure events are flowing
>>>
>>> "If it ain't moving, it ain't 3D." - Andy van Dam
>>>
>>> all the best, Don
>>> --
>>> Don Brutzman  Naval Postgraduate School, Code USW/Br
>>> brutzman at nps.edu
>>> Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA
>>>  +1.831.656.2149
>>> X3D graphics, virtual worlds, navy robotics
>>> http://faculty.nps.edu/brutzman
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20200814/3f2e224e/attachment.html>