[Gzz-commits] gzz/doc/pegboard/1009 PEG_1009.rst

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Tuomas J. Lukka <address@hidden>        02/10/07 01:09:55

Modified files:
        doc/pegboard/1009: PEG_1009.rst 

Log message:
        Answered by email

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/doc/pegboard/1009/PEG_1009.rst.diff?tr1=1.12&tr2=1.13&r1=text&r2=text

Patches:
Index: gzz/doc/pegboard/1009/PEG_1009.rst
diff -c gzz/doc/pegboard/1009/PEG_1009.rst:1.12 
gzz/doc/pegboard/1009/PEG_1009.rst:1.13
*** gzz/doc/pegboard/1009/PEG_1009.rst:1.12     Mon Oct  7 00:33:07 2002
--- gzz/doc/pegboard/1009/PEG_1009.rst  Mon Oct  7 01:09:55 2002
***************
*** 4,11 ****
  =============================================================
  
  :Authors:  Tuomas Lukka
! :Date:     $Date: 2002/10/07 04:33:07 $
! :Revision: $Revision: 1.12 $
  :Status:   Incomplete
  
  Transformations
--- 4,11 ----
  =============================================================
  
  :Authors:  Tuomas Lukka
! :Date:     $Date: 2002/10/07 05:09:55 $
! :Revision: $Revision: 1.13 $
  :Status:   Incomplete
  
  Transformations
***************
*** 25,71 ****
        return ortho(into, 0, 0, 0, x, y);
      }
  
! and rename coordsys into ortho
! 
! 
!     (Benja says:) ``scale`` doesn't belong here, because AWT cannot do it 
properly
!     when text is involved (because text's aspect ratio may change
!     with size).  
!       
!       (Tjl:) Well, coordsys already *does* scale. The thing is to just
!       ask for the font's width with the right scale, which you should
!       be able to ask the coordsys. Something like ::
! 
!           scale = vs.getHeight(cs);
! 
!       ?
!         
!             (Benja:) We have talked about this earlier. It messes up the
!             layout, because *the aspect ratio changes*, as I have said above.
!             You *cannot* assume that you can scale below the view level in 
AWT.
! 
!               (Tjl:) I didn't make my point clear. We *can* do this,
!               if we ask, at vobscene construction time,
!               how tall a given cs will be. 
!                 
!                     (Benja:) Ah. Now I understand somewhat... However,
!                     even then, you cannot satisfy scaling in two dimensions,
!                     so it would have to be ``scale(int into, float scale)``.
!                     Also, you're talking about the "height" of a coordsys--
!                     what is this? Coordsys are, at this point, transformations
!                     of points-- so what's the "height" of a transformation?
!                     Finally, I still don't like scale being here, because
!                     generally having to know the scale before the view
!                     comes in means that we cannot switch to a system where
!                     (in gl) we determine the parent transformations
!                     *after* the views have done their job. For example in
!                     text layout, it would be nice if we could first render
!                     the text with a given width, then look at the resulting
!                     height and decide how to translate the result-- this
!                     requires that a coordsys gets its parent after it
!                     is first created-- not currently allowed, but not 
!                     impossible to change.
!                     
  
  And into AffineVobCoorder the following functions::
  
--- 25,31 ----
        return ortho(into, 0, 0, 0, x, y);
      }
  
! and rename coordsys into ortho.
  
  And into AffineVobCoorder the following functions::