[Gzz-commits] gzz/doc Gzz_Memory.rst

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Tuomas J. Lukka <address@hidden>        03/01/07 06:02:05

Modified files:
        doc            : Gzz_Memory.rst 

Log message:
        A little further design

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/doc/Gzz_Memory.rst.diff?tr1=1.3&tr2=1.4&r1=text&r2=text

Patches:
Index: gzz/doc/Gzz_Memory.rst
diff -u gzz/doc/Gzz_Memory.rst:1.3 gzz/doc/Gzz_Memory.rst:1.4
--- gzz/doc/Gzz_Memory.rst:1.3  Tue Jan  7 03:26:12 2003
+++ gzz/doc/Gzz_Memory.rst      Tue Jan  7 06:02:05 2003
@@ -97,7 +97,7 @@
 
 .. UML:: memorycreates
 
-    class RequestHandle "interface"
+    class MemoryConsumer "interface"
        methods 
            getMaxBytes()
            getScaling()
@@ -111,15 +111,15 @@
 
     class ImageLoader
 
-    dep "enqueue, hash" CacheFacade RequestHandle
-    dep "load" ImageLoader RequestHandle
-    dep "create" client RequestHandle
+    dep "enqueue, hash" CacheFacade MemoryConsumer
+    dep "load" ImageLoader MemoryConsumer
+    dep "create" client MemoryConsumer
 
     ---
     horizontally(50, foo, client, CacheFacade, ImageLoader);
-    vertically(100, bar, RequestHandle, foo);
+    vertically(100, bar, MemoryConsumer, foo);
 
-The class ``RequestHandle`` abstracts a single memoryconsumer, where the
+The class ``MemoryConsumer`` abstracts a single memoryconsumer, where the
 system may query it for the maximum number of bytes needed, the way the
 number of bytes can be scaled, and set the current memory consumption
 to a particular amount.
@@ -137,11 +137,23 @@
        methods
            TexRect get(PageSpan p, float importance, Obs o)
 
-    class TexRect
+    pagequal = qual
+       fields
+           SinglePageSpan sp
 
-    class TextureImageRequest
+    assoc pagequal multi(1) - multi(0..1) TextureImageMemoryConsumer
+
+    class MemoryConsumer
+
+    class TextureImageMemoryConsumer
+       inherit MemoryConsumer
 
     ---
+    vertically(60, aaa, MemoryConsumer, TextureImageMemoryConsumer);
+
+    pagequal.w = GLSpans.e;
+    horizontally(60, bbb, pagequal, TextureImageMemoryConsumer);
+
 
 Defining the importance function is not simple; this represents 
 the tradeoffs between memory use for the focus and context.
@@ -151,7 +163,7 @@
 visible but might become visible when the user moves; these should
 only be loaded if there's extra memory available.
 
-
+The cases between the two extremes are the difficult ones.