Fresco/Documentation/src book.xml,1.8,1.9 control-graph.xml,1.6,1.7 hello.xml,1.14,1.15 kits.xml,1.7,1.8
Stefan Seefeld <[email protected]>
| Newsgroups | gmane.comp.video.fresco.cvs |
|---|---|
| Message-ID | <[email protected]> |
Update of /cvs/fresco/Fresco/Documentation/src
In directory purcel:/tmp/cvs-serv10841
Modified Files:
book.xml control-graph.xml hello.xml kits.xml
Log Message:
prefer svg imagedata over png, if ever possible
Index: book.xml
===================================================================
RCS file: /cvs/fresco/Fresco/Documentation/src/book.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- book.xml 21 Jan 2003 07:45:32 -0000 1.8
+++ book.xml 23 Mar 2003 19:19:43 -0000 1.9
@@ -1,5 +1,5 @@
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.0//EN"
- "http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd"[
+ "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"[
<!-- these are chapter-entity declarations -->
Index: control-graph.xml
===================================================================
RCS file: /cvs/fresco/Fresco/Documentation/src/control-graph.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- control-graph.xml 28 Jan 2003 18:44:34 -0000 1.6
+++ control-graph.xml 23 Mar 2003 19:19:43 -0000 1.7
@@ -207,26 +207,26 @@
represents a "trail" or "path" to the currently traversed graphic.
We need to create a "snapshot" of this trail at the hit graphic. This is done by calling
<emphasis>hit</emphasis> on the PickTraversal, resulting in a memento being created.
- <figure id="scene-figure" float="1">
+ <figure id="scene-figure">
<title>scene</title>
<mediaobject>
<imageobject>
+ <imagedata fileref="figures/scene.svg" align="center" format="SVG"/>
+ </imageobject>
+ <imageobject>
<imagedata fileref="figures/scene.png" align="center" format="PNG"/>
</imageobject>
-<!-- <imageobject> -->
-<!-- <imagedata fileref="figures/scene.pdf" align="center" format="PDF"/> -->
-<!-- </imageobject> -->
</mediaobject>
</figure>
- <figure id="scene-graph-figure" float="1">
+ <figure id="scene-graph-figure">
<title>scene graph corresponding to the snapshot in ...</title>
<mediaobject>
<imageobject>
+ <imagedata fileref="figures/scene-graph.svg" align="center" format="SVG"/>
+ </imageobject>
+ <imageobject>
<imagedata fileref="figures/scene-graph.png" align="center" format="PNG"/>
</imageobject>
-<!-- <imageobject> -->
-<!-- <imagedata fileref="figures/scene-graph.pdf" align="center" format="PDF"/> -->
-<!-- </imageobject> -->
</mediaobject>
</figure>
Imagine the mouse to click on the red polygon. This will result in
@@ -242,15 +242,15 @@
</programlisting>
The <classname> Traversal</classname>'s trail, in the moment the <emphasis>hit</emphasis> occurs,
contains the following entries:
- <figure id="trail-figure" float="1">
+ <figure id="trail-figure">
<title>trail</title>
<mediaobject>
<imageobject>
+ <imagedata fileref="figures/trail.svg" align="center" format="SVG"/>
+ </imageobject>
+ <imageobject>
<imagedata fileref="figures/trail.png" align="center" format="PNG"/>
</imageobject>
-<!-- <imageobject> -->
-<!-- <imagedata fileref="figures/trail.pdf" align="center" format="PDF"/> -->
-<!-- </imageobject> -->
</mediaobject>
</figure>
For each position, the trail contains the following information:
@@ -280,15 +280,15 @@
Since after the traversal is over, the stack will be empty, the <classname>Picktraversal</classname>
needs to create a memento of itself, which can be used later on to deliver the event.
The controller stack, extracted out of the trail, is
- <figure id="cstack-figure" float="1">
+ <figure id="cstack-figure">
<title>controller/focus stack</title>
<mediaobject>
<imageobject>
+ <imagedata fileref="figures/cstack.svg" align="center" format="SVG"/>
+ </imageobject>
+ <imageobject>
<imagedata fileref="figures/cstack.png" align="center" format="PNG"/>
</imageobject>
-<!-- <imageobject> -->
-<!-- <imagedata fileref="figures/cstack.pdf" align="center" format="PDF"/> -->
-<!-- </imageobject> -->
</mediaobject>
</figure>
It is used to update the focus, i.e. to call (in appropriate order) all the controllers'
@@ -306,15 +306,15 @@
</programlisting>
Finally, if all filters let the event through, the Editor's handle method will be called. It sees
the trail like
- <figure id="gstack-figure" float="1">
+ <figure id="gstack-figure">
<title>trail, the unaccessible graphics are grayed out</title>
<mediaobject>
<imageobject>
+ <imagedata fileref="figures/gstack.svg" align="center" format="SVG"/>
+ </imageobject>
+ <imageobject>
<imagedata fileref="figures/gstack.png" align="center" format="PNG"/>
</imageobject>
-<!-- <imageobject> -->
-<!-- <imagedata fileref="figures/gstack.pdf" align="center" format="PDF"/> -->
-<!-- </imageobject> -->
</mediaobject>
</figure>
A special iterator allows it to access the graphics which, inside the editor, were intersecting
@@ -324,15 +324,15 @@
<section><title>navigating non positional devices</title>
<para>
<!-- talk about focus navigation -->
- <figure id="control-graph-figure" float="1">
+ <figure id="control-graph-figure">
<title>control graph</title>
<mediaobject>
<imageobject>
+ <imagedata fileref="figures/control-graph.svg" align="center" format="SVG"/>
+ </imageobject>
+ <imageobject>
<imagedata fileref="figures/control-graph.png" align="center" format="PNG"/>
</imageobject>
-<!-- <imageobject> -->
-<!-- <imagedata fileref="figures/control-graph.pdf" align="center" format="PDF"/> -->
-<!-- </imageobject> -->
</mediaobject>
</figure>
You can navigate the focus through this control graph via the following
@@ -355,15 +355,15 @@
<section><title>sumary</title>
<para>
<!-- event dispatching sumary -->
- <figure id="event-dispatching-figure" float="1">
+ <figure id="event-dispatching-figure">
<title>event and focus management</title>
<mediaobject>
<imageobject>
+ <imagedata fileref="figures/events.svg" align="center" format="SVG"/>
+ </imageobject>
+ <imageobject>
<imagedata fileref="figures/events.png" align="center" format="PNG"/>
</imageobject>
-<!-- <imageobject> -->
-<!-- <imagedata fileref="figures/events.pdf" align="center" format="PDF"/> -->
-<!-- </imageobject> -->
</mediaobject>
</figure>
</para>
Index: hello.xml
===================================================================
RCS file: /cvs/fresco/Fresco/Documentation/src/hello.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -d -r1.14 -r1.15
--- hello.xml 28 Jan 2003 18:44:34 -0000 1.14
+++ hello.xml 23 Mar 2003 19:19:43 -0000 1.15
@@ -10,15 +10,15 @@
is a separate process, whos address is configured into the CORBA runtime environment of all programs, such
that you can look it up as an 'initial reference'. The name server returns an 'Interoperable Object Reference'
(IOR), which the client uses for direct requests.
- <figure id="fig.resolve" float="1">
+ <figure id="fig.resolve">
<title>a client contacts the server via the naming service</title>
<mediaobject>
<imageobject>
+ <imagedata fileref="figures/resolve.svg" align="center" format="SVG"/>
+ </imageobject>
+ <imageobject>
<imagedata fileref="figures/resolve.png" align="center" format="PNG"/>
</imageobject>
-<!-- <imageobject> -->
-<!-- <imagedata fileref="figures/resolve.pdf" align="center" format="PDF"/> -->
-<!-- </imageobject> -->
</mediaobject>
</figure>
Here is the relevant code in python:
Index: kits.xml
===================================================================
RCS file: /cvs/fresco/Fresco/Documentation/src/kits.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- kits.xml 28 Jan 2003 18:44:34 -0000 1.7
+++ kits.xml 23 Mar 2003 19:19:43 -0000 1.8
@@ -12,26 +12,23 @@
<para>Berlin's principal paradigm is composition. All complex objects are compositions out of
small, leightweight building blocks, each from a specific domain, such as 'text', 'layout',
'figure'. Let's have a look at a simple button widget.</para>
- <figure id="fig.about-button" float="1">
+ <figure id="fig.about-button">
<title>A button...</title>
<mediaobject>
<imageobject>
<imagedata fileref="figures/about-button.png" align="center" format="PNG"/>
</imageobject>
-<!-- <imageobject> -->
-<!-- <imagedata fileref="figures/about-button.pdf" align="center" format="PDF"/> -->
-<!-- </imageobject> -->
</mediaobject>
</figure>
- <figure id="fig.about-button-sg" float="1">
+ <figure id="fig.about-button-sg">
<title>...and its underlaying scene graph</title>
<mediaobject>
<imageobject>
+ <imagedata fileref="figures/about-button-sg.svg" align="center" format="SVG"/>
+ </imageobject>
+ <imageobject>
<imagedata fileref="figures/about-button-sg.png" align="center" format="PNG"/>
</imageobject>
-<!-- <imageobject> -->
-<!-- <imagedata fileref="figures/about-button-sg.pdf" align="center" format="PDF"/> -->
-<!-- </imageobject> -->
</mediaobject>
</figure>
<para>As simple as this button looks, it is already an amazing composition of smaller parts coming
@@ -57,15 +54,15 @@
various styles through the use of exchangable implementations.</para>
<para>Clients don't instantiate objects by themselfs. Instead, they ask factory objects to create objects
for them.</para>
- <figure id="fig.abstract-factory" float="1">
+ <figure id="fig.abstract-factory">
<title>the abstract factory pattern</title>
<mediaobject>
<imageobject>
+ <imagedata fileref="figures/abstract-factory.svg" align="center" format="SVG"/>
+ </imageobject>
+ <imageobject>
<imagedata fileref="figures/abstract-factory.png" align="center" format="PNG"/>
</imageobject>
-<!-- <imageobject> -->
-<!-- <imagedata fileref="figures/abstract-factory.pdf" align="center" format="PDF"/> -->
-<!-- </imageobject> -->
</mediaobject>
</figure>
<para>The exact type of the returned object isn't known, which means that the server has more freedom to choose
@@ -110,16 +107,16 @@
<para> On the server side, all this is provided by means of the prototype pattern. On startup, one object per type is loaded into a lookup
table (no worries, kits are almost stateless, so this isn't as expensive as it sounds), such that the lookup can be implemented by means of
CORBA's own type system (objects have an '_is_a(in string repoId)' method). If an appropriate object was found, it is simply cloned and the
- new copy is assigned to the client's ServerContext.</para>
- <figure id="fig.prototype" float="1">
+ new copy is assigned to the client's ServerContext. blablabla</para>
+ <figure id="fig.prototype">
<title>the prototype pattern</title>
<mediaobject>
<imageobject>
+ <imagedata fileref="figures/prototype.svg" align="center" format="SVG"/>
+ </imageobject>
+ <imageobject>
<imagedata fileref="figures/prototype.png" align="center" format="PNG"/>
</imageobject>
-<!-- <imageobject> -->
-<!-- <imagedata fileref="figures/prototype.pdf" align="center" format="PDF"/> -->
-<!-- </imageobject> -->
</mediaobject>
</figure>
<para> the full sequence of events thus looks like this:</para>