diff options
| author | Kevin Rushforth <[email protected]> | 2005-04-01 00:02:28 +0000 |
|---|---|---|
| committer | Kevin Rushforth <[email protected]> | 2005-04-01 00:02:28 +0000 |
| commit | 46cb80a0363025c330baea513b0224fbbdf35de3 (patch) | |
| tree | 2d9ed0768bb271a873266253704733e4e4ded3fb /www/j3d1_4/vsg-op.html | |
| parent | 6a4504426cc054b5e033ba4c2ed31d3ea8c959f4 (diff) | |
Updates to proposed Java 3D API changes
git-svn-id: https://svn.java.net/svn/j3d-core~svn/trunk@183 ba19aa83-45c5-6ac9-afd3-db810772062c
Diffstat (limited to 'www/j3d1_4/vsg-op.html')
| -rw-r--r-- | www/j3d1_4/vsg-op.html | 80 |
1 files changed, 80 insertions, 0 deletions
diff --git a/www/j3d1_4/vsg-op.html b/www/j3d1_4/vsg-op.html new file mode 100644 index 0000000..64db9ad --- /dev/null +++ b/www/j3d1_4/vsg-op.html @@ -0,0 +1,80 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html> +<head> + <meta content="text/html; charset=ISO-8859-1" + http-equiv="content-type"> + <title>Java 3D 1.4: ViewSpecificGroup View Set Operation</title> +</head> +<body> +<h2>Java 3D<sup><font size="-2">TM</font></sup> 1.4: +ViewSpecificGroup View Set Operation<br> +</h2> +<p>This page describes a possible enhancement to Java 3D 1.4 to +allow the application to specify the operation used to compute the set +of views for nested +ViewSpecificGroup (VSG) nodes. Currently, the set of views used to +render descendants of nested VSG nodes is the intersection of the set +of views +inherited from its +parent(s) and the set of views specified in the child VSG node. We +propose to +add an attribute to VSG such that the resulting set of views is either +as the intersection or the union of the set of views inherited from its +parent(s) and the set of views specified in the child VSG node, or +simply the set of views specified in the child VSG node. More formally, +we plan to define three modes as follows: +</p> +<ul> + <table border="0" cellspacing="2" cellpadding="2"> + <tbody> + <tr> + <td><code>INTERSECT</code></td> + <td><code>:</code></td> + <td><code>viewSet[n] += +viewSet[n-1] ∩ VSG[n].viewSet</code></td> + </tr> + <tr> + <td><code>UNION</code></td> + <td><code>:</code></td> + <td><code>viewSet[n] += +viewSet[n-1] ∪ VSG[n].viewSet</code></td> + </tr> + <tr> + <td><code>REPLACE</code></td> + <td><code>:</code></td> + <td><code>viewSet[n] += +VSG[n].viewSet</code> </td> + </tr> + </tbody> + </table> + <br> +where <code>n</code> is the nesting level (the number of ancestor VSG +nodes in the +scene graph path).<br> +The default mode is <code>INTERSECT</code>. +</ul> +<p>Note that the set of views used to render descendants of a top-level +VSG node (that is, a VSG node that is not itself a descendant of +another VSG node) is the set of views specified in the VSG node, +regardless of the mode. More +formally: <code>viewSet[0] = VSG[0].viewSet</code> for all +values of <code>viewSetOp</code>.<br> +</p> +<p>The proposed API is:</p> +<ul> + <li>New methods in existing classes:<br> + </li> + <ul> + <pre>ViewSpecificGroup<br> method: setViewSetOp(int op) // one of: INTERSECT, UNION, REPLACE<br></pre> + </ul> +</ul> +<ol> +</ol> +<p><font color="gray">Page last updated — +$Date$ +</font></p> +</body> +</html> |