[X3D-Public] X3D-Edit notes, was got MultiTexture and MultiTextureTransform example scenes?

Michalis Kamburelis michalis.kambi at gmail.com
Fri May 3 03:37:49 PDT 2013


Don Brutzman wrote:
> I've added view3dscene as a built-in supported player. X3D-Edit updated
> and deployed.
>
> If there are default values for the installation paths on MacOSX or
> Linux that you might recommend, am happy to add them into the
> configuration file. I listed a (likely) configuration path for Windows
> (XP or 64) as
>
> C:\Program Files (x86)\view3dscene\view3dscene.exe
>

view3dscene paths:

- Windows: We don't provide Windows installers (for now), only zip file 
to unpack wherever you want. This means there really is no simple 
default path.

"C:\Program Files (x86)\view3dscene\view3dscene.exe" may be correct only 
for a small subset of users, even if we did use an installer. Various 
Windows versions and configurations have different locations for program 
files. The " (x86)" suffix is only used on 64-bit Windows machines for 
32-bit programs, as far as I know. Right now we only release 32-bit 
view3dscene for Windows. But it will likely change --- when more Windows 
systems are 64-bit, we will start to release 64-bit view3dscene as well 
(you can already compile it from sources, we just don't officially 
release it *yet*).

The bottom line is, hardcoding such location is not a stable solution... 
For view3dscene, and for all other Windows programs too.

We can record view3dscene.exe location in the Windows registry, this 
seems a standard way on Windows to make your exe location known. Would 
it help x3d-edit? Can it read Windows registry to get the location?

- Mac OS X: users can drag the application anywhere, as is standard for 
Mac OS X. Most users probably drag it to /Applications or 
$HOME/Applications, these are the places to look for. Note that next 
view3dscene releases will be distributed as standard Mac OS X .app 
bundle, so the view3dscene binary will be actually under a subdirectory 
like /Applications/view3dscene.app/Contents/MacOS/view3ddscene .

This is all a standard approach on Mac OS X, as far as I know. If we can 
do anything better please let me know :)

- Linux: If downloaded from our tar.gz release, users can unpack it 
anywhere. Most users will probably put this somewhere on $PATH, so you 
can search the environment variable $PATH for view3dscene/tovrmlx3d 
binaries. When installed from packages (Debian packages are coming), we 
will be in /usr/bin/view3dscene (that's always on $PATH anyway).

Hope this helps :),
Michalis



More information about the X3D-Public mailing list