[x3d-public] x3d v4 proposed changes > 2 opensource criteria > any that are short

[GPU Group]

INVENTORY
FREEWRL
* X3Dv4 Implementations
   https://www.web3d.org/x3dv4-implementations
1) 43 Projective Texture Mapping
x freewrl does not implement, document is mistaken
2) 23.4.4 NavigationInfo > TURNTABLE
* freewrl implemented
(other freewrl navmodes and related not in v3.3:
DIST - explicit control over distance to pivot point for examine, turntable
- touchpads don't need RMB
SHIFT - turns off sensors
HOVER - isOver mode (useful for touch pad - allows triggering of isOver
only)
PEDAL - can drag 'floating cursor' in steps
SPHERICAL - like FLY: YAWPITCH except rotations constrained to viewpoint
local axes)
subsets of FLY: YAWZ, XY, YAWPTICH,ROLL)
3) GeoSpatial > GeoOrigin - freewrl still allows in v3.3, never deprecated
in freewrl
4) The rest freewrl has not implemented
/FREEWRL
Does this table miss anything?
/INVENTORY
-Doug Sanden
PS who's doing projective texture mapping? Should start with that?


On Mon, Jan 27, 2020 at 11:59 AM GPU Group <gpugroup at gmail.com> wrote:

> INVENTORY
> FREEWRL
> * X3Dv4 Implementations
>    https://www.web3d.org/x3dv4-implementations
> 1) 43 Projective Texture Mapping
> x freewrl does not implement, document is mistaken
> 2) 23.4.4 NavigationInfo > TURNTABLE
> * freewrl implemented
> (other freewrl navmodes and related not in v3.3:
> DIST - explicit control over distance to pivot point for examine,
> turntable - touchpads don't need RMB
> SHIFT - turns off sensors
> HOVER - isOver mode (useful for touch pad - allows triggering of isOver
> only)
> PEDAL - can drag 'floating cursor' in steps
> SPHERICAL - like FLY: YAWPITCH except rotations constrained to viewpoint
> local axes)
> subsets of FLY: YAWZ, XY, YAWPTICH,ROLL)
> 3) GeoSpatial > GeoOrigin - freewrl still allows in v3.3, never deprecated
> in freewrl
> 4) The rest freewrl has not implemented
> /FREEWRL
> Does this table miss anything?
> /INVENTORY
>
>
> On Mon, Jan 27, 2020 at 11:14 AM Don Brutzman <brutzman at nps.edu> wrote:
>
>> Thanks for writing Doug.
>>
>> On 1/27/2020 6:01 AM, GPU Group wrote:
>> > A rule of web3d.org <http://web3d.org> is that changes to the spec
>> need a least 2 opensource implementations.
>>
>> * Web3D Standards Adoption Process
>>    https://www.web3d.org/standards/adoption-process
>>
>> 5.c. "Identify at least two independent and interoperable implementations
>> (at least one should be open source)"
>>
>> > Q. are there any proposed changes that do not yet have 2 opensource
>> implementations?
>>
>> Yes, plenty.  We have not taken a recent inventory of features yet, but
>> will be tracking that at
>>
>> * X3Dv4 Implementations
>>    https://www.web3d.org/x3dv4-implementations
>>
>> Our prominent open-source implementations for X3Dv3.3 include FreeWrl,
>> X_ITE, X3DOM, Castle Game Engine.  Soon Xj3D will be back on the table as
>> well.  There are also non-rendering X3Dv4 implementations for Java,
>> JavaScript, Python, conversions and validation.  Not sure about Titania but
>> presumably yes.  X3D-Editv4 is on the horizon. Interestingly everything on
>> this list is open source.
>>
>> Hoping that FreeWrl developers are keen to keep their record-setting X3D
>> support accomplishments continuing!  8)
>>
>> All feedback welcome, appreciate your many efforts.
>>
>> > Thanks,
>> > Doug Sanden
>> > -freewrl
>>
>> 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/20200127/53a57192/attachment.html>