| | 12 | </p> |
| | 13 | |
| | 14 | <p> |
| | 15 | 285. |
| | 16 | <b>Document volume and surface programming interfaces</b><br> |
| | 17 | November 12, 2010<br> |
| | 18 | Tom Goddard<br> |
| | 19 | Include documentation in the code of useful volume and surface Python |
| | 20 | and C++ functions and generate documentation from those code comments. |
| | 21 | This would speed up my new development that uses existing code, would |
| | 22 | encourage me to make more thoughtful interfaces to algorithms, and |
| | 23 | substantially encourage outside developers. |
| | 24 | </p> |
| | 25 | |
| | 26 | <p> |
| | 27 | 284. |
| | 28 | <b>Surface rendering in Python</b><br> |
| | 29 | November 12, 2010<br> |
| | 30 | Tom Goddard<br> |
| | 31 | Port surface rendering code from C++ to Python using PyOpenGL. |
| | 32 | Most surface rendering code (excluding transparent rendering) does not |
| | 33 | require C++ for speed. Keep only the speed critical part in C++. |
| | 34 | This would enable easier development of new surface features such as |
| | 35 | clipped outline boxes, or separate inside/outside colors. |
| | 36 | </p> |
| | 37 | |
| | 38 | <p> |
| | 39 | 283. |
| | 40 | <b>Solid volume rendering in Python</b><br> |
| | 41 | November 12, 2010<br> |
| | 42 | Tom Goddard<br> |
| | 43 | Port solid volume rendering code from C++ to Python using PyOpenGL. |
| | 44 | I don't think any part of the existing code requires C++ for speed. |
| | 45 | In Python it would be easier to add new capabilities like clipped |
| | 46 | outline boxes. |
| | 47 | </p> |
| | 48 | |
| | 49 | <p> |
| | 50 | 282. |
| | 51 | <b>Volume slice tool</b><br> |
| | 52 | November 12, 2010<br> |
| | 53 | Tom Goddard<br> |
| | 54 | Allow displaying opaque gray-level volume slices on oblique slices when |
| | 55 | clipping a volume with near/far or per-model clip planes. The 3d volume |
| | 56 | and an clipped outline box of the volume would still be shown to provide |
| | 57 | context. Moving the slice would be done by moving the clip plane. Might |
| | 58 | also allow click and drag on the cut facet. Currently oblique slices can |
| | 59 | be shown with the volume dialog subregion selection panel. That method has |
| | 60 | several difficulties: not able to find it, moving slice is not intuitive, |
| | 61 | context provided by seeing volume behind slice and box outline not provided. |
| | 62 | </p> |
| | 63 | |
| | 64 | <p> |
| | 65 | 281. |
| | 66 | <b>Clipped outline boxes</b><br> |
| | 67 | November 12, 2010<br> |
| | 68 | Tom Goddard<br> |
| | 69 | When a volume surface or solid model outline box is clipped with near/far |
| | 70 | or per-model clip planes show the outline at the clip plane. Currently the |
| | 71 | outline is simply clipped. Showing the outline would provide a good visual |
| | 72 | cue as to where the clipping is done, especially with solid volume rendering. |