> Again, there are specific problems with using PIL: > > 1) Images are currently sent to OpenGL decoded. This is wasteful of > ram and CPU power. Decoding should only happen when nessesary.
I don't understand what you mean ? > 2) PIL doesn't support APNG, MNG, or Ogg Theora Yes, but at least it supports PNG, JPEG and other more "exotic" image format. Adding support for animated textures doesn't require to rewrite non-animated texture, isn't it ? > 3) PIL has libpng and libjpeg as dependencies, therefore so does Soya, > and PIL also has many more libraries as dependencies For an other project, i have read part of PIL sources, and i remember there was a pure-Python PNG support. However they probably have libpng support too for performance. Moreover, PIL is packaged for many Linux distribution, if not all. > PIL is dual-licensed, meaning they only GPL older versions while making > people pay for the newest. For this reason I don't want to contribute > to them to add APNG/etc support (nor do I want anyone else to). As long as it is GPL'ed, and it fits our need, it is not a problem. Older versions of Soya (< 0.7 i think, before the Pyrex rewrite) were linked to libPNG and libJPEG. However it caused some compilation problems during the transition between 2 libpng versions. PIL is virtually immune to that, since i believe it defaults to pure-python if it fails linking to libpng. I also think we don't have to support ALL animation formats. I think a loss-less compression format and a non-loss-less compression format is far enough, as conversion tools exist, or even only a single format. My personal preference goes to MNG and / or Ogg Theora. Ideally, we should not link directly to the C library (libmng, libtheora ?) but use the corresponding python module (pytheora ?), in order to avoid static dependencies as well as compilation troubles. Jiba _______________________________________________ Soya-user mailing list [email protected] https://mail.gna.org/listinfo/soya-user
