Box2d update from last SVN ?

Hello Brucey

Having some times to progress in my project using Box2d I'm wondering something about the Max module.

The actual version of Max-Box2d is very stable so maybe it's not too important for the moment.

As you may notice the v2.1.0 is nearly done.
Since the actual module use some of the incomplete features of v2.1.0, do you think it would be possible to be updated to this version ?

If the answer is yes, how do you proceed to find news and changes with SVN ?
With "Check for modifications" option and cycle though each files ?
What's your best approach to maintain "versioning" ?

Thanks ;)

The ModuleInfo in box2d.bmx usually gives an idea of where things are at :

ModuleInfo "History: 1.04"
ModuleInfo "History: Added b2ShapeDef.SetUserData() method."
ModuleInfo "History: Added b2Mat22.GetAngle() method."

That's the current SVN version - since the last release.
I have many more pending changes in my own version too.
You will also see things like :

ModuleInfo "History: Updated to box2d svn (rev 172)"

which show what svn revision of box2d the code supports.

The problem with proper box2d release version numbers is that the svn version is not always in-sync with that source, and hence saying that this is 2.1 wouldn't be entirely accurate.
Although I could add something like 2.1 + rev 1xx.

Finished off the latest work on it, and committed :

Updated to box2d svn (rev 175)
Added b2LineJoint type.
Added shape SetFriction() and SetRestitution() methods.

That's pretty much as current as the code gets :-p

Hum OK I see about the revision.
I wasn't very sure too about the official release and rev since there is often differences.
I was just wondering how you add change to the code.

By the way thanks for the update ;)

Do you mean, how *I* would find news/changes for the original SVN repo, or how *you* would find out what news/changes are in the box2d SVN repo? :-p

For maxmods, you can hook-up to the RSS feed on this page :
http://code.google.com/p/maxmods/source/list

Although it lists changes to all the modules there, you'd still see when a change to box2d occurred.


I compare the differences between one release and the previous, and see if anything new (API) has appeared, then work on applying those changes to the BlitzMax API. For example, there's a new b2LineJoint, which required adding new types, and modifications to the Joint creation code.
Fortunately, since I am working off the box2d SVN, changes tend to be small, so I'm not overwhelmed with stuff to add - unlike the case of updating from a new "release" version of a library, which can involve a lot of work to get the BlitzMax API back in-sync.

are there any tutorials for dumb people i.e. me

You answered my questions in your second paragraph :)
Thanks

I don't know about you but I have experimented crashing bug in the test bed "breakable body" example.

To reproduce it I just need to draw a polygon with "D" then create it with "M" and moving the broken part with the mouse.
I know it's sound like a testbed or box2d bug but just in case you experiment difficulties by porting this example in the future ;)