[X3D-Public] Historical question

[Dave A]

Jon,

Hi, yes, Tony's last post explains it all very well. Looks like I'll 
need to split my fields.

Dave

On 6/6/2011 11:03 AM, John Stewart wrote:
> Hi Dave;
>
> Apologies for not being part of the FreeWRL conversation, but in reference to:
>
>> 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?
>
> I did a google search, and found lots of web pages stating that you can't do it. eg:
>
>
> "Note: you can't define an exposedField in a Script. " :
> http://www.lighthouse3d.com/vrml/tutorial/script.shtml
>
>
> under the section "Scripting Extensions":
> http://www.bitmanagement.com/developer/contact/scripting.html
> they allow exposedFields.
>
> > From Patrick; (grep the email archives if you don't know who Patrick is):
> "	• The VRML standard does not allow exposed fields in script interfaces. Contact nevertheless supports them. I've replaced exposed fields by a combination of event-in slots, event-out slots and fields."
>
> http://forum.instantreality.org/index.php?topic=200.0
>
>
> Please see section A.2.3 here: (check out the URL)
> http://www.web3d.org/x3d/specifications/ISO-IEC-19775-2.2-X3D-SceneAccessInterface/Part02/vrml97.html
>
> ------
>
> As you can see, lots of interesting discussions....
>
>
> I'll catch up with the FreeWRL mailing list later on today, and see what the emails are about!
>
>
> JohnS.
>
>
>
> -----
> 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
>
>
>