gzz-commits
[Top][All Lists]
Advanced

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

[Gzz-commits] gzz ./TODO doc/pegboard/pegboard.html doc/pegbo...


From: Tuomas J. Lukka
Subject: [Gzz-commits] gzz ./TODO doc/pegboard/pegboard.html doc/pegbo...
Date: Mon, 28 Oct 2002 03:50:38 -0500

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Tuomas J. Lukka <address@hidden>        02/10/28 03:50:38

Modified files:
        .              : TODO 
        doc/pegboard   : pegboard.html 
        doc/pegboard/1021: click.rst 

Log message:
        Update mouse click peg, make it current.

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/TODO.diff?tr1=1.327&tr2=1.328&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/doc/pegboard/pegboard.html.diff?tr1=1.36&tr2=1.37&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/doc/pegboard/1021/click.rst.diff?tr1=1.1&tr2=1.2&r1=text&r2=text

Patches:
Index: gzz/TODO
diff -u gzz/TODO:1.327 gzz/TODO:1.328
--- gzz/TODO:1.327      Mon Oct 28 03:37:27 2002
+++ gzz/TODO    Mon Oct 28 03:50:37 2002
@@ -42,6 +42,9 @@
                - report on #gzz
                - run tests (and report if introduces failures)
                - build docs in himalia
+       - make sure "make pegs" works right - currently libraries
+         don't load properly by C-python (need to put stuff in depends.
+         Make sure a plain 2.1 installation works.)
        + see (with ibid and buildbot) how we could run all tests nightly
          on 
            - pure software Mesa
@@ -249,14 +252,11 @@
        - python tests easily runnable one by one
        + remove Media*Stream and other span serialization functionality
           (PEG 1004)
-       + make sure "make pegs" works right - currently libraries
-         don't load properly by C-python (need to put stuff in depends.
-         Make sure a plain 2.1 installation works.)
-           - think about autogenerating the pegboard page from
-             a .rst file and the .rst files of the pegs - currently
-             we need to change several locations.
-             Note the colors in the table: they're very useful (depends
-             only on status).
+       - think about autogenerating the pegboard page from
+         a .rst file and the .rst files of the pegs - currently
+         we need to change several locations.
+         Note the colors in the table: they're very useful (depends
+         only on status).
         + the containment mechanism
             + Ted's bindings for it
     tuukkah:
Index: gzz/doc/pegboard/1021/click.rst
diff -u gzz/doc/pegboard/1021/click.rst:1.1 gzz/doc/pegboard/1021/click.rst:1.2
--- gzz/doc/pegboard/1021/click.rst:1.1 Fri Oct 25 04:17:06 2002
+++ gzz/doc/pegboard/1021/click.rst     Mon Oct 28 03:50:38 2002
@@ -1,10 +1,10 @@
 =============================================================
-PEG XXX: Mouse clicks and VobScene
+PEG 1021: Mouse clicks and VobScene
 =============================================================
 
 :Author:   Tuomas J. Lukka
-:Date:     $Date: 2002/10/25 08:17:06 $
-:Revision: $Revision: 1.1 $
+:Date:     $Date: 2002/10/28 08:50:38 $
+:Revision: $Revision: 1.2 $
 :Status:   Incomplete
 
 The VobScene API contains the method ::
@@ -24,6 +24,10 @@
 
 - Who stores the knowledge of which coordinate systems are activated?
 
+    RESOLVED: The logical choices are either VobCoorder, VobMatcher or a 
+    new class. Of these, VobCoorder can most likely store the information
+    efficiently. Thus, it's VobCoorder for now.
+
 - How is depth order etc. defined? This becomes a problem
   if (and when) we want to allow generic 3D manipulation; then,
   we need to actually find the "hit" in the coordinate system.
@@ -63,10 +67,14 @@
     public void activate(int cs)
     public void activate(Object key)
 
+These are automatically delegated to VobCooder's new method ::
+
+    public void activate(int cs);
+
 Also, make VobScene.put(Vob, coords) automatically call one of these.
 
 Then, redo getKeyAt() to return the key of the topmost **activated** 
-coordsys at the given location, with topmost defined as above.
+coordsys at the given location, with topmost defined as above. ::
 
     /** Get the topmost activated coordsys at (x,y), whose nearest activated
      * direct ancestor (not determining) is parent.
@@ -74,3 +82,4 @@
     public int getCSAt(int parent, float x, float y, float[] targetcoords) ;
 
     public Object getKeyAt(int parent, float x, float y, float[] targetcoords) 
;
+
Index: gzz/doc/pegboard/pegboard.html
diff -u gzz/doc/pegboard/pegboard.html:1.36 gzz/doc/pegboard/pegboard.html:1.37
--- gzz/doc/pegboard/pegboard.html:1.36 Fri Oct 25 04:46:21 2002
+++ gzz/doc/pegboard/pegboard.html      Mon Oct 28 03:50:38 2002
@@ -296,9 +296,45 @@
                </td>
                <td valign="top">mudyc<br>
             </td>
-            <td valign="top"><br>
+            <td valign="top">tjl<br>
                </td>
-             </tr>
+             </tr><tr>
+      <td valign="top" bgcolor="#ff9900"><a href="1021/click.rst">1021</a><br>
+      </td>
+      <td valign="top" bgcolor="#ff9900">current<br>
+      </td>
+      <td valign="top" bgcolor="#ff9900">Mouse clicks and VobScene<br>
+      </td>
+      <td valign="top" bgcolor="#ff9900">tjl<br>
+      </td>
+      <td valign="top" bgcolor="#ff9900"><br>
+      </td>
+    </tr>
+    <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><br>
+      </td>
+    </tr>
+    <tr>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><br>
+      </td>
+      <td valign="top"><br>
+      </td>
+    </tr>
+
 
   </tbody>
 </table>
@@ -370,6 +406,7 @@
 
 <br>
 
+<br>
 <br>
 <br>
 <br>




reply via email to

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