1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
|
<HTML>
<HEAD>
<TITLE>VRweb customization</TITLE>
</HEAD>
<BODY background="vrwebbg.gif">
<H1>VRweb customization</H1>
<p>
<IMG ALT="VRweb" WIDTH="129" HEIGHT="40" SRC="vrwebsmall.gif">
<p>
<A name="cmdargs"></A>
<H2>Command line arguments</H2>
<p>
<code>-h</code>, <code>-help</code><br>gives a short description of
possible command line arguments.
<p>
<code>-verbose</code><br>turns on verbose output (incl. IPC
communication); use it to locate VRweb crashes (if they should ever
happen...) and include the output in the bug report
<p>
<code>-lang[uage] lg</code><br>sets the language of the user interface
to one of
<code>[english|german|french|italian|spanish|korean|japanese|styrian]</code>.
<p>
There are currently no plans for supporting other languages. Please,
send bug reports or information requests in English or German only.
<p>
<code>-URL url</code><br>base URL for relative references (typically
set via <code>-URL %u</code> in ~/.mailcap).
<p>
<code>-remote file</code><br>open file in a running VRweb instance or
create a new VRweb window if none found. It is not possible to
redirect stdinput to a remote instance. However the optional FILE
argument after all options allows this using a <code>-</code>.
<p>
<code>-getRemoteID</code><br>determines the X11 window ID of a running
VRweb instance or 0x0 if none found. Exits afterwards.
<p>
<code>-remoteViewpoint</code><br>make a running VRweb instance jump to
a named viewpoint, defined with argument -URL _baseurl_#camera, and
exit.
<p>
<code>-helpDir dir</code><br>directory or URL where to find on-line
help files. Defaults to <code>~/.vrweb/help</code>.
<p>
<code>-fontDir dir</code><br>directory of VRweb font files. Defaults
to <code>~/.vrweb/fonts</code>.
<p>
<code>-bg3d color</code><br>set scene background color. Color
specified as for <A href="#commonargs">-bg</A>.
<p>
<code>-draw[mode]</code><br>select the initial drawing mode to be one of
<code>[wireframe|hiddenline|flat|smooth|texturing]</code>
<p>
<code>-intdraw[mode]</code><br>selects the interactive drawing mode to be one of the list above
or <code>same</code> to use the same mode during navigation too.
<p>
<code>-speed</code><br>sets an (overall) speed factor for navigation
<p>
<code>-alphaplanes</code><br>inquire visual with alpha-bitplanes.
Their use in VRweb is limited to the "quality polygon antialiasing"
option (OpenGL version). They are not needed for transparency.
<p>
<code>-mesabackbuf</code><br>selects the backbuffer for Mesa to be one of
<code>[pixmap|image|auto]</code>. Pixmap transfers each drawing
command immediately to the XServer. Image causes all drawings to be
made into an XImage, which is transfered to the XServer when complete;
shared memory usage (only available when displayed locally) makes this
transfer fast. The default setting auto uses image for shaded views
and pixmap for wireframes.
<p>
<code>-singlebuf</code><br>turns off double buffering for 3D
renderings. Usually slower than double buffering. OpenGL however may
provide a X-visual with greater depth.
<p>
<code>-indirect</code><br>render OpenGL through X-server (slower).
<p>
<code>-mosaic</code><br>use mosaic for anchor requests and on-line help
(else netscape).
<p>
<code>-local</code><br>force WWWInline and Texture2 to be searched as local files.
<p>
<A name="commonargs"></A>
<b>The following command line options are common to all InterViews applications:</b>
<p>
<code>-bg background</code>, <code>-fg foreground</code>, <code>-flat
col</code><br>select the color for background, foreground and flat GUI
elements respectively. Specify colors with symbolic names (white,
black, green etc.) or hexadecimal RGB values: <code>#RRGGBB</code>
(you can get them also from the color chooser).
<p>
<code>-font fn</code><br>selects the font or fontset. See
SceneViewer.ad for details.
<p>
<code>-display dis</code><br>the display where VRweb should be shown. Normally
determined by environment variable $DISPLAY.
<p>
<code>-visual vClass</code><br>selects the visual class. Valid settings are:
PseudoColor, TrueColor, DirectColor, StaticGray, GrayScale, StaticColor. Normally
VRweb uses the default visual to avoid color map flashing ("technicolor").
<p>
<code>-visual_id 0xID</code><br>selects a visual id for the window. See
xdpyinfo for visual-ids available on your XServer.
<p>
<code>-dbuf</code>, <code>-nodbuf</code><br>turns on (default) or off (less memory
usage) double buffering for GUI elements.
<p>
<code>-sgimotif</code>, <code>-motif</code>, <code>-openlook</code><br>
selects the GUI style to be SGI-like Motif (default), "normal" Motif
or OpenLook.
<p>
<code>-xrm '*attribute:value'</code><br>specifies an arbitrary
Xattribute on commandline.
<p>
<HR>
<p>
<H2>X-Attributes</H2>
<p>
VRweb follows the naming scheme of Xdefaults for <A
HREF="http://www.iicm.edu/harmony-technical">Harmony</A>, the <A
href="http://www.iicm.edu/hyperwave">HyperWave</A> authoring tool for
Unix/X11 (Hyper-G client). The place of VRweb in the resource
hierarchy is
<p>
<code>Harmony.Scene</code>
<p>
Please refer to file <code><b>SceneViewer.ad</b></code> in the UNIX
distribution of VRweb, for a list of Xattributes recognized by VRweb
and their default values.
<p>
<HR>
<p>
Back to <A HREF="vrwebhlp.html">overview</A>.
</BODY>
|
