From: Mark B. <mb...@0x...> - 2000-07-25 18:50:19
|
PySDL is at the point where I'm not certain where its users would like it to further develop. This is in part why the releases have slowed, since I'm often second-guessing future design plans. So what I'm looking for, is ideas as to what people want from PySDL, that it doesn't currently provide. Ideas I've tossed around include creating an interface similar to the one surface objects have for audio buffers, adding adaptors for PIL and PST, creating an overly complex system for 'compiling' surface operations for speed, and some other things. The first idea isn't such a terrible one, but I've yet to find a need for it, or hear of anyone that needs such an ability. The second idea seems like a somewhat practical way for people to save modified data to various file formats. The third idea seems less and less practical as time goes on, since I'm still not convinced that Python will ever be the proper environment for complex realtime effect generation, or if it will, that the complexity belongs within a support module. As you can see, these don't really account for much of what might be practical for PySDL users. Do they care about saving screen shots in JPEG, or whether PySDL offers a mini-compiler/interpreter for surface operations? Perhaps what they'd like are C functions for more easily integrating PySDL into a C SDL program, so they can use it for scripting? Perhaps what they'd like is an add-on framework they can use the develop software in Python, using PySDL, so everyone using PySDL doesn't need to implement the same engine 1,000 times? I don't know. So I'm asking. What is it you want? I'd also like to note that Pete Shinners sent me a more modularized PySDL code base a number of days ago. I'm still contemplating whether I like the layout, but it seems to be a clean break up. I might be able to use some macros and other evil C tricks to reduce some of the namespace pollution, but this might not be worth the evil involved. A side note to Pete: I haven't been ignoring you, I've just been trying to decide what I think of it before giving you a response. ;-) |