Pyglet: Day 1

I’m calling it a night on day 1 of playing with pyglet. It was an interesting and fun day. The worst part was definitely the 3 or 4 crashes I caused with NetBeans by pressing some key combinations. I didn’t quite narrow down the general pattern that was causing it but each time I was able to replicate it immediately after restarting so then I just knew to avoid using that key combination in that situation. Annoying… yes. Deal-breaker… no.

I definitely scoured the pyglet documentation and api listing as well as beckoned Google’s aid in the learning experience today. And I feel that I have definitely learned from it. I suspect that the next time I pick up on this project, I will be doing more of the same. Pyglet doesn’t feel natural to me yet, but I am making progress and frequently running the code to make sure that I haven’t broken anything beyond repair. That quick run is definitely one of my favorite things about languages that don’t need to be compiled!

Once I finish up this game, I will be opening up a page that lists the projects that I have done and that I will be working on in the near (and maybe not-so-near) future. I did some work on that page today when my mind needed a break from reading python code. So it really just needs a valid link to download the game from and for me to decide how I’m gonna have the screen shots laid out on the page.

Here’s to hoping that I have the free time to make Pyglet: Day 2 happen in the very near future. I look forward to it!

Python: The Tools

I’ve made the choice about what language and libraries I’m gonna toy around with and I’m in the process of getting it all set up.

Python is the language. Version 2.6.2 as it seems most tools and apis are written for the 2.6 line and not yet updated for the 3.x version of python.

Netbeans is the ide. I’ve used Netbeans before so it’s not wholly new to me. But it is a newer version and it has been approximately a year since I’ve used Netbeans. So, I’m not really expecting any big learning curve or anything.

After getting everything installed, I’m gonna get acclimated to using python in Netbeans and then get started on a simple game to introduce me to pyglet.

Pyglet is the “cross-platform windowing and multimedia library” that I’m gonna use. Essentially it’s gonna handle some of the game-oriented features that I need. This is the first of the tools that I’ve never used a day in my life so hopefully I learn it quickly and smoothly.. only time will tell.

Pyglet is based on OpenGL. I’m not expecting that to present any problems though since that’s the api that I learned when I first learned graphics programming like 5 years ago. I’ve never really used DirectX (XNA is as close as I’ve gotten to that), so my mind thinks in the “OpenGL way” anyway when it comes to graphics related code.

If memory serves me correctly, getting OpenGL installed and set up can potentially be a pain. /sigh. Nothing to it but to do it, though.

I’ll have to see how my first experiences with pyglet go, but from the reading I did, I’m thinking it may be necessary to use rabbyt as well. Several sources pointed out that pyglet doesn’t have a sprite type object for getting images into the game and manipulating them. And rabbyt is a (currently in beta) library built on top of pyglet to resolve that exact issue. But I’m gonna hold off on it for the time being. That’ll give me a chance to get acquainted with the different tools I’m using anyway as it ramps up from just python with Netbeans to including pyglet (with OpenGL attached) and then to rabbyt (should it be necessary).

Here’s to a day of getting acquainted with the tools!