OpenVRML is a VRML and X3D browser plug-in and C++ toolkit for incorporating VRML/X3D support into applications. It provides VRML97 and Classic VRML X3D parsers, a runtime, and an OpenGL renderer as C++ libraries. The renderer is fully separate from the runtime library so that users can also provide their own renderer. The OpenVRML browser is provided as a D-Bus service, and is embeddable in host applications using XEmbed. The distribution provides both a stand-alone host and a host that runs as a Mozilla plug-in.
Re: Spaces, the filename frontier...
> % Or to better yet improve the
> % configuration system, we could
> % /System Preferences/*.xml
> % It's about time we migrate folder
> % names to Plain Damn English. If
> % has a real religious problem with
> this, [...]
> A big problem with that is that many
> existing shell scripts assume that there
> are no spaces in file names. The shell
> splits lines into tokens on whitespace.
> Spaces in filenames thus cause trouble
> unless the scripts are carefully
> written. (insert perl banner ad here).
> Zsh and Bash both support array
> variables, and filenames can be gotten
> via "find -print0"...
> It would take a certain amount of
> effort to audit all scripts for this
> weakness. It would also require the
> addition of a clause in the distribution
> policy document, and once that's done,
> all new scripts would require audits for
> "sif" (space if filename) bugs.
A bigger problem is internationalization. If it's worth doing in English, it's worth doing in other languages. Then you have a situation where software that wants to deploy itself can't be sure what the directory names are without consulting some directory. Windows does this. It is needlessly complicated.
The filesystem hierarchy should be kept succinct and standard. Clarity to the Average User--where it's appropriate--should be taken care of by an abstraction layer.
Re: When will Galeon be independant?
> % It's already independent. It uses
> % Gecko, the same engine that
> % uses. It does not use Mozilla.
> Well, how would one remove
> unneccessary pieces of the mozilla
> and keep Galeon running? I'd like to
> shrink that huge beast.
It'd be nice if we could install "just Gecko". Unfortunately, the Mozilla folks seem to have made it rather difficult to deploy Gecko as a module separate from the rest of the browser. This is fixable in theory; but it would be a lot of work, and it just might take an uphill battle or two to get it done.