/usr/share/dx/java/htmlpages/earlier.htm is in dxsamples 4.4.0-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 | <html>
<head>
<meta http-equiv="content-type" content="text/html;charset=iso-8859-1">
<title>Java Explorer Status</title>
</head>
<body bgcolor="white">
<hr>
<h2>Changes in 2.0.0</h2>
<ul>
<li>
<li>Due to an bug in previous versions, you needed to start the Data Explorer user interface and the Data Explorer executive separately. That bug has been fixed. You should load nets saved with an earlier version and save them again.
<li>DXServer will use a single dxexec to service any number of connected browsers. This should enhance the scalability of Java Explorer. The startserver script understands a <i>-session</i> command line argument which allows you to configure the number of dxexecs which DXServer will start. You'll probably want to user multiple sessions only if you have multiple machines pointed to by your dxserver.hosts.
<li>Direct interaction uses visual cues which are similar to those in the Data Explorer user interface such as a rotation gnomon.
<li>The <i>-memory</i> argument now defaults to no explicit limit on the amount dxexec will allocate. This is the norm when using Data Explorer and should provide reasonable behavior given the default number of sessions which is 1.
<li>Now it should be easy to install web pages in directories of your choosing rather than having to use <i>installDir</i>/java/htmlpages. Several changes to the way dxui generates makefiles and html files and to the startserver script support this change. You may find it most convenient to have dxui generate a new makefile and html file for your existing nets in order to take advantage of these changes. Files generated with an earlier version of Java Explorer will continue to work, so no action is really required on your part.
<li>The issue to be aware and careful of is applets which share a codebase will be allowed to interoperate. From now on dxui will generate applet tags with a codebase="../". Then individual jar files are located relative to that codebase. The obvious alternative is an applet tag with a relative pathname in the code parameter which isn't legal.
<li>
<li>
<p>In addition to gif images and vrml worlds, dx objects can now be transfered into a web page through Java Explorer. This feature uses an ActiveX component in the web page and therefore works in Internet Explorer and not in Netscape. The ActiveX component uses a copy of Data Explorer installed on the machine which runs the browser in order to render its image. This also requires adding tear.exe to your path.</p>
<li>This technique should be useful for web pages which benefit from frequent camera manipulation.
<li>
<li>
<p>The net files you save for use with DXServer, have always used a special version of the Image macro. Now, the macro uses an internal cache setting of <i>CACHE_LAST</i> which should save memory.</p>
<li>
<li>This 2.0.0 release begins adding the ability to use a gui builder such as <a href="http://www.software.ibm.com/ad/vajava/about.htm">VisualAge</a> to combine Java Explorer's machine generated java code with customized gui interfaces for your web pages. Future releases will include examples of such applets. Combining the capabilites of Java Explorer with VisualAge involves importing Java Explorer's jar file, making an applet which subclasses dx.net.DXLinkApplication, and setting some of Java Explorer's properties. The documentation you would need for this is missing, so it's virtually impossible to do.
<li>
<li>A setting in your $HOME/DX file - DX*htmlDir - should be changed so that it does not include the htmlpages directory. For example:<br>
<br>
<code>DX*htmlDir: /usr/http/java<br>
<br>
</code>
<li>
<li>Two new settings in $HOME/DX are now used. They are <b>DX*userHtmlDir</b> and <b>DX*userJarFile</b>. The default settings are <b>user</b> and <b>user.jar</b> respectively. Consequently, dxui will generate makefiles which compile applets into user.jar and install user.jar into <i>htmlDir/userHtmlDir</i>. By default, all web pages generated by dxui will not be installed into <i>installDir</i>/java/htmlpages. Instead they'll be installed into a directory beside htmlpages.
</ul>
<h2>Changes in 1.0.4</h2>
<ul>
<li>Shift+Mouse Click in any Java Explorer Image applet will
cause the applet to pop its image up in a new browser window.
This enables the user to save the image.
<li>Java Explorer's web page generation mechanism will now automatically
generate applet tags in the .html file which result in the
content produced by the DXLOutput tool being displayed in an
applet running in the browser. Examples of this mechanism in
place are <a href="MutualFund.html" TARGET="_parent">MutualFund</a>
and <a href="ddi.html" TARGET="_parent">Thunderstorm Simulation</a>.
<li>The dx.net package in Java Explorer includes the
<a href="Status.htm#interfaces">dx.net.DXLinkHandler</a>
interface which an applet can implement in order
to handle output produced by a DXLOutput tool in a net.
<li>A new menu in the 'Execution' panel provides a selection of views -
Front, Back, Left, Right, etc.
</ul>
<h2>Changes from 1.0.3 to 1.0.4</h2>
<ul>
<li>Data-driven selector and selector list interactors were malfunctioning
on the second execution following receipt of new input values for
<i>stringdata</i> and <i>valuelist</i> inputs. They would continue to
malfunction until the user selected a new value in the interactor. The
specific symptom was that the selector or selector list tool would output
a value from its most recent user input or from the stored net if the
user had never entered a value.
<li>The mechanism by which DXServer erases old gif files malfunctioned
on the pc with an httpd program causing DXServer to erase these files
too soon. As a result, the browser's Java Console would contain error
messages indicating that <i>AppletClient couldn't load <filename>.gif</i>.
</ul>
<h2>Changes from 1.0.2 to 1.0.3</h2>
<ul>
<li>A bug in Netscape 4.05 and earlier versions prevented data-driven
selector interactors from working properly. Since that bug is fixed in
Netscape 4.06, the Java Explorer applets attempt to distinguish
between 4.06 and other versions in handling these interactors at
run time. If Java Explorer mistakenly identifies a pre-4.06 browser
as a 4.06 browser, then the Java Explorer applet will crash when
it handles an option-menu style data-driven selector interactor
message. There will be a corresponding message in the browser's
Java Console.
<li>The <a href=Status.htm#configuration>distributed execution</a>
mechanism did not work using the SGI version of DXServer
due to a syntax error in the remote shell script used to spawn
dx sessions. The DXServers for the other platforms experienced
protocol errors due to dropped data packets.
<li>Java Explorer obeys the Image tool's interaction mode input
parameter. You may include an interactor in your visualization
to control the parameter. If the input is tab down then Java
Explorer may overwrite it. Java Explorer will obey the value of
the input if the value is one of "none", "rotate", "pick", "panzoom",
or "zoom". If the value is "panzoom", then Java Explorer will enter
its pan mode.
<li>Java Explorer's Image and Pick menus in the <i>Execution</i> panel
will be included in the user interface if there are 2 or more image
or pick tools respectively. Previously these menus were included if
there was 1 image tool or pick tool.
<li>Java Explorer will honor the image tool's interactionmode input
parameter value saved in a .net file. In other words if you save
a visual program with the Image tool in <i>Pick</i> or <i>Rotate</i>
mode, then Java Explorer will be in <i>Pick</i> or <i>Rotate</i>
mode (respectively) when the browser hits the web page resulting
from that net.
<li>A bug in DXServer in 1.0.2 and earlier versions in which
the DXServer entered an infinite loop if dxexec crashed is now fixed.
<li>Java Explorer now uses Netscape's Document Object Model for
locating image window destinations within the web page only for
vrml output and not for image output.
</ul>
<h2>Changes from 1.0.0 to 1.0.2</h2>
<ul>
<li>All .class files required by Java Explorer are now in one
jar file. As a result the time taken by a browser to load
Java Explorer's classes over the internet should be reasonable.
<li>Support for Data Explorer's sequencer is now included.
If your visual program contains multiple images tools, 2 or more of
which should sequence together, then set the <b>groupName</b> input of
their associated <b>WebOptions</b> tools to a common string.
The Java Explorer sequencer works differently from the Data Explorer
sequencer in that it cycles the Data Explorer sequencer through one
time, then replays images from a local cache for good performance.
The Data Explorer sequencer does not replay images from an image cache.
Instead it actually reexecutes the net with every step, relying on
data caching in the executive for good performance. The differences
which would be obvious to an end user are:
<ol>
<li>When the Java Explorer sequencer has finished one cycle the
green execution light goes off, unlike in Data Explorer.
</ol>If an interactor value is changed while Java Explorer is replaying
images from its cache, the change will not be reflected in the image unless
the user selects <i>Sequence</i> in the <i>Mode</i> menu again.
<li>Camera interaction modes now operate in the coordinate space of the viewer.
<li>Camera interaction modes allow you to stroke in the image with the mouse.
<li>DXLExitDX now successfully terminates dxexec in the pc version of DXServer.
<li>The input types to WebOptions have changed. In the previous release,
the inputs were all of type "value list or string list or object". Now the
mdf information for WebOptions contains appropriate types for all the inputs.
As a result you may get warning messages from dxui when loading an older
net saved with a WebOptions. If you do get such a warning, then you
must check the values entered in the configuration dialog for WebOptions.
It's likely that one or more values were lost.
<li>Some interfaces used in the java code generated by dxui have changed.
In order to use nets saved with the previous version of Java Explorer with
this version, you must do the following:
<ol>
<li>Remove or hide the old version of WebOptions (found in weboptionsmac.net).
<li>Add the new version found in <i>installDir</i>/java/server/dxmacros
to your DXMACROS.
<li>Load and visual program then save it using 'File/Save'.
<li>Save a new java file using 'Edit/Java/Net To Applet'.
</ol>
<li>Dxui used to write the files comprising a web page into its
current working directory. Now it writes them into the same directory
as the .net file.
<li>So that you aren't required to hand edit the
makefile generated by 'Edit/Java/Save As Web Page' you may make settings
for the following in $HOME/DX:
<ul>
<li><b>DX*cosmoDir: /some/where/vrml</b>
<blockquote>
<small>A value is required for cosmoDir only if you're generating
web pages which use vrml. The files pointed to by cosmoDir are
supplied with the cosmo plug-in.</small>
</blockquote>
<li><b>DX*dxJarFile: <i>installDir</i>/java/htmlpages/dx.jar</b>
<li><b>DX*jdkDir: /usr/jdk_base/lib/classes.zip</b>
<blockquote><small>This location depends on your installation of java.</small>
</blockquote>
<li><b>DX*htmlDir: <i>installDir</i>/java/htmlpages</b>
<li><b>DX*serverDir: <i>installDir</i>/java/server</b>
</ul>
<li>You may produce an <i>Orbit</i> and use it in a web page
without using a connection to DXServer. To do this, simply
follow the instructions for producing a Java Explorer web page. Then
remove the applet tag pointing to <i>myprog.class</i> from the .html file.
<li>A display in <i>orbit</i> mode now gives the user an indication that
an <i>orbit</i> is available by changing the cursor. However, this works
only in Internet Explorer.
</ul>
<p>
|