On Sat, Apr 17, 2010 at 8:51 PM, Joe Wreschnig <[email protected]>wrote:
> As soon as you make a > window or a vertex buffer or load an image or etc., you're going to > end up paying most of that cost anyway. > Not entirely. You can (at least in theory) avoid the cost of the text rendering subsystem and the audio subsystem, each of which are fairly heavy on initialisation costs. Either pyglet > should commit to explicitly exposing the (real) pyglet.foo modules, or > it should not and application writers should explicitly import what > they want to use. Six of one, half a dozen of the other. As you mentioned earlier, pyglet has a metric ton of modules, and importing them explicitly is a bit of a pain, especially for the short programs where pyglet's terseness really shines. As for pyglet importing everything by default, give it a try. Explicitly import all pyglet modules into each file of your program, and see what it does to your startup times. It may be that you can live with the increased launch times, but I certainly wouldn't want to impose that penalty on everyone. -- Tristam MacDonald http://swiftcoder.wordpress.com/ -- 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.
