[X3D-Public] X3DOM - navigation type TURNTABLE

[doug sanden]

>
> "Turntable" like interaction are today very common navigation methods in 3d modelling and exploring application. I believe this could be useful for X3D in general but don't like the typeParams interface to much. There is space for improvement.
>
>>> The turntable navigation example announced by X3DOM is nice. Anyone else try it?
>>>
>>> http://www.x3dom.org/?p=3536
>>>
>>> http://www.x3dom.org/x3dom/example/x3dom_turntable.html
>>>
>>> <navigationInfo id='nav' headlight='false' type='turntable' typeParams="0 0 0.2 1.4"></navigationInfo>
>>>
>>> Wondering if we should add TURNTABLE to our list of navigation types supported in X3D v3.4. Seems useful. I've added it to the candidate list, discussion will be welcome.
>>>
>>
>> Seems useful - tilt-unconstrained examine mode can be awkward.
>>
>>> http://web3d.org/wiki/index.php/X3D_version_3.4_Development
>>>
>>> Also wondering if there are references regarding this approach, perhaps in IEEE VR conference?
>>>

To solve spherical panorama, I introduced navigationInfo type="YAWPITCHZOOM" (I should have named it type="freewrl_YAWPITCHZOOM" to keep with the specs.

PROCEDURAL NAVIGATION
Q. could/should there be a way to add a script .js to navigationInfo, so as to minimize the proliferation of navigation types, and allow a unique navigation type written for one browser to work in another?
ie
<navigationInfo type='procedural' typeParams='--enter javascript here--'/>
- is there a common set of things/inputs/outputs that all navigationInfo custom types could script against? For example:
- current bound viewpoint node
- origin (or is this always the viewpoint?)
- other point or pose ie a target viewpoint pose in a transition (perhaps another navigation info field to reference the other node)
- time, dtime - for transition types