[X3D-Public] Historical question

[Tony Parisi]

Oh in Scripts?

No you can't. That was a purposeful design decision in VRML97-- for IMHO
really obscure reasons but I am sure there are people on this list who can
properly defend it.

We lifted that restriction in X3D. I am sure there are people on this list
who could properly malign that decision :-p

So, yes, to be strictly compliant, a VRML97 browser would not allow it.
Apparently many implementors decided to go the pragmatic route vs.
parochial.

I bet if you feed FreeWRL a VRML-encoded X3D file with the correct header
line, it won't bitch about this. Can you make that change and get around the
issue?

Tony


On Mon, Jun 6, 2011 at 10:52 AM, Dave A <dave at realmofconcepts.com> wrote:

>  Thanks. The reference pointed to me by FreeWRL contained:
>
>  [image: +]6.40 Script
>
> *Script {*
>   exposedField MFString *url           []*
>   field        SFBool   *directOutput  FALSE*
>   field        SFBool   *mustEvaluate  FALSE*
>   # *And any number of*:*  eventIn      eventType eventName**  field        fieldType fieldName initialValue**  eventOut     eventType eventName**}*
>
>
> Note: no mention of 'exposedField' thus not implemented.
>
> FWIW: Vivaty Studio actually creates some non-spec code (capital BOOLEANS)
> and
> uses 'exposedField' in x3dv instead of 'inputOutput'
>
>
>
> On 6/6/2011 10:20 AM, Tony Parisi wrote:
>
> Here's the reference:
>
>
> http://www.web3d.org/x3d/specifications/vrml/ISO-IEC-14772-VRML97/part1/concepts.html#4.7
>
> Tony
>
> On Mon, Jun 6, 2011 at 10:19 AM, Tony Parisi <tparisi at gmail.com> wrote:
>
>> exposedField was definitely in the VRML spec.
>>
>>
>>
>> On Mon, Jun 6, 2011 at 9:33 AM, Dave A <dave at realmofconcepts.com> wrote:
>>
>>> Hey all,
>>>
>>> I've just started using FreeWRL and was surprised that it was rejecting
>>> scripts with 'exposedField' on them. Now, I've used Contact, Cortona,
>>> Flux/Vivaty, and Instant Player, and they all support this. But the FreeWRL
>>> guys point out that 'exposedField' is not in the VRML spec (it is in the X3D
>>> spec but as 'inputOutput').
>>>
>>> So, how did this 'exposedField' come to be, when, and if it's in so many
>>> popular browsers, how is it not in at least an Amendment, and (to the
>>> FreeWRL folks), why not implement it there?
>>>
>>> Thanks for any enlightenment you may provide.
>>>
>>> Dave A.
>>>
>>> _______________________________________________
>>> X3D-Public mailing list
>>> X3D-Public at web3d.org
>>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>>>
>>
>>
>>
>>  --
>> Tony Parisi                             tparisi at gmail.com
>> CTO at Large                         415.902.8002
>> Skype                                     auradeluxe
>> Follow me on Twitter!             http://twitter.com/auradeluxe
>>
>>
>>
>
>
> --
> Tony Parisi                             tparisi at gmail.com
> CTO at Large                         415.902.8002
> Skype                                     auradeluxe
> Follow me on Twitter!             http://twitter.com/auradeluxe
>
>
> ------------------------------
>
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 10.0.1382 / Virus Database: 1511/3680 - Release Date: 06/04/11
>
>


-- 
Tony Parisi                             tparisi at gmail.com
CTO at Large                         415.902.8002
Skype                                     auradeluxe
Follow me on Twitter!             http://twitter.com/auradeluxe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20110606/df7c8218/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 175 bytes
Desc: not available
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20110606/df7c8218/attachment-0001.gif>