I see, thanks Marting. I presume if performance of tesselation was a problem, some applications could get around that by caching the results - perhaps in a saved binary file. Only recalc these on application startup if the corresponding svg file was newer.
On Jul 19, 5:24 pm, "Martin O'Leary" <[email protected]> wrote: > 2009/7/14 Tristam MacDonald <[email protected]>: > > > > > The > > glu tesselation functions were designed long before the number of draw calls was ever considered as a potential bottleneck, and at that time vertex processing was the bottleneck. Unfortunately, > > the entire of glu has been deprecated, so it is unlikely to receive any > > improvements in this area. > > The alternative, I am afraid, is to roll your own tessellation functions. > > This isn't actually that hard, and has the benefit that you will have > > complete control of the output, but it will be a bit of work. > > One unfortunate disadvantage of this approach is that it requires > either Python code for tessellation (quite slow) or packaging C > libraries with your code (and we all know the problems that can arise > from that). The advantage of GLU is that, while it's officially > deprecated, it is widely available, and generally performs as > advertised. If you can make GLU do what you want to do, it's a quick > and easy route to some quite well optimized behaviour on a wide > variety of systems. > > Martin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
