Hi,
On 10/25/06, Robert Osfield <[EMAIL PROTECTED]> wrote:
Hi Rafa,
W.r.t subclassing DatabasePager and DatabaseRequestHandler, I'm open
to changing some methods to virtue as long as they are methods that
are called often.
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.
Should be very great, I currently don't have to subclass the
DatabasePager to make what I want, but I use some "dirty" tricks to
get it works. So by adding some callbacks, everything should be a lot
more clean.
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.
Multiple database reading threads should be great too, as we are going
into a multiple core era.
I am quite busy too but if anyone want to talk about this feature or
to start something, let me know, it would be a pleasure for me to
help.
--
Serge Lages
http://www.magrathea-engine.org
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
