gzz-commits
[Top][All Lists]
Advanced
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] gzz/doc/pegboard/1003 PEG_1003.html

From: Tuomas J. Lukka
Subject: [Gzz-commits] gzz/doc/pegboard/1003 PEG_1003.html
Date: Tue, 27 Aug 2002 00:32:18 -0400 
CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Tuomas J. Lukka <address@hidden>        02/08/27 00:32:18

Modified files:
        doc/pegboard/1003: PEG_1003.html 

Log message:
        Incomplete change; will try to complete later

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/doc/pegboard/1003/PEG_1003.html.diff?tr1=1.1&tr2=1.2&r1=text&r2=text

Patches:
Index: gzz/doc/pegboard/1003/PEG_1003.html
diff -c gzz/doc/pegboard/1003/PEG_1003.html:1.1 
gzz/doc/pegboard/1003/PEG_1003.html:1.2
*** gzz/doc/pegboard/1003/PEG_1003.html:1.1     Sun Aug 25 13:39:35 2002
--- gzz/doc/pegboard/1003/PEG_1003.html Tue Aug 27 00:32:18 2002
***************
*** 2,34 ****
  <html>
  <head>
    <title>PEG 1003</title>
    <meta http-equiv="content-type"
   content="text/html; charset=ISO-8859-1">
  </head>
! <body>
  <h1>PEG 1003: Fix hierarchical <tt>VobScene</tt>s</h1>
  <p>Hierarchical <tt>VobScene</tt>s need some fixing.<br>
! </p>
  <p>Open issues:<br>
! </p>
  <ul>
!   <li>Is the integer identifier of the coordinate system into which to place
  a new coordinate system appropriate?</li>
!   <li>Should plain coordinate systems be usable as those ints?</li>
    <ul>
!     <li>What are the semantics there? Current, just translate, is not good.
! However, using the vob-internal CS is not really nice either, as Vob CSs
! usually are in pixels, and this would be in 10s or 100s of pixels per 
unit.</li>
    </ul>
!   <li>The most general use case is the PP-like viewport. How is that 
implemented?
  You need</li>
    <ul>
!     <li>clipping</li>
!     <li>separate coordinate system for the motion of the clipping rectangle
! and the contents<br>
!     </li>
    </ul>
  </ul>
! <br>
  </body>
  </html>
--- 2,52 ----
  <html>
  <head>
    <title>PEG 1003</title>
+       
    <meta http-equiv="content-type"
   content="text/html; charset=ISO-8859-1">
  </head>
!   <body>
!  
  <h1>PEG 1003: Fix hierarchical <tt>VobScene</tt>s</h1>
+  
  <p>Hierarchical <tt>VobScene</tt>s need some fixing.<br>
!  </p>
!  
  <p>Open issues:<br>
!  </p>
!  
  <ul>
!    <li>Is the integer identifier of the coordinate system into which to place 
  a new coordinate system appropriate?</li>
!    <li>Should plain coordinate systems be usable as those ints?</li>
!    
    <ul>
!      <li>What are the semantics there? Current, just translate, is not good. 
! However, using the vob-internal CS is not really nice either, as Vob CSs 
usually
! are in pixels, and this would be in 10s or 100s of pixels per unit.</li>
!    
    </ul>
!    <li>The most general use case is the PP-like viewport. How is that 
implemented? 
  You need</li>
+    
    <ul>
!      <li>clipping</li>
!      <li>separate coordinate system for the motion of the clipping rectangle 
! and the contents</li>
!    
    </ul>
+  
  </ul>
! Possible solutions:<br>
! <ul>
!   <li>Separate clipping from coordinate systems. Currently, a coordinate
! system defines a clip rectangle. How about specifying the coordinate system
! to clip to when creating a (any) coordinate system, as well as the coordinate
! system into whose coordinates the given coordinate system should go.<br>
!   </li>
! </ul>
!  <br>
!  <br>
  </body>
  </html>
reply via email to
[Prev in Thread] Current Thread [Next in Thread]