|
From: <br...@ph...> - 2005-04-14 14:15:16
|
Ga=EBl Varoquaux wrote: > I was not aware of the term.c:do_arrow() and do_point(), I need t= o > spend more time reading gnuplot's code.=20 If you've ever done OO coding, it's quite simple: there'll be a "base= =20 class" implementing a set of 3D terminal-like operations by,=20 essentially, calling map3d_xy() and then handing the work over to the 2D terminal API, or by calling other functions of the class. Native = 3D terminal drivers then get to "overload" as many of those methods as i= t=20 takes to get the job done. > Yes this is maybe a solution, but if you look at the way do_3dplot = is > currently written there is a lot of work to do to break it in > routines that separate the data handling and resizing, from the > projection and the removing of the hidden lines. Of course. The important thing to note is that collecting this code= =20 into calls of native 3D terminal-style functions will benefit the= =20 overall code quality even if we were to decide not to ever actually= =20 incorporate 3D drivers. We can only benefit from this, no matter how= =20 far we actually go. |