/[gzz]/gzz/doc/pegboard/1009/PEG_1009.rst
ViewVC logotype

Diff of /gzz/doc/pegboard/1009/PEG_1009.rst

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.7 by benja, Sun Oct 6 16:44:05 2002 UTC revision 1.8 by benja, Sun Oct 6 16:52:16 2002 UTC
# Line 34  Add into VobCoorder the following conven Line 34  Add into VobCoorder the following conven
34                    
35          (Tjl:) Well, coordsys already *does* scale. The thing is to just          (Tjl:) Well, coordsys already *does* scale. The thing is to just
36          ask for the font's width with the right scale, which you should          ask for the font's width with the right scale, which you should
37          be able to ask the coordsys. Something like          be able to ask the coordsys. Something like ::
38    
39              scale = vs.getHeight(cs);              scale = vs.getHeight(cs);
40    
41          ?          ?
42            
43                (Benja:) We have talked about this earlier. It messes up the
44                layout, because *the aspect ratio changes*, as I have said above.
45                You *cannot* assume that you can scale below the view level in AWT.
46    
47  And into AffineVobCoorder the following functions::  And into AffineVobCoorder the following functions::
48    
# Line 60  And into AffineVobCoorder the following Line 64  And into AffineVobCoorder the following
64          (Tjl:) Well, have you looked at fillets demo? We don't always          (Tjl:) Well, have you looked at fillets demo? We don't always
65          want to keep in a 2 1/2 D world. Sometimes 3D is nice.          want to keep in a 2 1/2 D world. Sometimes 3D is nice.
66          But maybe best to leave it to GLVobCoorder.          But maybe best to leave it to GLVobCoorder.
67            
68                (Benja:) Ok.
69    
70  Also, for all these functions, we should have a shorthand  Also, for all these functions, we should have a shorthand
71  in VobScene:  in VobScene:
# Line 71  just to make it a little easier to say t Line 77  just to make it a little easier to say t
77      (Benja:) How about just ``translate``?      (Benja:) How about just ``translate``?
78                    
79          (Tjl:) Want to make sure it's not interpreted as "translate this vobscene".          (Tjl:) Want to make sure it's not interpreted as "translate this vobscene".
80            
81                (Benja:) Hmmm... ok... ``translateCS`` just seems hard to write.
82    
83  For the affine ones, the VobCoorder is cast into AffineVobCoorder, and  For the affine ones, the VobCoorder is cast into AffineVobCoorder, and
84  the error propagated if it's not.  the error propagated if it's not.
# Line 87  the error propagated if it's not. Line 95  the error propagated if it's not.
95    
96          (Tjl:) How about UnsupportedOperationException? Hmm..          (Tjl:) How about UnsupportedOperationException? Hmm..
97          or a subclass of that, NotAffineCoorder          or a subclass of that, NotAffineCoorder
98            
99                (Benja:) Subclass, because a) we need to store the view in
100                the exception, and b) ``UnsupportedOperationException`` is
101                raised by *many* things, not safe to use at all.
102    
103    
104  Transforming points into coordinate systems  Transforming points into coordinate systems
# Line 116  At the same time, remove VobCoorder.getR Line 128  At the same time, remove VobCoorder.getR
128          (Tjl:) One that requires catch() or one that doesn't?          (Tjl:) One that requires catch() or one that doesn't?
129          I don't really like the exception either way: a pseudoinverse          I don't really like the exception either way: a pseudoinverse
130          (closest to real inverse) can be well-defined.          (closest to real inverse) can be well-defined.
131            
132                (Benja:) Hm. So is the method supposed to return ``true``
133                if the inverse that was found is real? Then need to change
134                javadoc: a pseudoinverse is "reasonable" IMHO. On the other
135                hand, if there are cases where no usable inverse can be found,
136                we need the exception (not sure which type).
137    
138  The reason for allowing the array ``pt[]`` to contain several points is  The reason for allowing the array ``pt[]`` to contain several points is
139  simply performance.  simply performance.

Legend:
Removed from v.1.7  
changed lines
  Added in v.1.8

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26