/[gzz]/gzz/doc/pegboard/1018/PEG_1018.rst
ViewVC logotype

Diff of /gzz/doc/pegboard/1018/PEG_1018.rst

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

revision 1.1 by humppake, Thu Oct 17 06:14:44 2002 UTC revision 1.2 by humppake, Fri Oct 18 13:14:10 2002 UTC
# Line 8  PEG 1018: Generalizing VobVanishingClien Line 8  PEG 1018: Generalizing VobVanishingClien
8  :Status:   Incomplete  :Status:   Incomplete
9    
10  Yes, I believe that the view interface in 0.8 is much more  Yes, I believe that the view interface in 0.8 is much more
11  flexible than the on in 0.6. Although I have been now working  flexible than the on in 0.6. Although I had been working
12  on 0.8 for weeks, I need still time to get used to those  on 0.8 for weeks, I still had problems to get used to those
13  coordsys transformations everywhere. I think there should be  coordsys transformations everywhere. I think there should be
14  easy-to-use interface for prototyping new views. Something where  easy-to-use interface for prototyping new views. Something with
15  you can start directly putting some vobs into (at least 2D) space  you can start directly putting some vobs into space and see
16  and see the results without need to think optimal view spesific  the results without need to think optimal view spesific
17  coordinate systems first.  coordinate systems first.
18    
19    Issues
20    ------
21    
22  ``VobVanishingClient`` seems to have already it own simplified  ``VobVanishingClient`` seems to have already it own simplified
23  routines for placing vobs and building connections. Using those in  routines for placing vobs and building connections. Using those in
24  ``PlainVanishing`` looks quite nice. So, generalizing ``VobVanishingClient``  ``PlainVanishing`` looks quite nice. So, generalizing ``VobVanishingClient``
25  would be a good start. Probably using the raster could also be made easier,  would be a good start. So, because ``PlainVanishing`` is a hard coded
26  at least better documented.  component int ``VobVanishingClient``, I would first make this component
27    a parameter for ``VobVanishingClient``'s constructor, interface for the
28    component, and finally ``PlainVanishing`` only implements that interface.
29    Looks too simple this far. There must another issues to concern?
30    
31    Naming issues for above... and UML.
32    
33    Probably using the raster could also be made easier or at least
34    better documented.
35    

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.2

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