[Gzz-commits] gzz/doc/pegboard/1005 PEG_1005.txt

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Tuomas J. Lukka <address@hidden>        02/09/24 12:27:06

Modified files:
        doc/pegboard/1005: PEG_1005.txt 

Log message:
        Answer

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/doc/pegboard/1005/PEG_1005.txt.diff?tr1=1.2&tr2=1.3&r1=text&r2=text

Patches:
Index: gzz/doc/pegboard/1005/PEG_1005.txt
diff -c gzz/doc/pegboard/1005/PEG_1005.txt:1.2 
gzz/doc/pegboard/1005/PEG_1005.txt:1.3
*** gzz/doc/pegboard/1005/PEG_1005.txt:1.2      Tue Sep 24 08:42:29 2002
--- gzz/doc/pegboard/1005/PEG_1005.txt  Tue Sep 24 12:27:06 2002
***************
*** 24,29 ****
--- 24,33 ----
      Not sure we can make it general enough to encompass all the experiments
      we'd like to do...
  
+     (Tjl:)
+       Of course not; OTOH, it's better than what we have now. Going to the 
right 
+       direction.
+ 
  The VobMatcher API would be
  
      public interface VobMatcher {
***************
*** 53,60 ****
      
      Can that work with this scheme?`
  
  
! At the same time, add to VobMap a new method
  
      put(Vob v)
  
--- 57,69 ----
      
      Can that work with this scheme?`
  
+     (Tjl:)
+       I don't see why it couldn't. All we basically need is a call to
+       quash a renderable (don't show while animating) and replacing it with
+       split pieces.
+ 
  
! At the same time, add to VobPlacer a new method
  
      put(Vob v)
  
***************
*** 63,67 ****
--- 72,83 ----
  (Benja:) 
      I'd prefer a longer (more descriptive) method name as this won't be used 
      as often.
+ 
+     (Tjl:)
+       Consistency: we now have
+           void put(Vob vob, int coordsys);
+           void put(Vob vob, int coordsys1, int coordsys2);
+       so I think put(Vob v) would be best. Sorry, I first said
+       VobMap, I meant of course VobPlacer.  
  
      Tuomas