[X3D-Public] proposed feature: ability for scene to query browser regarding node support

[Joe D Williams]

> > I can't imagine it being terribly difficult. But.... an additional 
> > api
> call is not going to prevent a browser from misrepresenting it's ...


Also, if looking at nodes, might as well check fields, for example is 
Viewpoint CenterOfRotation supported?

Overall, I think the queries for components and levels should suffice 
for authoring and publishing.

Joe


----- Original Message ----- 
From: "Rex Melton" <rex.melton at jeospace.net>
To: "Don Brutzman" <brutzman at nps.edu>
Cc: <x3d-public at web3d.org>
Sent: Thursday, April 04, 2013 10:10 AM
Subject: Re: [X3D-Public] proposed feature: ability for scene to query 
browser regarding node support


> On 4/4/2013 12:16 PM, Don Brutzman wrote:
>> Yes, excellent description of what is specified.  Thanks Rex!
>>
>> I certainly agree, it is an important and valuable feature that is 
>> already provided in the specification.  However, the widespread and 
>> difficult problem for authors is that browsers don't match their 
>> internal conformance to what is required.. feature support is 
>> usually a "work in progress."
>>
>
> If a browser lies to you about it's supported profiles and 
> components - then it should be taken out to the wood shed and be 
> flogged.
>
>> So, am wondering if this potential added feature, asking about a 
>> specific node, might help authors deal with this long-standing 
>> problem.
>>
>> Do you think such a Browser API call would be simple enough to 
>> implement and maintain in Xj3D?
>>
>
> I can't imagine it being terribly difficult. But.... an additional 
> api call is not going to prevent a browser from misrepresenting it's 
> capabilities.
>
>>
>> On 4/4/2013 8:26 AM, Rex Melton wrote:
>>>
>>> Support information is available, but not in a 'is my node 
>>> supported'
>>> function call.
>>>
>>> An author can determine the supported components and levels by 
>>> querying
>>> the browser object through the SAI.
>>>
>>> The component info object contains the max supported level. Nodes 
>>> and
>>> their features are spec'ed for each component by level.
>>>
>>>
>>>
>>> On 4/4/2013 10:45 AM, Don Brutzman wrote:
>>>> On 4/4/2013 7:37 AM, Joe D Williams wrote:
>>>>> Hi Don,
>>>>>
>>>>>> query browser regarding node support
>>>>>
>>>>> As Leonard mentioned in the meeting, mostly much better to 
>>>>> depend upon
>>>>> existing declarations.
>>>>
>>>> Sorry Joe, but I'm not following, please elaborate.
>>>>
>>>> Regarding existing declarations:
>>>>
>>>> - Existing declarations of X3D version/profile/component in
>>>> specification/schema/DTD are exact
>>>> - Browser declarations in documentation are often missing or 
>>>> change
>>>> over time
>>>> - An author doesn't know in advance whose browser/player will be 
>>>> used
>>>> for their scene, and so cannot be certain of support
>>>>
>>>> The idea that I'm suggesting is, should an authored script be 
>>>> able to
>>>> check with the Browser to see if a given node is supported?
>>>> - Being able to check this allows the author to provide an 
>>>> alternative
>>>> - Also allows at least some form of graceful declaration
>>>> - Example: "Sorry, your X3D browser is missing CAD support using
>>>> NURBS, please click here to see the video instead"
>>>>
>>>>
>>>> all the best, Don
>>>
>>>
>>> _______________________________________________
>>> X3D-Public mailing list
>>> X3D-Public at web3d.org
>>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>>>
>>
>>
>> all the best, Don
>
>
> _______________________________________________
> X3D-Public mailing list
> X3D-Public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org