gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] gzz/doc/gl Mipzip.rst


From: Tuomas J. Lukka
Subject: [Gzz-commits] gzz/doc/gl Mipzip.rst
Date: Sat, 18 Jan 2003 14:14:16 -0500

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Tuomas J. Lukka <address@hidden>        03/01/18 14:14:16

Modified files:
        doc/gl         : Mipzip.rst 

Log message:
        twid

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/doc/gl/Mipzip.rst.diff?tr1=1.6&tr2=1.7&r1=text&r2=text

Patches:
Index: gzz/doc/gl/Mipzip.rst
diff -u gzz/doc/gl/Mipzip.rst:1.6 gzz/doc/gl/Mipzip.rst:1.7
--- gzz/doc/gl/Mipzip.rst:1.6   Sat Jan 18 11:39:44 2003
+++ gzz/doc/gl/Mipzip.rst       Sat Jan 18 14:14:16 2003
@@ -34,10 +34,6 @@
     horizontally(80, foo, FormatData, LevelData);
     vertically(80, bar, MipzipFile, foo);
 
-Due to the requirements of memory handling and GL threads,
-we need to separate loading the mipmap level and teximaging
-it.
-
 The following classes collaborate to provide Mipzip
 functionality. First of all, MipzipLoader has a nested
 class, Level, for representing a mipmap level, and
@@ -61,6 +57,7 @@
     class MipzipLoader.Level
        jlink
        fields
+           enum state
            int levelNo
            Dimension size
            byte[] loadedData
@@ -103,6 +100,7 @@
            ...
 
     class gzz.mem.MemoryPartitioner
+       jlink
        use gzz.mem.MemoryConsumer
 
     class MipzipMemoryConsumer
@@ -123,5 +121,14 @@
 
     horizontally(80, naz, gzz.mem.MemoryConsumer,
                gzz.mem.MemoryPartitioner);
+
+The process of loading a single mipzip level is
+rather intricate.
+Due to the requirements of memory handling and GL threads,
+we need to separate loading the mipmap level and teximaging
+it to different threads.
+
+
+
 
 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]