Tuesday, June 9, 2009

Status?

pybox2d isn't dead just yet.

A few days ago, I started porting the bleeding-edge version of the library.

Some changes include the addition of b2Fixture, contact listener changes, a new way to create edge chains, and significant algorithm changes. More information on these C++-specific changes can be found on the forums and the Box2D SVN changelog.

As it is a departure from the previous builds, it will stay as a branch on here at least until it's significantly improved over the trunk. I'm not entirely happy about the significant API changes that are occurring, but I'm just bringing to Python what Erin Catto and others are making available to the C++-world. I guess what I'm trying to say is, well, don't shoot the messenger.
Posted by at

5 comments:

  1. elemelJune 17, 2009 at 1:45 AM

    Sounds great. :-)

    ReplyDelete
  2. AnonymousJuly 27, 2009 at 4:18 AM

    Totally understandable re: the API changes.

    ReplyDelete
  3. AnonymousSeptember 23, 2009 at 1:33 AM

    How's pybox2d doing? Haven't heard in awhile and miss the updates.

    ReplyDelete
  4. kneOctober 3, 2009 at 3:44 PM

    With new personal obligations (grad school + work are somewhat of time sinks), pybox2d is on the back-burner.

    I can't say there's too much to implement once I get the chance, though. Upstream, Box2D has had but a few changes recently. Removal of SetMassFromShapes is nice, I guess. The new broadphase -- no more proxies -- is possibly the best thing. Constantly changing function names and structures make for big headaches on this end, so I'm sure you can see why I'm not terribly excited about it. There's been some issues with 64-bit installs again, but I have yet to get a 64-bit VM up and running to sort that out.

    On the plus side, there's been a few projects popping up every now and then. Until I get back to it, maybe you could check out some of them? :)

    ReplyDelete
  5. Mark WexlerOctober 26, 2009 at 10:18 AM

    I'm just starting to use pybox2d, and so far I'm really happy with it: everything just seems as easy and elegant as it could be.

    I'm a little bit worried, though, about kne's last comment, the one about not being completely happy with the changes happening to Box2D. Could you be a little more specific? What direction is it evolving in, and why would someone not necessarily be happy with it?

    This is important for someone who's about to invest a significant amount of effort in (py)Box2D. Thanks a lot.

    ReplyDelete

Subscribe to: Post Comments (Atom)