VRML - Changes X/VRML97

Author

Changes X/VRML97

Joerg Scheurich aka MUFTI

2005-10-27, 6:18 am

Hi,

Currently i found out, that to convert from a VRML97 (ISO/IEC 14772:1997)
file to a X3D x3dv file you need to exchange

field -> initializeOnly
eventIn -> inputOnly
eventOut -> outputOnly
exposedField -> inputOutput

LOD.level -> LOD.children
Switch.choice -> Switch.children
Collision.collide -> Collision.enabled

You also need to select a PROFILE as part of the new X3D header, e.g. for
a background with 2 skyColors, you need the profile "Full" 8-(

So you need to exchange

#VRML V2.0 utf8

with something like

#X3D V3.0 utf8
PROFILE Immersive

or

#X3D V3.0 utf8
PROFILE Full

Are there additional things to change ?

so long
MUFTI
--
Englisch: Deutsch:
collator die Zusammentragmaschine
to collateralize [finan.] lombardieren
(von dict.leo.org)

Joe D Williams

2005-10-27, 6:28 pm

"Joerg Scheurich aka MUFTI" <rusmufti@bera.rus.uni-stuttgart.de> wrote in
message news:djq4rm$64q$2@infosun2.rus.uni-stuttgart.de...
> Hi,
>
> Currently i found out, that to convert from a VRML97 (ISO/IEC 14772:1997)
> file to a X3D x3dv file you need to exchange
>
> field -> initializeOnly
> eventIn -> inputOnly
> eventOut -> outputOnly
> exposedField -> inputOutput

OK. this is easier to understand, right?

>
> LOD.level -> LOD.children
> Switch.choice -> Switch.children
> Collision.collide -> Collision.enabled

yes

>
> You also need to select a PROFILE as part of the new X3D header, e.g. for
> a background with 2 skyColors, you need the profile "Full" 8-(
>
> So you need to exchange
>
> #VRML V2.0 utf8
>
> with something like
>
> #X3D V3.0 utf8
> PROFILE Immersive
>
> or
>
> #X3D V3.0 utf8
> PROFILE Full

should work

>
> Are there additional things to change ?

the script must be ecmascript

>
> so long
> MUFTI
> --
> Englisch: Deutsch:
> collator die Zusammentragmaschine
> to collateralize [finan.] lombardieren
> (von dict.leo.org)

Best Regards,
Joe

Braden McDaniel

2005-10-27, 10:18 pm

On Thu, 2005-10-27 at 08:58 +0000, Joerg Scheurich aka MUFTI wrote:
> Hi,
>
> Currently i found out, that to convert from a VRML97 (ISO/IEC 14772:1997)
> file to a X3D x3dv file you need to exchange
>
> field -> initializeOnly
> eventIn -> inputOnly
> eventOut -> outputOnly
> exposedField -> inputOutput

This isn't strictly required. The old names are still valid; they are
just deprecated.

--
Braden McDaniel e-mail: <braden@endoframe.com>
<http://endoframe.com> Jabber: <braden@jabber.org>

Joerg Scheurich aka MUFTI

2005-10-28, 6:40 pm

>> Are there additional things to change ?

> the script must be ecmascript

The old java API is no longer valid in X3D ?

May X3D browser no longer have additional languages (like perl) for VRML scripts ?

so long
MUFTI
--
Um das zu pruefen und falls notwendig, zum Zerlegen der Festplatte
gebrauche Win95 Disk Zerleger, welchen Du in deinem Programm:
Zubehoer-System Werkzeug Akte hast.

Joe D Williams

2005-10-29, 6:30 pm

re: access types:

>

> This isn't strictly required. The old names are still valid; they are
> just deprecated.

I do not think this is true.
There is no 'intermediate' or 'transitional' spec and
deprecated is not found in the spec.
in this regard, it is either VRML97 or it is X3D.
Best Regards,
Joe

"Braden McDaniel" <braden@endoframe.com> wrote in message
news:1130461953.13480.39.camel@localhost.localdomain...
> On Thu, 2005-10-27 at 08:58 +0000, Joerg Scheurich aka MUFTI wrote:
>
> This isn't strictly required. The old names are still valid; they are
> just deprecated.
>
> --
> Braden McDaniel e-mail: <braden@endoframe.com>
> <http://endoframe.com> Jabber: <braden@jabber.org>
>

Joe D Williams

2005-10-29, 6:30 pm

"Joerg Scheurich aka MUFTI" <rusmufti@bera.rus.uni-stuttgart.de> wrote in
message news:djtqvn$b1h$1@infosun2.rus.uni-stuttgart.de...
>
>
> The old java API is no longer valid in X3D ?

which one? Please look at the X3D spec.

http://www.web3d.org/x3d/specifications/
ISO-IEC-19777-2-FDIS-X3DLanguageBindings-Java/
Part2/X3D_Java.html

>
> May X3D browser no longer have additional languages (like perl) for VRML
scripts ?

I think several would like to expand the spec
but now there is only ecmascript and java in X3D.
So, like VRML97 it is optional for the browser, but X3D.
>
> so long
> MUFTI

Thanks and Best Regards,
Joe

> --
> Um das zu pruefen und falls notwendig, zum Zerlegen der Festplatte
> gebrauche Win95 Disk Zerleger, welchen Du in deinem Programm:
> Zubehoer-System Werkzeug Akte hast.

Braden McDaniel

2005-10-29, 6:30 pm

On Sat, 2005-10-29 at 16:38 +0000, Joe D Williams wrote:
> re: access types:
>
>
>
> I do not think this is true.

It is.

> There is no 'intermediate' or 'transitional' spec and
> deprecated is not found in the spec.

"Deprecated" most certainly is found in the spec.

http://www.web3d.org/x3d/specificat...sicVRMLEncoding

> in this regard, it is either VRML97 or it is X3D.

I don't know what that means.

--
Braden McDaniel e-mail: <braden@endoframe.com>
<http://endoframe.com> Jabber: <braden@jabber.org>

Joe D Williams

2005-10-31, 6:44 pm

> "Deprecated" most certainly is found in the spec.
>
>
http://www.web3d.org/x3d/specificat...s-XML-ClassicVR
ML/Part02/concepts.html#ClassicVRMLEncoding

Sorry, Braden, I had forgotten about that instance of weakness.
I do think this only applies to Classic VRML encoding and not to
XML encoding. Anyway, don't use it. I doubt new browsers, or
even old ones really aiming at X3D, will allow it so failure is
guaranteed.

Best Regards,
Joe

"Braden McDaniel" <braden@endoframe.com> wrote in message
news:1130608487.13480.139.camel@localhost.localdomain...
> On Sat, 2005-10-29 at 16:38 +0000, Joe D Williams wrote:
>
> It is.
>
>
> "Deprecated" most certainly is found in the spec.
>
>
http://www.web3d.org/x3d/specificat...s-XML-ClassicVR
ML/Part02/concepts.html#ClassicVRMLEncoding
>
>
> I don't know what that means.
>
> --
> Braden McDaniel e-mail: <braden@endoframe.com>
> <http://endoframe.com> Jabber: <braden@jabber.org>
>

Braden McDaniel

2005-10-31, 10:28 pm

On Mon, 2005-10-31 at 22:51 +0000, Joe D Williams wrote:
> http://www.web3d.org/x3d/specificat...s-XML-ClassicVR
> ML/Part02/concepts.html#ClassicVRMLEncoding
>
> Sorry, Braden, I had forgotten about that instance of weakness.
> I do think this only applies to Classic VRML encoding and not to
> XML encoding. Anyway, don't use it.

"Avoid using it in new content" is generally the suggestion implied by
deprecation.

> I doubt new browsers, or
> even old ones really aiming at X3D, will allow it so failure is
> guaranteed.

Without any citation of specific instances, this seems like hand waving.
Conforming processors of the X3D Classic VRML encoding must support it.
If you know specifically of some that aspire to conformance and do not
support this, I'm sure it would be helpful to file bug reports.

--
Braden McDaniel e-mail: <braden@endoframe.com>
<http://endoframe.com> Jabber: <braden@jabber.org>

Joerg Scheurich aka MUFTI

2005-11-09, 7:01 pm

giles <giles@metalab.unc.edu> wrote:
> The intent is to not allow these constructs in the files. Do you have
> suggested changes to make this clear?

"deprecated name for inputOnly fields"

->

"deprecated name for inputOnly fields, that is not allowed in X3D files anymore"

> We deprecated the words because
> we thought readers of the spec would need to know about them.

I think, it was a good idea to make eventIn/eventOut etc. to a reserved
word, cause this could makes it easier, to write a combined
VRML97 -> X3D and X3DV -> X3D converted....

so long
MUFTI
--
If you have a thread that uses Sleep with infinite delay, the
system will deadlock.
(from the MSDN Documentation)