| 1 |
<h2>DESCRIPTION</h2> |
| 2 |
|
| 3 |
<em>g.pnmcomp</em> isn't meant for end users. It's an internal tool |
| 4 |
for use by <em><a href="wxGUI.html">wxGUI</a></em>. |
| 5 |
|
| 6 |
<p> |
| 7 |
In essence, <em>g.pnmcomp</em> generates a PPM image by overlaying a |
| 8 |
series of PPM/PGM pairs (PPM = RGB image, PGM = alpha channel). |
| 9 |
|
| 10 |
<h2>NOTES</h2> |
| 11 |
|
| 12 |
The intention is that <em>d.*</em> modules will emit PPM/PGM pairs (by |
| 13 |
way of the PNG-driver code being integrated into Display Library). The |
| 14 |
GUI will manage a set of layers; each layer consists of the data |
| 15 |
necessary to generate a PPM/PGM pair. |
| 16 |
|
| 17 |
Whenever the layer "stack" changes (by adding, removing, |
| 18 |
hiding, showing or re-ordering layers), the GUI will render any layers |
| 19 |
for which it doesn't already have the PPM/PGM pair, then re-run |
| 20 |
<em>g.pnmcomp</em> to generate the final image (just redoing the |
| 21 |
composition is a lot faster than redrawing everything). |
| 22 |
|
| 23 |
<p> |
| 24 |
A C/C++ GUI would either have <em>g.pnmcomp's</em> functionality |
| 25 |
(image composition) built-in, or would use the system's graphics API |
| 26 |
to perform composition (for translucent layers, you would need OpenGL |
| 27 |
or the Render extension, or something else which supports translucent |
| 28 |
rendering). |
| 29 |
|
| 30 |
<p> |
| 31 |
Tk doesn't support transparent (masked) true-colour images (it does |
| 32 |
support transparent GIFs, but that's limited to 256 colours), and an |
| 33 |
image composition routine in Tcl would be unacceptably slow, hence |
| 34 |
the existence of <em>g.pnmcomp</em>. |
| 35 |
|
| 36 |
<h2>SEE ALSO</h2> |
| 37 |
|
| 38 |
<em> |
| 39 |
<a href="g.cairocomp.html">g.cairocomp</a> |
| 40 |
</em> |
| 41 |
|
| 42 |
<h2>AUTHOR</h2> |
| 43 |
|
| 44 |
Glynn Clements |