In my case, I don't need the window and context management, because I
use pyglet in a PyQt application, just for its OpenGL bindings and the
buffers/texture/etc.. abstraction library.
Would that be possible to add an option to completely disable the
window and context management in pyglet without breaking everything ?
I have some time to contribute a patch, but I would like to know if
this is a silly idea first.
[1] http://groups.google.com/group/pyglet-users/browse_thread/thread/4968e9ab69a6661c
--
Lup
pyglet works on Snow Leopard using a 32-bit Python. I'm currently
using 2.6.4 from ActiveState.
Richard
Yes I'm aware of that, but I actually need a 64 bits Python for this
app.
Where's the cocoa effort concentrated?
....
Would that be possible to add an option to completely disable the
window and context management in pyglet without breaking everything ?
I have some time to contribute a patch, but I would like to know if
this is a silly idea first.
I've implemented the option by avoiding a few imports here and there,
my app starts, but then even basic things like creating textures are
broken because they are tied in some way to context management
(getting GL version, etc...).
So, it seems implementing this option can't be done the quick and
dirty way, I'd rather be working on a cocoa port. Tristam could you
send me your patches, or perhaps create the branch so I can work on
it ?
Thanks
On Feb 27, 11:39 am, Florian Bösch <pya...@gmail.com> wrote:I've implemented the option by avoiding a few imports here and there,
> This could be opened as a branch to pyglet mainline, so it can be
> improved by whoever has access to a mac.
my app starts, but then even basic things like creating textures are
broken because they are tied in some way to context management
(getting GL version, etc...).
So, it seems implementing this option can't be done the quick and
dirty way, I'd rather be working on a cocoa port. Tristam could you
send me your patches, or perhaps create the branch so I can work on
it ?
Well, we're anyway operating on the principle that whoever gets stuff
done does "maintain" something, so if the source to that branch is
"query it from Tristam" that pretty much ensures almost nobody will
check it out just to see how things are, and decide to take it up. It
really is a 1:1 thing, and that's not good in a distributed source
control, where things should be n:m.
Chard.