57067 - RFE: VRML Support

Status: RESOLVED WONTFIX

(SeaMonkey :: UI Design, enhancement, P5)

Description

[Jason Kersey]

I want to step into my 3d world of fun, but cannot do so in mozilla.  Fix this
please.

Comment 1

[David Krause]

Sweet, now I need to find my VRML projects from freshman year ES130.

BTW: Why is this in the Evangelism component?

Comment 2

[timeless]

Are we sure that vrml plugins don't work w/ mozilla?

Comment 3

[Doron Rosenberg (IBM)]

over to plugins

Comment 4

[Braden]

Hehe... Wow, there are actually other people interested in this? :-)

I actually have a project to do this well underway. It's an XPCOM plugin called
Semblance, and it uses the OpenVRML library, for which I am a co-maintainer.
Look here: <http://sourceforge.net/projects/openvrml/>

I don't have any of the plugin source in CVS yet, but that should change shortly
after the 0.9.0 release of OpenVRML (which will hopefully happen later this
month). You can assign this bug to me if you want, though I'm really not sure
this should be considered a Mozilla bug.

Comment 5

[Braden]

BTW, if folks are interested in seeing existing (legacy API) VRML plugins work
with Netscape, I suggest filing bugs specific to the problem plugin, and use the
4xp keyword.

Comment 6

[Matthias Versen [:Matti]]

*** Bug 152211 has been marked as a duplicate of this bug. ***

Comment 7

[rubydoo123]

what plug-in is being referred to? and can you please supply a testcase for this
issue.

Comment 8

[Braden]

Resolving INVALID. If there are problems with a specific plug-in, file a new bug.

Comment 9

[shrirang khanzode]

.

Comment 10

[timeless]

*** Bug 152211 has been marked as a duplicate of this bug. ***

Comment 11

[timeless]

doron carelessly sent this to plugins, my question was not a suggestion the vrml
plugins didn't work in mozilla.

Comment 12

[timeless]

nobody

Comment 13

[Braden]

timeless: Then what *is* this bug about?

If this is a suggestion that Mozilla should support VRML directly without a
plug-in, then I believe this should be marked WONTFIX.

Comment 14

[Aaron Kaluszka]

*** Bug 182009 has been marked as a duplicate of this bug. ***

Comment 15

[Braden]

Any VRML support should be added with a plug-in. WONTFIX.

Comment 16

[Manko]

Can't agree with WONTFIX.

VRML (more precisely, X3D) is an XML-based markup language. Main Mozilla policy
is AFAIK native support of usable and widespread XML formats, manipulating it
via DOM interface etc. For example, we have integrated in Mozilla such markups
as MathML, RDF, XUL, SOAP, XSL and (in future) SVG and WML.

Plugins are a legacy from older Netscape versions, it have very limited and
non-transparent object model for scripting.

I guess that power and flexibility of DOM interface to X3D, ability to create XP
Mozilla code for 3D support and, last but not least, trend to using 3D elements
in user interface (in MacOS X Jaguar, for example) early or late will raise this
issue again.

Thus, please, remove WONTFIX resolution.

Comment 17

[Braden]

1. This bug is about VRML, which is *not* XML based.

2. X3D will supposedly have multiple encodings--one of which will supposedly be
XML-based, but none of which is currently specified. Presumably those
specifications are forthcoming.

So if X3D XML support is what you want, that belongs in another bug. *But*...
Incorporating this directly into the browser is a huge task that may require an
OpenGL-based Mozilla frontend (a huge task by itself) in order to perform
acceptably.

Comment 18

[Zook Valem]

>>1. This bug is about VRML, which is *not* XML based.
If someone ever get an itching finger to say something against this then take a
look at this sample VRML code before saying anything about it.

--snip--
#VRML V2.0 utf8
Group {
	children [
		Shape { appearance Appearance { 	
					material DEF mat Material {
						emissiveColor 0.2 0.2 0.2} }
			geometry Sphere {}
		}
		DEF ts TouchSensor {}
	]
}

DEF switchScript Script {
	eventIn SFBool in2
	field SFColor out 0 0 0
	field SFNode m USE mat

	directOutput TRUE

	url "javascript:

		function in2(value, timestamp) {

			if (value) {
				out[0] = 0.5;
				out[1] = 0.5;
				out[2] = 0.5;
			}
			else {
				out[0] = 0.2;
				out[1] = 0.2;
				out[2] = 0.2;
			}
			m.emissiveColor = out;
		}"
}

ROUTE ts.isOver TO switchScript.in2
--snip--