Alternatively it might be that a small tweak to the design of
DatabasePager & DatabaseRequestHandler would help avoid the need for
subclassing. For instance using calbacks to override specific bits of
functionality rather than forcing subclassing is one way.
I also consider DatabasePager something that is not cast in concrete,
it works well for a range of usage styles, but I'm certainly open to
suggestions as to how it could be further improved. Areas of interest
to me are use of multiple database reading threads, the possibility of
multi-threading texture/display list generation using shared graphics
context.
I am however really busy right now, so can't get embroiled in any
complex topics as I simply don't have the bandwidth available.
Don't worry about that!, I'm really busy too, and the releases of our code needs
sometimes not make the best changes on the libraries, but when I have some
time I will try to suggest some of the work I was developing on here.
Thanks!
Rafa.
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
