|
From: Roger H. <rog...@mi...> - 2007-06-29 12:53:01
|
On 28 Jun, 2007, at 22:39, Jose' Cruanyes wrote: > We're ready to go on with the Hiddenline renderers, but I'm not sure > that poluting the Quesa space is the way to go, also because we want > to create several different renderers. > > so we want to detach the renderers from quesa. Sounds good. > > there are several options, > one Quick n dirty that is use several #defines to turn on and off > the renderers at compile time, > and the other is to make all the renderers (minus one?) plug-ins. If you are not talking about source separation, there's not much wrong with what I am doing now, which is to only allow the user to select the ones the application supports, either grey them out or what I do, not add them to the appropriate menu/pop-up menu. Of course plug-in renderers give better modularity. > > the problem with the second approach is that the Open GL renderers > (that forms the base class for all others) uses private View methods > and data, so we have to make them public. How many methods are we talking about? Would they be of any use to other renderers? Could they be implemented as a library which was hard linked? > > the third approach is to leave the OpenGL Hiddenline renderer (only > one) on by default, You mean the original 'Interactive' renderer is not going to be the default? A traditional hidden line renderer would not be much good as a default. > > Also, What about make the cartoon renderer a illumination style like > Phong or Lambert? Nice lateral thinking. Yes I like it. > What do you think? > > Pax et Bonum |