[visionegg] Re: Retry: Pyglet?

Hi Dav,

Yes, pyglet-experiment is the branch to work on. I just merged all the
recent changes from the trunk. I never quite got pyglet experiment to
work, and unfortunately I don't have a lot of time right now to devote
doing it myself. If you get it working, that would be great. Although a
current limitation of pyglet compared to pygame is the lack of gamma
setting functions. Jon Peirce (of PsychoPy fame) contacted me about
porting these platform dependent functions to pyglet, so I think there
is some will and manpower to share the load -- perhaps PsyhchoPy folks
have already started on this. The main downside to pyglet that I can see
is that it may be slower than PyOpenGL 2 due to switching to ctypes
wrappers from swig. But PyOpenGL 3 already uses ctypes, so this issue
seems like something we're going to have to live with, regardless.

Also, I was going to wait until I had more experience with it before
making an announcement here on the mailing list, but I have created a
git repository mirroring the svn repository of the vision egg at
http://github.com/astraw/visionegg . I just created a pyglet-experiment
branch, there, too. If you'd prefer using git over svn, we could use
that. I haven't tried git/svn interoperability when branches are
concerned, but my first guess is that it's not going to be as easy or
seamless as it is updating just the svn trunk from a single git branch.
If we use git, I'm pretty sure we'll loose our merge tracking on the svn
branch (done with svnmerge.py). So if we choose to use git, it may be a
choice not easily reversed in terms of importing the revision history
back to svn for that branch. Nevertheless, I so far really like git (I
am using it for a number of personal projects), and it may make
collaborative development easier, so if you'd prefer it, I'd say to go
for it.

-Andrew

Dav Clark wrote:
> Hey all,
> 
> I'd like to try using pyglet w/ VisionEgg in order to better support two
> monitors (so I can have a monitoring console) and also to have access to
> what seems to be a much better event loop (for example, events such as
> keypresses are registered via callbacks, not reteived from an event queue).
> 
> There are currently two branches, pyglet-experiment seeming to be the
> more recent (8 months instead of closer to a year).
> 
> If I want to have a look at the latest and greatest attempts at pyglet
> integation... should I simply pull down that branch?  And maybe merge in
> changes from trunk?  Any other advice?
> 
> Cheers,
> Dav
> ======================================
> The Vision Egg mailing list
> Archives: http://www.freelists.org/archives/visionegg
> Website: http://www.visionegg.org/mailinglist.html


-- 
Dr. Andrew D. Straw
California Institute of Technology
http://www.its.caltech.edu/~astraw/
======================================
The Vision Egg mailing list
Archives: http://www.freelists.org/archives/visionegg
Website: http://www.visionegg.org/mailinglist.html

Other related posts: