On 8 June 2017 at 13:47, Benjamin Moran <benmora...@gmail.com> wrote:
> I think as one of the "pyglet elders", Richard gets two votes here :)
> I believe that generic 3D model support, and a user-friendly way to set 2D
> and 3D projections are two of the last things missing from pyglet.
>
> Splitting pyglet into seperate modules at this point is probably not a
> good idea due to the aforementioned number of contributors. It's a
> discussion best left for the future when we're migrated to GL3+/Python3,
> and possibly pick up a few active contributors.
>
I would caution against overloading the GL3+ migration (I regret mentioning
Python 3, I shouldn't have confused the scope of the work like that).
> Regarding avoiding bloat, I think the basic classes and loading mechanisms
> are important. The codecs themselves are a different story, and I agree
> that we shouldn't try to support too much. We have good mechanisms for
> adding codecs later, just like the image module:
> pyglet.model.codecs.add_decoders(MyFormatDecoder())
> model = pyglet.model.load("mymodel.xyz")
>
> One or two generic decoders are probably a good idea. Obj seems a
> no-brainer.
>
+1
Richard
--
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 pyglet-users+unsubscr...@googlegroups.com.
To post to this group, send email to pyglet-users@googlegroups.com.
Visit this group at https://groups.google.com/group/pyglet-users.
For more options, visit https://groups.google.com/d/optout.
