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 06:19:35 -0400 
CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Tuomas J. Lukka <address@hidden>        02/08/27 06:19:35

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

Log message:
        A small comment. Setting mozilla's composer to not reformat the source 
seems to help the diffs considerably.

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

Patches:
Index: gzz/doc/pegboard/1003/PEG_1003.html
diff -c gzz/doc/pegboard/1003/PEG_1003.html:1.4 
gzz/doc/pegboard/1003/PEG_1003.html:1.5
*** gzz/doc/pegboard/1003/PEG_1003.html:1.4     Tue Aug 27 05:32:18 2002
--- gzz/doc/pegboard/1003/PEG_1003.html Tue Aug 27 06:19:34 2002
***************
*** 1,11 ****
! <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
! <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><i>
  Author: Tuomas Lukka
--- 1,8 ----
! <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 
Transitional//EN"><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><i>
  Author: Tuomas Lukka
***************
*** 58,64 ****
                   (so that the focus is shown in the middle of the viewport,
                   and as much of the viewed thing is shown around the focus
                   as fits in the viewport).
!          </ul>
           Calculating the position of the viewed thing relative to the viewport
           is easier than calculating the absolute position of the viewed thing
           on the screen: to calculate the position relative to the viewport,
--- 55,61 ----
                   (so that the focus is shown in the middle of the viewport,
                   and as much of the viewed thing is shown around the focus
                   as fits in the viewport).
!          </li></ul>
           Calculating the position of the viewed thing relative to the viewport
           is easier than calculating the absolute position of the viewed thing
           on the screen: to calculate the position relative to the viewport,
***************
*** 67,76 ****
           essentally translating the focus coordinates by the viewport's.
           <br><br>
           Therefore, I think that there is no need to special-case this in
!          the API, as it's easier to do with two nested cs.
!   </small>
! 
!   <li>A suggested principle: Vobs should not have to worry about clipping,
  neither in AWT nor in GL. The current system where a Vob has to set its 
cliprect
  works for really simple cases but gets inefficient and inconvenient.</li>
    <li><tt>createCoordsys(int transformedBy, int clippedBy, Object key, 
...)</tt></li>
--- 64,73 ----
           essentally translating the focus coordinates by the viewport's.
           <br><br>
           Therefore, I think that there is no need to special-case this in
!          the API, as it's easier to do with two nested cs.<br>
! (Tuomas:) Sorry, I don't follow this argument at all. Could we start using
! (x,y,w,h) etc. notation, since the verbal description is a bit hard to follow?
! Even more so, pictures would be good...</small></li><li>A suggested 
principle: Vobs should not have to worry about clipping,
  neither in AWT nor in GL. The current system where a Vob has to set its 
cliprect
  works for really simple cases but gets inefficient and inconvenient.</li>
    <li><tt>createCoordsys(int transformedBy, int clippedBy, Object key, 
...)</tt></li>
***************
*** 96,102 ****
     <li>The most general use case is the PP-like viewport. How is that 
implemented?
  You need
  
!     <li>cs1 = createCoordsys(0, 0, ...)</li>
      <li>cs2 = createCoordsys(0, cs2, ...)</li>
      <li>would clip by both coordinate systems when cs2 used.<br>
      </li>
--- 93,99 ----
     <li>The most general use case is the PP-like viewport. How is that 
implemented?
  You need
  
!     </li><li>cs1 = createCoordsys(0, 0, ...)</li>
      <li>cs2 = createCoordsys(0, cs2, ...)</li>
      <li>would clip by both coordinate systems when cs2 used.<br>
      </li>
***************
*** 111,124 ****
       and the child being used for the contents.
    </p>
  
!   </li>
  
- </ul>
    <br>
    <br>
!   </li>
! </ul>
   <br>
   <br>
! </body>
! </html>
--- 108,121 ----
       and the child being used for the contents.
    </p>
  
!   
! 
  
    <br>
    <br>
!   
! 
   <br>
   <br>
! <br>
! </body></html>
\ No newline at end of file
reply via email to
[Prev in Thread] Current Thread [Next in Thread]