I haven't been paying any attention to this thread, so sorry if this comment is totally off-point, but it would be possible to use setuptools plugins to allow third-party modules to appear as if they were in the pyglet.resource module.
This seems like a better solution than putting a module in pyglet/contrib, since (correct me if I'm wrong) nothing in that directory is actually installed. -Kale On 01/29/2017 08:32 PM, Benjamin Moran wrote: > [email protected], > Being non-standard is definitely a strong mark against it. In my mind, the > main > advantage of having it included in pyglet over an external module would be to > take advantage of the pyglet.resource module (and being automatically placed > in > an atlas.TextureBin). Animations already have their own add_to_texture_bin() > method of course, but I was thinking of this from the point of users. Perhaps > you're right, though, and the proprietary aspect of it is a disqualifier. > > Tristam, that's a good idea. I think there are a lot of interesting things out > there that don't belong in pyglet proper, but would be found useful by a lot > of > people. This might be another conversation, but my thought was that maybe this > is how the pyglet/contrib section of the pyglet repository can be used (after > some cleanup). The pyglet documentation could maybe have a short section that > mentions both contributed modules, as well as modules that are related to > pyglet > but hosted in their own repositories: > > "Module A", found in the pyglet/contrib directory: This module does A, B, > and C. > "Module B", found at www.somerepo.com: This module does X, Y, and Z. > > Perhaps I'll make this into a standalone module, and put it into the > pyglet/contrib directory. > > > On Monday, January 30, 2017 at 9:15:53 AM UTC+9, [email protected] wrote: > > I'm not sure, a lot of tools have their own proprietary formats that > aren't > likely going to be a standard any time soon, and its not as though its > difficult to export them into more compatible formats. There's also the > question of redundancy/bloat, do these formats add anything that existing > formats don't? If not then I may be more inclined to just create a > separate > addon script you can add to pyglet and leave it out of pyglet proper. > > -- > You received this message because you are subscribed to the Google Groups > "pyglet-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email > to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/pyglet-users. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
