Fresco/Documentation/src scene-graph.xml,1.4,1.5
Tobias Hunger <[email protected]> Fri, 18 Jul 2003 16:07:52 -0500
| Newsgroups | gmane.comp.video.fresco.cvs |
|---|---|
| Message-ID | <[email protected]> |
Update of /cvs/fresco/Fresco/Documentation/src
In directory purcel:/tmp/cvs-serv15171
Modified Files:
scene-graph.xml
Log Message:
Make sure the line limit of 80 chars is adhered to.
Index: scene-graph.xml
===================================================================
RCS file: /cvs/fresco/Fresco/Documentation/src/scene-graph.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- scene-graph.xml 18 Jul 2003 21:05:16 -0000 1.4
+++ scene-graph.xml 18 Jul 2003 21:07:50 -0000 1.5
@@ -30,7 +30,8 @@
</section>
<section><title>transformational containment</title>
<para>
- <!-- talk about transformational containment -->Since the scene graph is actually
+ <!-- talk about transformational containment -->Since the scene graph
+ is actually
stored in double-precision floating point values, and since any graphic
may be subject to arbitrary linear transformations within the scene, the
parent/child relationship between graphics naturally extends to
@@ -104,10 +105,10 @@
have its true state computed on the fly. This is known as
"externalizing" its state; in fresco we attempt to externalize as much
state from each graphic as possible. Partly this is done to facilitate
- the memory savings mentionned previously, but it also simplifies the task of
- maintaining the proper values for layout and cumulative transformation,
- which are highly dynamic to begin with. Since we compute them on the
- fly, such values are never "out of sync" with one another.
+ the memory savings mentionned previously, but it also simplifies the
+ task of maintaining the proper values for layout and cumulative
+ transformation, which are highly dynamic to begin with. Since we compute
+ them on the fly, such values are never "out of sync" with one another.
</para>
</section>
</section>