aboutsummaryrefslogtreecommitdiffstats
path: root/www/j3d1_4/proposed-changes.html
diff options
context:
space:
mode:
Diffstat (limited to 'www/j3d1_4/proposed-changes.html')
-rw-r--r--www/j3d1_4/proposed-changes.html257
1 files changed, 147 insertions, 110 deletions
diff --git a/www/j3d1_4/proposed-changes.html b/www/j3d1_4/proposed-changes.html
index 04dede8..d0e57bb 100644
--- a/www/j3d1_4/proposed-changes.html
+++ b/www/j3d1_4/proposed-changes.html
@@ -3,13 +3,14 @@
<head>
<meta http-equiv="content-type"
content="text/html; charset=ISO-8859-1">
- <title>Proposed Java 3D 1.4 API Changes</title>
+ <title>Proposed Java 3D API Changes</title>
</head>
<body>
-<h2>Proposed Java&nbsp;3D<sup><font size="-2">TM</font></sup> 1.4 API
+<h2>Proposed Java&nbsp;3D<sup><font size="-2">TM</font></sup> API
Changes</h2>
<p>This page highlights the proposed changes to the 1.4 version of the
-Java&nbsp;3D<sup><font size="-2">TM</font></sup> API. For a list of new
+Java&nbsp;3D<sup><font size="-2">TM</font></sup> API, and beyond. For a
+list of new
classes methods, etc., see the <a href="api-changes.html">List of
Proposed Java&nbsp;3D 1.4 API
Changes</a>. Click
@@ -20,101 +21,114 @@ javadocs for the proposed 1.4 API</a> (built from the dev-1_4 branch).
A list of other <a href="improvements.html">possible improvements to
Java&nbsp;3D version 1.4</a> is also available.
</p>
-<h3>I. High Priority Features</h3>
-<p>This list of high priority features will almost certainly make it
-into the 1.4 API.
-</p>
-<h4>1. Proposed API to be added</h4>
-<p>This is a list of features that we propose to add to
-the API.<br>
-</p>
-<ul>
- <li><a href="shaders.html">Programmable
+<table style="text-align: left; width: 100%;" border="0" cellspacing="4"
+ cellpadding="4">
+ <tbody>
+ <tr>
+ <td
+ style="text-align: left; vertical-align: top; background-color: rgb(255, 255, 225); width: 60%;">
+ <h3>1.4 Committed Features<br>
+ </h3>
+ <p>This list of high priority features will almost certainly make
+it
+into the 1.4 version of the Java&nbsp;3D API.</p>
+ <ul>
+ <li><a
+ href="file:///home/kcr/java3d/1.3.3/j3d-core/www/j3d1_4/shaders.html">Programmable
Shaders</a></li>
- <li><a href="graph-change-listener.html">Scene graph structure change
+ <li><a
+ href="file:///home/kcr/java3d/1.3.3/j3d-core/www/j3d1_4/graph-change-listener.html">Scene
+graph structure change
listeners</a></li>
- <li><a
+ <li><a
href="http://javadesktop.org/java3d/javadoc/1.4.0-latest/javax/media/j3d/SceneGraphObject.html#setName%28java.lang.String%29">Name
string</a> for all scene graph objects: add public <a
href="http://javadesktop.org/java3d/javadoc/1.4.0-latest/javax/media/j3d/SceneGraphObject.html#setName%28java.lang.String%29"><code>get/setName(String)</code></a>
to <code>SceneGraphObject</code>
class</li>
- <li>New <a
+ <li>New <a
href="http://javadesktop.org/java3d/javadoc/1.4.0-latest/javax/media/j3d/Node.html#ALLOW_PARENT_READ"><code>ALLOW_PARENT_READ</code></a>
capability bit in <code>Node</code>
class that will allow <a
href="http://javadesktop.org/java3d/javadoc/1.4.0-latest/javax/media/j3d/Node.html#getParent%28%29"><code>getParent()</code></a>
to be called on live/compiled scene graph</li>
- <li>Ability to get the locale from a live node: add public <code>getLocale()</code>
+ <li>Ability to get the locale from a live node: add public <code>getLocale()</code>
method and <code>ALLOW_LOCALE_READ</code> capability bit to <code>Node</code>
class<br>
- </li>
- <li>Additional blending functions, for example: <code>BLEND_SRC_COLOR</code>,
- <code>BLEND_ONE_MINUS_SRC_COLOR</code>, <code>BLEND_DST_COLOR</code>,
- <code>BLEND_ONE_MINUS_DST_COLOR</code>, etc.</li>
- <li><a href="picking.html">Additional core picking methods</a> (in
+ </li>
+ <li>Additional blending functions, for example: <code>BLEND_SRC_COLOR</code>,
+ <code>BLEND_ONE_MINUS_SRC_COLOR</code>, <code>BLEND_DST_COLOR</code>,
+ <code>BLEND_ONE_MINUS_DST_COLOR</code>, etc.</li>
+ <li><a
+ href="file:///home/kcr/java3d/1.3.3/j3d-core/www/j3d1_4/picking.html">Additional
+core picking methods</a> (in
Locale and BranchGroup)</li>
- <li><a href="stencil.html">Stencil buffer</a><br>
- </li>
-</ul>
-<h4>2. Proposed API to be deprecated</h4>
-<p>This is a list of features that we propose to
-deprecate in
+ <li><a
+ href="file:///home/kcr/java3d/1.3.3/j3d-core/www/j3d1_4/stencil.html">Stencil
+buffer</a><br>
+ </li>
+ </ul>
+ <p>This is a list of features that we propose to <a
+ href="#Footnote_1">deprecate<sup>1</sup></a> in
the API.<br>
-</p>
-<ul>
- <li><code>CompressedGeometry</code> (no HW support, lack of industry
+ </p>
+ <ul>
+ <li><code>CompressedGeometry</code> class (no HW support, lack
+of
+industry
acceptance)</li>
- <li><code>Sensor</code> prediction (has never been implemented)<br>
- </li>
- <li><code>PickPoint</code> (not fully implemented, cannot be used for
+ <li>Sensor prediction (has never been implemented)<br>
+ </li>
+ <li><code>PickPoint</code> class (not fully implemented, cannot
+be
+used for
geometry-based picking; use PickBounds with
a
BoundingSphere that has a small radius)</li>
-</ul>
-<p>Note that none of these features will actually be removed. It
-instead
-reflects a decrease of emphasis on these features. While they should
-continue
-to function normally, no additional effort is likely to be put into
-them (for example, compressed geometry will not be supported with
-programmable shaders). This action paves the way to remove them from a
-future major release (e.g., a 2.0 release).<br>
-</p>
-<h3>II. Medium Priority Features</h3>
-<p>This list of medium priority features is under discussion for
+ <li><code></code><code>Morph</code> node (expensive, picking
+doesn't
+work,
+can be done
+in a utility)</li>
+ </ul>
+ </td>
+ <td
+ style="text-align: left; vertical-align: top; background-color: rgb(235, 255, 235);"
+ colspan="1" rowspan="4">
+ <h3>Other Features for 1.4, 1.5, ...<br>
+ </h3>
+ <p>This list of medium priority features is under discussion for
possible inclusion
-into the 1.4 API.
-</p>
-<h4>1. Possible API to be added</h4>
-<p>This is a list of features that are being considered
-for addition to
-the API.<br>
-</p>
-<ul>
- <li><a href="render-texture.html">Render to texture</a></li>
- <li>Non-power-of-two textures</li>
- <li>Point sprites</li>
- <li>Ability for nested ViewSpecificGroup nodes to replace the set of
-views in addition to
-current intersection semantics</li>
- <li>API support for&nbsp; retained alpha buffers</li>
- <li>Ability to query properties from a <code>GraphicsConfiguration</code></li>
- <li>Better support for off-screen configuration parameters (e.g., an
+into the 1.4 or 1.5 API (or beyond). </p>
+ <ul>
+ <li>Non-power-of-two textures</li>
+ <li>Point sprites</li>
+ <li><a
+ href="file:///home/kcr/java3d/1.3.3/j3d-core/www/j3d1_4/vsg-op.html">Ability
+for nested ViewSpecificGroup nodes
+to replace the set of views</a><br>
+ </li>
+ <li>API support for&nbsp; retained alpha buffers</li>
+ <li>Ability to query properties from a <code>GraphicsConfiguration</code></li>
+ <li>Better support for off-screen configuration parameters
+(e.g., an
attribute in <code>GraphicsConfigTemplate3D</code> indicating whether
the requested <code>GraphicsConfiguration</code> is used for on-screen
rendering,
off-screen rendering, or both)</li>
- <li>Enhance <code>getLocalToVWorld()</code> to return a valid result
+ <li>Enhance <code>getLocalToVWorld()</code> to return a valid
+result
for non-live graphs.</li>
- <li><a href="lightweight-canvas3d.html">Lightweight Canvas3D (e.g.,
+ <li><a
+ href="file:///home/kcr/java3d/1.3.3/j3d-core/www/j3d1_4/lightweight-canvas3d.html">Lightweight
+Canvas3D (e.g.,
JCanvas3D)</a>. <span style="color: rgb(204, 0, 0);">Note: this
feature
will not
happen
without an someone from the community volunteering
to drive it.</span></li>
- <li>Add a new attribute for depth test function to
+ <li>Add a new attribute for depth test function to
RenderingAttributes: public <code>get/setDepthTestFunction(int&nbsp;function)</code>
methods that takes as values one of: <code>ALWAYS, NEVER,
EQUAL, NOT_EQUAL, LESS, LESS_OR_EQUAL, GREATER, GREATER_OR_EQUAL</code>.
@@ -124,7 +138,8 @@ will not
happen
without an someone from the community volunteering
to drive it.</span></li>
- <li>Method to retrieve the geometry data from the tessellation of a
+ <li>Method to retrieve the geometry data from the tessellation
+of a
glyph in a 3D font: a
public <code>GeometryArray&nbsp;getGlyphGeometry(</code><code>int&nbsp;glyphCode</code><code>)</code>
method in the <code>Font3D</code> class. <span
@@ -132,49 +147,71 @@ method in the <code>Font3D</code> class. <span
happen
without an someone from the community volunteering
to drive it.</span><span style="color: rgb(204, 0, 0);"></span></li>
-</ul>
-<h4>2. Possible API to be deprecated</h4>
-<p>This is a list of features that are being considered
-for deprecation in
-the API.<br>
-</p>
-<ul>
- <li><code></code><code>Morph</code> (expensive, picking doesn't work,
-can be done
-in a utility)</li>
-</ul>
-<p>These are in addition to the API being proposed for deprecation in
-section I.
-</p>
-<h3><a name="Future_Features"></a>III. Future Features</h3>
-<p>Here is an unprioritized list of possible features under
-consideration for a future (e.g., 1.5/2.0)
-version of the Java&nbsp;3D API.
-</p>
-<ul>
- <li>Multipass rendering</li>
- <li>Shadow map support</li>
- <li>Additional texture formats:
- <ul>
- <li>NIO buffer support</li>
- <li>Texture compression formats</li>
- </ul>
- </li>
- <li>Extensibility:
- <ul>
- <li>Access to the native context (JOGL integration)</li>
- <li>Geometry extensibility</li>
- <li>Additional node types (e.g., haptic rendering)</li>
- <li>Extensible geometry processing algorithms</li>
- </ul>
- </li>
- <li>Plug-in capability
- <ul>
- <li>Rendering Device Interface (pluggable renderers)</li>
- <li>Visibility structure</li>
- </ul>
- </li>
-</ul>
+ <li>Additional texture formats:
+ <ul>
+ <li>NIO buffer support</li>
+ <li>Texture compression formats</li>
+ </ul>
+ </li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td
+ style="text-align: left; vertical-align: top; background-color: rgb(255, 255, 203); width: 60%;">
+ <h3>1.5 Proposed Major Features</h3>
+ <p>This list of high priority features is being seriously
+considered for the 1.5 version of the Java&nbsp;3D API.</p>
+ <ul>
+ <li><a href="render-texture.html">Render to texture</a></li>
+ <li><a href="multipass.html">Multipass rendering</a></li>
+ <li>Shadow map support</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td
+ style="text-align: left; vertical-align: top; background-color: rgb(255, 255, 182); width: 60%;">
+ <h3>1.6 Possible Major Features</h3>
+ <p><span style="font-style: italic;">Not yet planned</span><br>
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td
+ style="text-align: left; vertical-align: top; background-color: rgb(255, 255, 164); width: 60%;">
+ <h3><a name="Future_Features"></a>2.0 Possible Major Features</h3>
+ <p>Here is an unprioritized list of possible features under
+consideration for a future 2.0 version of the Java&nbsp;3D API. </p>
+ <ul>
+ <li>Extensibility:
+ <ul>
+ <li>Access to the native context (JOGL integration)</li>
+ <li>Geometry extensibility</li>
+ <li>Additional node types (e.g., haptic rendering)</li>
+ <li>Extensible geometry processing algorithms</li>
+ </ul>
+ </li>
+ <li>Plug-in capability
+ <ul>
+ <li>Rendering Device Interface (pluggable renderers)</li>
+ <li>Visibility structure</li>
+ </ul>
+ </li>
+ </ul>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<p><small><a name="Footnote_1"></a>1 &#8211; Note that deprecated
+features will not actually be removed. It
+instead
+reflects a decrease of emphasis on these features. While they should
+continue
+to function normally, no additional effort is likely to be put into
+them (for example, compressed geometry will not be supported with
+programmable shaders). This action paves the way to remove them from a
+future major release (e.g., a 2.0 release).</small></p>
<p><font color="gray">Page last updated &#8212;
$Date$
</font></p>